Seedmate privacy notice
Version 2.1
Seedmate helps businesses organise their records and work with the people they authorise. This notice explains how we handle personal information when you visit our website, register interest, contact us or use an available Seedmate service.
Our core accounting service and its primary data storage are hosted in the UK on Google Cloud. We do not sell customer records or use customer content to train or fine-tune AI models. Some functions, including email delivery and invoice intake, involve other providers and processing locations, as explained below.
Who is responsible
Seedmate is operated by Thoughtful Gestures Ltd, registered in England and Wales under company number 15633318. Our registered-office details are on our Company information page.
For privacy questions, requests or complaints, email contact@seedmate.uk with the subject “Seedmate privacy”. The same contact accepts security reports; please do not include passwords, access tokens or unnecessary personal information in your message.
We are the controller of information we use for our own website, enquiries, marketing choices, business relationships and proportionate service administration and security. This means we decide why and how we use that information.
For personal information in a customer's business records, the customer normally decides the purpose and we process the information on its documented instructions. Where an accountant acts as a processor for its client, we may act as a further processor in that chain. The applicable Data Processing Agreement sets out those responsibilities. Our contract does not change the role a party actually performs.
Information we collect and where it comes from
When you register interest, we collect your name, email address, whether you are joining as a business user or accountant, and any organisation name you choose to provide. We also record whether you request occasional development updates. Registering interest does not create a software account.
When you contact us, we receive your message and the information you choose to include. Please do not send account passwords, authentication codes, access tokens or financial documents in an initial enquiry.
For an invited software user, information can include identity and contact details, organisation memberships, permissions, verification and authentication records, terms acceptance, support requests and relevant security activity.
Depending on the functions a customer enables, its business records may include customer and supplier contacts; invoices, receipts and other source documents; bank and transaction information; stock and purchasing records; tax identifiers and filing evidence; integration identifiers and credentials; and people or payroll records where those functions are specifically made available. We only use the categories needed for the enabled service. Customers should not supply sensitive information that the relevant function does not require.
Business information comes from authorised users, documents and files they provide, connected services they authorise, and relevant public registers. We retain the source information needed to explain financial records. Your organisation is responsible for giving appropriate information to the people whose records it supplies.
Our website and service also process limited technical information such as request times, IP addresses, browser information, requested paths, security events and authentication results. The precise information depends on the activity and the safeguards involved. Our Cookies notice explains browser storage separately.
If you allow optional analytics, Google Analytics receives the public page or the type of app screen visited, the time of the visit and technical information needed to handle the request, including your IP address and browser information. We use these counts to understand use of Seedmate. You can withdraw your choice in the Cookies notice.
How we use information
| Activity | Purpose and basis when we act as controller |
|---|---|
| Registration of interest | To manage the early-access request and send the invitation or response you have asked for. We rely on our legitimate interest in answering requests and arranging access, after considering your interests. This is not permission for unrelated marketing. |
| Optional development updates | To send the occasional Seedmate updates you actively request. We rely on your consent and keep that choice separate from access to the service. |
| Account and relationship administration | To provide a service contracted with you personally where necessary to perform that contract; otherwise, our legitimate interest in administering our relationship with the organisation you represent. |
| Security, fraud prevention and support | Our legitimate interests in protecting the service, responding to problems and preventing unauthorised access; or a legal obligation where one applies. We use proportionate information and restrict access. |
| Our own contractual, accounting and tax records | To perform the relevant contract, comply with legal obligations, and pursue our legitimate interests in establishing or defending legal claims where necessary. |
| Customer business content | We act on the customer's documented instructions under the applicable processing agreement. The customer determines its own lawful basis. We do not treat its employees' acceptance of our user terms as blanket consent to processing their business records. |
You can ask us about a legitimate-interest assessment relevant to your information. We do not use the registration-of-interest process to make solely automated decisions with legal or similarly significant effects about you.
Early access and email choices
The registration-of-interest form sends your request securely to our team through our European email delivery provider. The request includes your development-update choice. Our team manages the enquiry in its business email system. The initial form does not open an account or enrol you in a paid subscription.
We may contact you about the early access you requested. Occasional development or feature updates are optional. You can withdraw that choice by using the withdrawal method provided in the message or emailing our privacy contact. Withdrawing optional marketing does not prevent necessary service, security or contractual messages once you become a user.
Seedmate's automated email delivery uses delivery, failure and complaint information to operate reliably. Its current sending configuration disables individual open and click tracking. We do not infer marketing permission from a service email or a cookie setting.
People and organisations receiving information
Our authorised team can receive information needed to handle enquiries, operate the service or provide support. Routine employment or platform administration does not itself authorise browsing customer books. Access to customer content is limited to the relevant authorised purpose, permissions and recorded support arrangements; infrastructure administration is separately restricted.
Google Cloud provides our core UK hosting and recovery infrastructure. We also use a European email delivery service for automated messages and customer-enabled invoice intake, and a business email provider for human correspondence. These providers receive the information needed for their particular service, including message content and attachments when email is used. A recipient's own email provider may also process a message we send to that recipient.
Customers may choose to share information with their accountant, colleagues, customers, suppliers or a connected service. We apply the available permissions and sending or connection controls. The recipient's own processing may be governed by its privacy notice.
Where necessary, information can be disclosed to professional advisers, insurers, courts, regulators or law-enforcement bodies. We assess the authority and scope of a request, disclose only what is required and notify the affected customer where lawful. A third-party request does not create unrestricted access to customer accounts.
The customer processing agreement identifies authorised subprocessors and the process for proposed changes. A list of provider functions, legal entities and relevant processing locations is available through that agreement or on request. Naming a supplier in that record does not give it permission to use customer content for an unrelated purpose.
Connected services and statutory filings
Connections are optional and available only for supported functions. The connection process explains which accounts and permissions are involved. Authorising a connection does not automatically authorise every possible action, a payment or a statutory filing.
For HMRC services using OAuth, you authenticate with HMRC and authorise access there. We use the resulting credentials to perform the functions you permit. For relevant Making Tax Digital services, we also send required fraud-prevention information about the device, browser, network and authentication associated with the request. The relevant connection flow explains this information. These security signals are not used for advertising. Other filing methods have their own stated authentication and information requirements.
Companies House interactions can use public-register information or information you authorise us to submit. Filing requires an available supported service and the appropriate review and authority. Integration test access does not mean every filing function is available or recognised.
For enabled commerce connections, we process the records needed for the agreed accounting function, such as sales, fees, settlements and inventory information. Access to individual buyer information is limited to supported, authorised purposes. Provider-specific retention and deletion rules apply in addition to our customer agreement. Disconnecting a service stops future retrieval through that connection; lawful handling of information already imported is addressed separately.
UK hosting and international processing
The core application, accounting database, document storage and recovery resources are hosted in the UK on Google Cloud. This describes our core hosting arrangement. Email processing, recipients' systems and some supplier support, account administration or security metadata can involve locations outside the UK.
Where a restricted international transfer occurs, we must have a lawful transfer route. Depending on the recipient and circumstances, this may be UK adequacy arrangements or appropriate contractual safeguards, such as the UK International Data Transfer Agreement or the EU standard clauses with the UK Addendum, together with any required assessment and additional measures. Contact us for details of the safeguards applicable to your information.
How we protect information
Our safeguards include encrypted storage, secure connections, restricted credentials, separation between customer organisations, appropriate access permissions and controlled recovery. Original evidence and corrections are recorded so financial information can be explained. We review safeguards as the service changes.
Authorised systems need to process information to provide the service. Our encryption is not a promise that only the customer can ever decrypt its data. Our Security and hosting page describes the current approach in more detail.
We do not sell or rent customer records, build unrelated advertising audiences from them, enrich data-broker or insurer profiles, or pool them for unrelated cross-customer intelligence. We do not use customer content to train or fine-tune AI models. Any external AI processing of customer content requires a defined purpose, suitable provider arrangements and the customer's applicable instructions; the presence of an AI feature does not authorise unrelated reuse.
How long we keep information
We use retention periods or decision criteria appropriate to each category, rather than keeping every kind of record for the same period.
| Record | Retention approach |
|---|---|
| Early-access requests | Until the requested invitation or enquiry and necessary follow-up are complete, you withdraw the request, or the relevant early-access programme ends. We then delete or anonymise the request details unless a continuing relationship or identified legal need requires a limited record. Outstanding requests are reviewed to check that this purpose still applies. |
| Optional-update details | While the subscription remains active and relevant to the purpose explained at sign-up. Withdrawal stops further optional messages. We retain a minimal suppression record where needed to prevent sending again. |
| Consent and agreement evidence | For the relevant relationship and the period needed to demonstrate the applicable choice or agreement, respond to a complaint or deal with a legal claim. We restrict this evidence to that purpose. |
| Support and ordinary correspondence | Until the matter and reasonable follow-up are complete, with longer retention only for a continuing relationship, specific dispute or applicable legal requirement. |
| Security and delivery records | For the operational review period needed to reconcile message delivery, investigate faults and detect security incidents. The review period depends on the system, the checks it supports and whether an incident or dispute remains open. Relevant incident records may be kept until the investigation, necessary remedial work and any resulting reporting or legal requirement are complete. |
| Our own billing and statutory records | For the period required by the applicable accounting, tax or other law. This does not justify retaining every customer's entire dataset for that same period. |
| Customer business records and backups | Under the processing agreement and the customer's documented retention and exit instructions, including applicable provider rules, explained legal exceptions and the verified backup-expiry schedule. These arrangements are supplied before service content is accepted. |
Removing a queued email payload does not remove the delivered message from a recipient's mailbox. We address the application's copy, provider copies and our business-mailbox copies separately. We can explain the applicable retention arrangements on request.
We preserve the audit history needed for valid accounting records without treating that requirement as a blanket refusal to delete personal information. Correction, deletion or restriction is handled according to the applicable law, customer instructions and the nature of the record. Restoring a backup must not silently reinstate revoked access or reverse an applicable deletion instruction.
Your rights and complaints
Depending on the circumstances, you can request access, correction, erasure, restriction or portability of your information, object to processing based on legitimate interests, and withdraw consent. Withdrawal does not affect processing that was lawful beforehand. Rights have legal conditions and exceptions; we explain any relevant restriction.
You are not required to register interest or request marketing. The required form fields are needed to handle an early-access request. If you do not provide information necessary for account verification or the service you request, we may be unable to provide that function.
Contact our privacy address above. We may ask for proportionate information to verify identity. For information controlled by your business, contact that business; we assist it under the applicable agreement and will help direct a request received by us.
We acknowledge data-protection complaints within 30 days, investigate and keep you informed, and communicate the outcome without undue delay. Individual-rights requests follow their own applicable statutory time limits. You can also complain to the Information Commissioner's Office.
Changes to this notice
We date changes and explain material changes in an appropriate way before a new purpose applies. A revised privacy notice does not itself provide consent for an unrelated purpose. A change of product ownership does not authorise unrelated reuse of customer records.
