LateAnnualReturns.ie
Last updated: 11 November 2026
| Type of data | Examples | Where it comes from |
|---|---|---|
| Order details | Your name, email address and phone number; the company name; the name and address the invoice should be issued to; the CRO number; financial year end; whether a strike-off notice has been issued; your reason for the late filing; your payment method. | You, through the order form. |
| Identity and AML documents | Passport, national ID card or driving licence; proof of address; the results of our checks and risk assessment, including sanctions and politically-exposed-person screening; beneficial owner details. Directors' PPSNs, where we file CRO forms for the company. | You; AML screening tools and public sources. |
| Supporting documents | Letters, accountant correspondence, IT records and similar evidence of why the return was late. These may include sensitive information such as medical certificates. | You. |
| Company filing information | Filing history, annual return dates, strike-off status, officers of the company. | The CRO public register and you. |
| Information about directors and shareholders | Names, addresses, dates of appointment, shareholdings and beneficial ownership shown on the CRO register and the Register of Beneficial Ownership. We may use it to prepare a compliance review or proposal for a company. | Public registers, you and your accountant. |
| Proposal and signature data | Your name, typed signature, IP address, the date and time you accepted a proposal, and information about when and how you open it. | You, and our proposal software. |
| Company records and post | Statutory registers we keep as company secretary, forms we file, and post (including letters from Revenue or the CRO) sent to the registered office when it is our address. | You, the CRO, Revenue and other senders of post. |
| Payment and invoice details | Amount, date, payer name, order reference, invoice details. We do not see or store full card numbers; card payments are handled by our payment provider. | You, our payment provider and our banks. |
| Communications | Emails, call notes, messages sent by contact form or WhatsApp. | You. |
| Website and technical data | IP address, browser and device type, pages requested, date and time, security and error logs. | Collected automatically when you use the website. |
| Court and CRO papers | The affidavit, application, notices and orders, which contain information from the categories above. | Prepared by us from the information you give us. |
The law requires us to have a "legal basis" for each use of your personal data. This table shows each purpose and its basis.
| What we do | Data used | Legal basis |
|---|---|---|
| 1. Reply to enquiries and free company-status checks. | Name, email, company name, your message. | Steps taken at your request before a contract (Article 6(1)(b) GDPR); our legitimate interest in answering enquiries (Article 6(1)(f)). |
| 2. Take your order and do the work: review your filing history, prepare the affidavit and application, notify the Registrar of Companies, attend court, deal with the CRO and lodge the court order. | Order details, company filing information, reason for late filing, supporting documents, court papers. | Performing our contract with you (Article 6(1)(b)). |
| 3. Verify identity and manage money laundering risk: due diligence, screening, monitoring, record-keeping and reporting. | Identity and AML documents, screening results, order and company details. | Legal obligation under the Criminal Justice (Money Laundering and Terrorist Financing) Act 2010, as amended (Article 6(1)(c)). |
| 4. Take payment, issue invoices, keep accounts and meet tax and company law duties. | Payment and invoice details, order reference. | Contract (Article 6(1)(b)) and legal obligation (Article 6(1)(c)). |
| 5. Use sensitive information you choose to send us (for example, a medical certificate) to support your application. | Supporting documents containing health or other sensitive data. | Your explicit consent (Article 9(2)(a)). You can withdraw it, but we may then be unable to rely on that document. |
| 6. Send service messages: order confirmation, payment instructions, requests for missing documents, progress updates. | Name, email, order details. | Contract (Article 6(1)(b)). |
| 7. Tell existing clients about similar services we offer. | Name, email. | Our legitimate interest (Article 6(1)(f)), with a right to opt out in every message. See section 5. |
| 8. Keep the website secure and working: prevent misuse, limit repeated form submissions, find and fix faults. | IP address, device and request logs. | Legitimate interests (Article 6(1)(f)). |
| 9. Handle complaints, bring or defend legal claims, and protect our regulatory position. | Any data relevant to the issue. | Legitimate interests (Article 6(1)(f)) and legal obligation (Article 6(1)(c)). |
| 10. Share information with authorities where the law requires it (see sections 6 and 7). | Whatever the law requires. | Legal obligation (Article 6(1)(c)). |
| 11. Prepare a compliance review or proposal for a company using public CRO and register information, and record your acceptance. | Information about directors and shareholders, proposal and signature data, order details. | Steps taken at your request before a contract (Article 6(1)(b)) and our legitimate interest in preparing accurate proposals and keeping proof of agreement (Article 6(1)(f)). |
| 12. Act as the company's secretary and registered office when needed for your application: keep statutory records, file forms with the CRO and handle post. | Information about directors and shareholders, company records and post, order details. | Performing our contract with you (Article 6(1)(b)) and legal obligation under company law (Article 6(1)(c)). |
| 13. Collect directors' PPSNs where we file CRO forms on the company's behalf. | PPSN, name, company. | Contract (Article 6(1)(b)). |
| 14. Use AI tools to help staff draft and check documents and correspondence, with a member of staff reviewing the result. | Order details, documents and correspondence, limited to what the task needs. | Contract (Article 6(1)(b)) and our legitimate interest in working efficiently and accurately (Article 6(1)(f)). |
| 15. Write to directors and contact persons of companies, using public information, about their filings and our services. | Name, role, business email address, company name. | Our legitimate interest (Article 6(1)(f)), with a right to opt out in every message, and consent where the law requires it. See section 5. |
Giving us the information in rows 2 to 4 is necessary for us to provide the service. If you do not provide it, or the identity documents we are legally required to obtain, we cannot act for you. We do not use automated decision-making or profiling that has legal or similarly significant effects on you.
We share personal data only where needed for the purposes above. Service providers act on our instructions under written contracts. We do not sell personal data. The table below shows the types of recipient. A current list of the named providers we use is in the Annex to this policy, and is also available on request.
| Recipient | Why | Notes |
|---|---|---|
| Our team | To deliver the service. | Staff and contractors, mainly based in Ireland and Slovakia, bound by confidentiality, with access limited to what they need. Team members may work or access our systems securely from other locations, including outside the EEA. The same security rules apply wherever they are. |
| Our other group company | Invoicing and running your order. | The Start Up Shop Limited and Office Pal Limited, where needed. |
| Solicitor and Commissioner for Oaths | To swear the affidavit and attend court on your behalf. | The solicitors we instruct for court applications. They act as independent controllers for the information they need to represent the company, under their own professional duties. |
| Courts and public bodies | To make the application and lodge the order; to meet legal duties. | The District Court; the Registrar of Companies / CRO (public register); Revenue; the Department of Justice AML Compliance Unit; An Garda Síochána. |
| Payment providers and banks | To take card payments and bank transfers. | Our card payment provider also acts as an independent controller for the payment and fraud data it collects. Our banks hold the details of bank transfers you make to us: Fire for Office Pal Limited, and Revolut for The Start Up Shop Limited. |
| Accounting and automation providers | To issue invoices, keep accounts, and pass order details between our systems. | Typically the invoice name, company name, amount and reference. |
| Email, storage and hosting providers | Email, document storage, and website hosting. | The website is hosted in the EU (Belgium). Order files are stored in the region set for our Google Workspace account (see section 8). |
| Proposal and e-signature provider | To send you proposals and record your signature. | The provider records your name, typed signature, IP address, date and time, and may record when a proposal is opened. |
| AML, document and team tools | Identity and AML checks, document generation, team coordination. | We choose tools carefully and do not post identity documents in chat tools. |
| Artificial intelligence providers | To help our staff draft and check documents and correspondence. | We give them only what the task needs and use providers whose terms do not allow them to train their models on our data. We use a business (Team) account, and a member of staff checks the output. |
| Messaging apps | If you contact us by WhatsApp or similar apps. | The app provider processes those messages under its own terms. |
| Advisers and insurers; a buyer of the business | Professional advice, insurance, audit, or a sale of the business. | Under duties of confidentiality. |
| Data | How long | Why |
|---|---|---|
| Enquiries that do not become an order | 12 months after the last contact | To follow up on your question. |
| Order records, correspondence, court and CRO papers | 6 years after the matter is completed | Contract and legal claim time limits; company and tax records. |
| AML records: identity documents, proof of address, risk assessments, screening results | At least 5 years after our relationship ends; longer if an authority directs | Legal obligation under anti-money laundering law. |
| Payment, invoice and accounting records | 6 years after the end of the financial year | Tax and company law. |
| Supporting documents containing health information | Returned to you or securely deleted when the matter closes. | Only kept as long as needed for the matter. |
| PPSNs | Until the filing is complete, plus 3 months. | Only used to file CRO forms for the company. |
| Marketing opt-out records | For as long as needed to respect your choice | To make sure we do not email you again. |
| Website server and security logs | 30 days | Security and troubleshooting. |
When these periods end we delete or anonymise the data securely. Deleted data can remain in backups for a short period (normally up to 30 days) before it is overwritten.
You have the right to:
To use any of these rights, contact us using the details in section 1.4. We may ask you to confirm your identity. We will reply within one month (we can extend this by up to two months for complex requests, and we will tell you if so). There is normally no charge.
Our website links to our other services and to third-party sites (for example RestoreMyCompany.ie, CloseMyCompany.ie and AnnualReturnWatch.ie). Each has its own privacy policy, and we are not responsible for third-party sites. Please read their policies before giving them your data.
We may update this policy from time to time. The latest version is always on this page with its date. If we make an important change, we will tell clients by email where we have their address.
We would like the chance to put things right, so please contact us first. You also have the right to complain to the Data Protection Commission, Ireland's data protection authority, at dataprotection.ie.
This list shows the named providers we use at the date above. We update it when our providers change. Providers act on our instructions under written contracts, except where stated.
| Provider | What it does for us | Where data may be processed | Safeguard for transfers outside the EEA |
|---|---|---|---|
| Google (Workspace, Drive, Gmail, Cloud) | Email, document storage, website hosting | EU (website hosted in Belgium; order files in Google Drive in our Workspace region); credentials and logs may be held outside the EU; support from other locations | EU-US Data Privacy Framework (Google is certified) and standard contractual clauses in Google's data processing terms |
| Stripe Payments Europe Limited | Card payments. Also an independent controller for payment and fraud data. | EEA and United States | EU-US Data Privacy Framework (Stripe is certified) and standard contractual clauses |
| Revolut Bank UAB (Irish branch) | Business bank account (The Start Up Shop Limited) that receives bank transfers from clients. Also an independent controller for the payment data it holds. | EEA (Revolut Bank UAB is licensed in Lithuania and acts through its Irish branch). Revolut group companies may process data in other countries. | Revolut Bank UAB is a bank licensed in the EEA. Safeguards for any transfers outside the EEA are set out in Revolut’s own privacy notice. |
| Fire Financial Services Limited (fire.com) | Business bank account (Office Pal Limited) that receives bank transfers from clients. Also an independent controller for the payment data it holds. | Ireland (EEA) | Not applicable. Fire is a payment institution authorised by the Central Bank of Ireland. |
| Xero | Invoicing and accounting | New Zealand, Australia, United States and other locations where Xero's teams and data centres are | Adequacy decision for New Zealand; standard contractual clauses |
| Zapier | Automation that passes order details to Xero | United States (Zapier has no EU-only option) | EU-US Data Privacy Framework (Zapier is certified), with standard contractual clauses as a fallback |
| Slack | Team coordination (no identity documents) | United States and other locations where Slack and its providers operate | Standard contractual clauses in Slack's data processing addendum; Slack also takes part in the EU-US Data Privacy Framework through Salesforce |
| AMLHQ | Anti-money laundering checks | Ireland (Microsoft Azure data centre in Ireland) | AMLHQ states that it does not transfer personal data outside the EEA; its data processing agreement forms part of its terms |
| Docupilot | Document generation | United States (hosted on Amazon Web Services) | Standard contractual clauses in Docupilot's data processing agreement |
| Anthropic (Claude) | AI assistance for staff drafting and checking | United States and other locations where Anthropic's providers operate | Data processing addendum in Anthropic's commercial terms, which includes standard contractual clauses |
| Reachinbox.ai | Sending emails to company directors about overdue filings | United States | Appropriate safeguards required by data protection law, such as standard contractual clauses |
| Better Proposals | Sending proposals and recording electronic signatures | Not stated by the provider; some of its providers are in the United States | Data processing agreement with the provider, and appropriate safeguards for transfers outside the EEA |
| WhatsApp (Meta) | Messages you choose to send us | EEA and other locations | Meta's own terms |
| Solicitors we instruct | Swearing the affidavit and attending court | Ireland | Not applicable |
See also our Terms and Conditions.