FilingPing: Privacy Notice
Last updated: 1 October 2026
This notice explains what personal data we collect when you use FilingPing (the Service), why we collect it, who we share it with, how long we keep it, and your rights. It is written to meet Articles 13 and 14 of the UK GDPR.
1. Who we are
The controller of your personal data is Craig Hallsworth, a sole trader trading as FilingPing, First Floor, Swan Buildings, 20 Swan Street, Manchester M4 5JW. Email: support@filingping.co.uk.
ICO registration number: ZC252957.
We are not required to appoint a Data Protection Officer. For any privacy question or request, email support@filingping.co.uk.
2. The short version
- We collect as little as we can: your email address, a scrambled (hashed) copy of your API keys, the companies you watch and any labels you give them, your alert destinations (webhook and Slack URLs), and billing information from Stripe/Onelink if you buy a paid plan.
- We never see your full card number.
- We do not store the names, addresses or dates of birth of company directors or other officers, or of persons with significant control.
- Our website and API set no cookies and use no analytics or tracking.
- Event data is deleted after 90 days. Your account data is deleted when you delete your account.
3. What we collect, why, and our lawful basis
| Data | Where it comes from | What we use it for | Lawful basis (UK GDPR Art. 6(1)) |
|---|---|---|---|
| Email address | You, when you sign up | Sending your API key, the daily digest, service notices (for example, a paused alert destination, an inactive-account warning, a plan-change confirmation, or a one-off reminder if you have not added a company yet) and replies to your messages; identifying your account | Contract (b): we need it to provide the Service |
| API keys, stored only as a one-way SHA-256 hash plus a short prefix, with when each key was created, last used and revoked | Generated by us | Checking your requests come from you; key management and security | Contract (b); legitimate interests (f): security |
| Watchlist: company numbers, optional labels, the date each was added, and whether it is paused | You | Monitoring those companies and telling you about changes | Contract (b) |
| Alert destinations: webhook URLs (including Slack incoming-webhook URLs), signing secrets, which event types you want, and delivery status (attempts, errors) | You and our systems | Delivering and retrying alerts, and pausing destinations that keep failing | Contract (b) |
| Terms acceptance and settings: when you accepted our terms and which version; your email digest settings | You | Showing which terms you accepted; sending the emails you have chosen | Contract (b); legitimate interests (f): being able to show which terms applied |
| Billing references: Stripe customer ID, subscription ID, subscription status, current period end date and plan | Stripe | Knowing which plan you are on, preventing double charging, and reconciling billing | Contract (b); legitimate interests (f): keeping accurate business records; legal obligation (c) where tax law requires us to keep them |
| Order information from Stripe/Onelink: name, email, billing address and country, any tax ID you give, payment information (never your full card number), and order, subscription, refund and dispute details | Stripe/Onelink, when you buy a paid plan | Providing your plan, answering billing questions, handling refunds and disputes, and keeping business and tax records | Contract (b); legal obligation (c) for tax records; legitimate interests (f) for handling disputes |
| Account records: signup date, when your account was last active, when your last key email was sent, which days a digest was sent, and an audit log of plan changes and account deletion (by account number) | Our systems | Running the Service, preventing duplicate emails, closing inactive free accounts, investigating billing problems and disputes | Legitimate interests (f): running a reliable service and dealing with disputes |
| IP address | Your device, when you use the signup form, signup API or free company check | Limiting how many signups and company checks can come from one address, to stop abuse | Legitimate interests (f): preventing abuse, protecting our email reputation and staying within Companies House usage limits |
| Messages you send us (support, complaints, requests) | You | Answering you and keeping a record | Legitimate interests (f); legal obligation (c) for data protection complaints and rights requests |
| Technical logs: error messages, which may include account or Stripe reference numbers | Our systems | Finding and fixing faults, and security | Legitimate interests (f): keeping the Service working and secure |
Legitimate interests. Where we rely on legitimate interests, we have judged that the use is expected, limited and low-risk, and that it does not override your rights.
Do you have to give us your data? You need an email address to use the Service. Without it we cannot send your API key. Labels are optional.
No marketing, and no automated decisions. We do not send marketing emails, and we do not make decisions about you by automated means that have legal or similarly significant effects.
Please do not put personal data in labels or webhook URLs. Use company names or your own reference codes.
4. Companies House data: about companies, not about people
The Service is built on public data from Companies House, used under the Open Government Licence v3.0. We deliberately keep company-level information only: company number, company name, status, whether accounts or the confirmation statement are overdue, and basic filing details (category, type, description code and dates). We do not collect or store the names, addresses or dates of birth of directors, other officers or persons with significant control. An alert about an officer or PSC filing says only that a filing of that type was made.
A company name can sometimes include a person's name (for example, "J Smith Plumbing Ltd"), and a small company can be closely linked to one person. Where company-level information does relate to an identifiable individual, we process it only as part of the public company record, to tell our customers about changes to companies they watch, and to show a summary of a company's public record to anyone who looks it up with our free company check (we keep that summary for up to an hour, to avoid repeat requests to Companies House). Our lawful basis is legitimate interests (f): helping businesses manage credit and supplier risk using information that is already public. Companies House is the source. The recipients are our customers who watch the company (and the alert destinations they choose), and our service providers in section 5. We keep events for 90 days. We keep a snapshot of each watched company's current name and status so that we can detect changes, and delete it once no customer has watched the company for 90 days. You have the rights in section 9, including the right to object, and you can complain to us or the ICO (sections 10 and 11). Because we do not hold contact details for these individuals, it would be impossible or would involve disproportionate effort to contact them individually, so we publish this notice instead.
5. Who we share data with
We do not sell your data. We share it only with these service providers and recipients:
| Recipient | Role | What they receive | Where |
|---|---|---|---|
| Render Services, Inc. (hosting and database) | Processor, under Render's data processing addendum | Everything we store (it runs our servers and database) | Our servers and database are in the EU (Frankfurt, Germany). Render is a US company and uses sub-processors, so some access or support may take place in the US |
| Resend (transactional email) | Processor, under Resend's data processing addendum | Your email address and the content of emails we send you (API key email, digests, service notices) | EU (Ireland). Resend is a US company, so US-based staff or sub-processors may have access; see section 6 |
| Stripe, including Sold through Link, LLC ("Onelink") (payments; merchant of record) | Independent controller | We send Stripe your email address and account number when you start checkout. Stripe collects your payment details directly, and shares order information with us (see section 3). We can see that information in our Stripe account; our own database stores only the reference numbers listed in section 3 | United States and elsewhere. See https://onelink.com/privacy and https://stripe.com/privacy |
| Cloudflare, Inc. (domain name services and email forwarding) | Processor | Emails you send to support@filingping.co.uk (address, subject and content), which Cloudflare forwards to our mailbox; and it may handle requests to our website, including your IP address | Global network, including the United States |
| Google (our support mailbox, Gmail) | Service provider | Emails you send to support@filingping.co.uk and our replies; our internal alert emails, which may include account or Stripe reference numbers | United States and elsewhere |
Destinations you choose. If you set up a webhook or Slack alert, we send alert data (company number, your label and event details) to the address you give us. The recipient (for example Slack) handles it under your own arrangement with them.
We may also disclose data where the law requires it, to protect our legal rights, or to a buyer if the Service is sold (and we would tell you).
Companies House is our data source, not a recipient. We do not send your personal data to Companies House. It receives ordinary API requests about company numbers. If you use name matching (uploading company names so we can find their company numbers), it also receives the names you ask us to look up, as search requests. If a name you upload is a person's name (for example a sole trader's business name), that search is the only use we make of it, and we keep only the names of the companies you choose to watch, as your labels.
6. International transfers
- EU/EEA (Render's Frankfurt region; Resend's Ireland region): UK adequacy regulations cover the EU/EEA, so no extra safeguards are needed for data stored there.
- United States: Stripe/Onelink, Google and Cloudflare, and US-based staff or sub-processors of Render and Resend, may process your data in the US. For providers certified under it, we rely on the UK Extension to the EU-US Data Privacy Framework (the "UK-US data bridge": the Data Protection (Adequacy) (United States of America) Regulations 2023). Where a transfer is not covered by it, we rely on the provider's data processing terms, which include the EU Standard Contractual Clauses with the ICO's International Data Transfer Addendum. You can ask us for details of these safeguards at support@filingping.co.uk.
7. How long we keep data
| Data | How long |
|---|---|
| Account (email, plan, Stripe references, signup date, terms acceptance, settings) | Until you delete your account (or we close it). Free accounts that have never had a paid subscription and have not been used for 12 months (no sign-in to our account page and no API requests) are deleted after we email a warning and the account stays unused for a further 30 days. Receiving our daily email does not count as use. Accounts that have had a paid subscription are kept until you delete them |
| API key hashes and key records | Until you delete your account |
| Watchlist and labels | Until you remove the company or delete your account |
| Alert destinations (webhook and Slack URLs) and secrets | Until you delete the destination or your account |
| Company change events, and delivery records (including error messages) | 90 days after we receive the event, then deleted automatically. Deleted sooner if you delete your account |
| Company snapshots (name, status, overdue flags) | While any customer watches the company; deleted automatically once no one has watched it for 90 days |
| Record of which days a digest was sent | Until you delete your account |
| Audit log (account number, plan changes, Stripe subscription ID, account deletion) | 6 years, then deleted automatically |
| Record of Stripe notifications (event reference and type) | 2 years, then deleted automatically |
| IP addresses used for rate limiting | Held only in server memory, not written to our database or our application logs. Cleared when the server restarts, and periodically pruned |
| Technical logs held by our host | 7 days on our current Render plan |
| Database backups held by our host | Up to 7 days, then overwritten |
| Emails held by Resend, including content | 30 days in Resend's logs (Resend's current retention for our plan) |
| Support messages and complaints | 2 years after the matter is closed |
| Order information in our Stripe account | 6 years, for tax and accounting records. Stripe/Onelink also keep it under their own policies, and we cannot always delete it from Stripe ourselves |
When you delete your account through DELETE /v1/account, we immediately delete your account, API key hashes, watchlist, labels, alert destinations, delivery records and digest records. We keep a record that the account (by number only) was deleted in our audit log. Copies may remain in email and hosting logs and backups for the periods above. Stripe and Onelink keep their own payment records; you can ask them to delete data as their privacy notices describe.
8. Cookies
Our website (https://filingping.co.uk) and API set no cookies and use no tracking technologies, analytics or third-party scripts. Our account page keeps your API key only in the open page, not in your browser's storage. Stripe's checkout pages are run by Stripe/Onelink and may use their own cookies, as their privacy notice explains.
9. Your rights
You have the right to:
- access a copy of your personal data;
- rectification: have inaccurate data corrected (for example, your email address);
- erasure: have your data deleted (you can do this yourself with
DELETE /v1/account); - restriction of how we use your data in some circumstances;
- object to processing based on legitimate interests;
- data portability: receive the data you gave us in a machine-readable format (you can also export your watchlist through the API);
- withdraw consent, where we rely on consent (we do not at present).
Your right to object. Where we rely on legitimate interests (sections 3 and 4), you can object at any time on grounds relating to your situation. We will stop unless we have compelling legitimate grounds, or need the data for legal claims.
To use a right, email support@filingping.co.uk. We may need to confirm that the request comes from the account holder, for example by replying to your account email address. We will respond without undue delay and within one month. The month starts when we receive your request or, if later, when we receive information we reasonably need to confirm your identity. If we need you to clarify your request, the time limit pauses until you reply. We can extend it by up to two further months if the request is complex or you have made several requests. If we do, we will tell you why within the first month.
10. Your right to complain to us
You have the right to complain to us if you think we have not handled your personal data in line with data protection law (section 164A of the Data Protection Act 2018). You can complain:
- by email to support@filingping.co.uk, ideally with the subject line "Data protection complaint"; or
- by post to FilingPing, First Floor, Swan Buildings, 20 Swan Street, Manchester M4 5JW.
We will acknowledge your complaint within 30 days of receiving it (we aim to do so within 5 working days). We will look into it without undue delay, keep you informed of progress, and tell you the outcome. Complaining to us does not affect your right to complain to the ICO (section 11).
11. Complaints to the ICO
You also have the right to complain to the Information Commissioner's Office: https://ico.org.uk/make-a-complaint/, telephone 0303 123 1113. The ICO usually expects you to have raised the complaint with us first.
12. Security
We store only a hash of each API key. We accept webhook URLs only over HTTPS, we block private network addresses, and we sign every webhook. Data is encrypted in transit. Access to our systems is limited to the operator. If a breach is likely to put your rights at risk, we will tell you and the ICO as the law requires.
13. Changes to this notice
We will post any changes here and update the date at the top. If a change is significant, we will email you before it takes effect.