Who we are
Capduo Holdings Limited, trading as Fieldwell, is responsible for the personal information used to operate the Fieldwell household application. Our company number is 15700435 and our registered office is Henwood House, Henwood, Ashford, Kent TN24 8DH, United Kingdom.
Contact [email protected] for privacy questions, complaints or rights requests. This notice covers app.fieldwell.money and associated account, subscription and service communications. The separate website notice covers public-site visits, enquiries and the website support assistant.
These notices are not permission to use information for unrelated purposes. Accepting a subscription is not consent to marketing or to connecting a bank.
Information and purposes
| Information | What we use it for |
|---|---|
| Name, email, identity-provider identifiers and account details | Sign-in, account administration and communication |
| Session, verification, passkey and security-event information | Authentication, account recovery and abuse prevention |
| Household membership, invitations and permissions | Sharing the correct records with the correct people |
| Financial records, balances, holdings, transactions, income, spending, liabilities and assumptions | The records, calculations, charts and plans you request |
| Documents, extracted content and reviewed suggestions | Requested extraction, evidence storage and record preparation |
| Subscription, invoice, payment-status and provider references | Subscription access, receipts, reconciliation, refunds and disputes |
| Support messages and delivery status | Answering requests and delivering important service communications |
| Browser/device details, IP addresses and operational metadata | Security, reliability and troubleshooting |
Information comes from you, authorised household members, chosen identity and bank providers, documents you upload and the corrections or records you save. Records may include other people, such as dependants, tenants, borrowers or company officers. Only add information you are entitled to share and make this notice available to those people where appropriate. Your responsibility to share information lawfully does not remove ours.
Avoid unnecessary sensitive information. Financial records can reveal sensitive matters, including health or religious beliefs. Do not include these where they are not needed; contact us about removing material or handling a particular request if necessary.
Lawful bases and choices
We use information necessary to perform our contract with you to operate the account and provide requested household tools, calculations and paid access. This does not automatically make a non-user relative or counterparty a party to your contract.
We rely on legitimate interests for proportionate security, fraud prevention, reliability, support, claims handling and necessary administration of shared records, balancing these purposes against the rights of affected people, particularly children. We use information required by an applicable legal obligation for accounting, legal and regulatory purposes.
Optional marketing requires a separate choice. It is not a condition of an account or subscription. Requested bank access uses the provider's explicit authorisation flow; that authorisation is not blanket consent to unrelated use of your financial information.
Optional AI processing is undertaken when you request the relevant feature. Manual alternatives remain available. We do not treat acceptance of these terms as unrestricted permission to send every household record to an AI provider.
You can decline optional functions. A function cannot operate without the information genuinely necessary for it, but unrelated parts of your account are not conditional on optional marketing or a bank connection.
Sharing within a household
People with household access can see or change records according to their role. The household is not a guarantee of per-person secrecy. Check permissions before inviting a partner, family member or adviser, particularly where records concern joint accounts, companies or dependants.
Revoking someone's access stops future platform access through that permission. It cannot recall a copy they have already lawfully received. A professional adviser's own processing may be governed by their separate notice and obligations; these consumer terms do not establish a professional reseller arrangement.
Sign-in, bank data and payments
Chosen sign-in providers can supply an identifier, email and available profile information. With passkeys, Fieldwell stores public credential information and verification metadata, not your fingerprint, face template or device PIN.
Bank access, where available, is authorised through TrueLayer's hosted dialog. The requested categories can include name, account details, balances, transactions, direct debits and standing orders. Review the actual categories and duration shown before authorising. Access tokens are used to perform authorised requests; Fieldwell support does not need your bank password.
The UK provider's end-user terms and privacy information explain its own processing. Connecting a bank is separate from subscribing to Fieldwell. Disconnecting stops future collection through that connection, subject to requests already in progress, but does not automatically delete imported records.
Stripe processes checkout and payment-method information. Fieldwell records subscription, customer, payment and invoice references and the payment status needed for access and support. Stripe also processes data for its own payment, fraud-prevention and legal responsibilities. Payment documents come through Stripe. Core subscription invoices, payments and annual revenue recognition are processed in Zoho Books; exceptions and adjustments may require manual reconciliation. Household closure does not automatically delete financial records retained for accounting and legal obligations.
Service providers
We use the following providers or categories for the relevant functions, not as permission to send all data to every provider:
- DigitalOcean: application and database hosting.
- Cloudflare: network delivery, security and relevant hosted functions.
- Backblaze: encrypted independent recovery storage.
- Better Stack: service monitoring and operational alerts.
- Resend: transactional emails and delivery information.
- Google and Apple, where selected and enabled: sign-in.
- Twilio, where an SMS function is enabled: requested verification messages.
- TrueLayer and your chosen bank: authorised account-information access.
- Wise, where a direct connection is selected: the requested account data.
- Perplexity API: selected AI extraction or explanation requests.
- Stripe: subscription payments, invoices, receipts and payment management.
- Zoho Books: business accounting and reconciliation.
- Professional advisers or authorities: justified accounting, legal, complaint or regulatory purposes.
Providers may act on our instructions for some activities and under their own responsibilities for others, particularly identity, banking and payments. Their own notices describe those independent activities. We do not sell household financial records for advertising.
International processing
The application hosting is configured in DigitalOcean's London region. That does not mean every database recovery, email, support, payment or AI operation stays in the UK. Relevant provider processing can include the UK, EEA, United States and other countries in their current subprocessor lists.
The following published provider terms explain the transfer arrangements for their services. They distinguish adequacy routes, where applicable, from contractual safeguards for restricted transfers:
- Hosting: DigitalOcean's DPA provides applicable Data Privacy Framework routes and contractual fallback clauses, including a UK Addendum.
- Network/security: Cloudflare's DPA provides UK contractual safeguards for restricted transfers; its subprocessor list describes the relevant providers and locations.
- Email: Resend's DPA identifies primary processing in the United States and UK SCC/Addendum safeguards. Its subprocessors are listed separately.
- Payments: Stripe's transfer addendum incorporates UK transfer safeguards for the relevant controller/processor transfers. Stripe also has independent payment and legal responsibilities.
- AI: Perplexity's API terms incorporate its DPA, including UK transfer clauses. Its subprocessor list identifies the relevant processing providers; a legal reference to Irish courts does not mean all processing occurs in Ireland.
- Encrypted backups and monitoring: Backblaze's UK/EEA notice and Better Stack's DPA describe applicable international-transfer routes and onward-transfer protections.
- Accounting: our Zoho Books account uses the EU service. Zoho's UK notice nevertheless describes processing across the EEA, US and other operating countries; an EU account is not a promise of EU-only support or processing.
- Banking and SMS: the TrueLayer notice describes primarily UK/EEA storage and safeguards for other transfers; Twilio's DPA describes the protections for relevant messaging services.
Provider terms are not a claim that every available region or subprocessor is used for every Fieldwell request. For a particular processing activity, contact [email protected] for the applicable provider, destination and safeguards or a copy of relevant clauses, subject to necessary redactions. We must assess and maintain the safeguards applicable to our actual transfers; a supplier's general security claim is not a substitute for that responsibility.
AI, calculations and decisions
An AI request may include selected document text, the instructions needed for that task and relevant context. Review what you submit and avoid unrelated pages or identifiers. We do not promise that provider processing has zero retention or no training use unless that is established for the particular service.
Suggestions can be wrong. Financial changes require the supported review/apply step; this notice is not permission for an AI model to move money or make an investment decision for you. Calculations use the inputs and assumptions relevant to the requested result.
Retention and deletion
We retain information for the purpose for which it is needed, not indefinitely merely because it was collected.
- Account and household records: while needed to provide the account and requested record history, subject to closure, deletion requests and justified exceptions for shared rights, security, law or claims.
- Authentication and temporary processing: for the session, verification, processing or review window for which the record was created. Temporary material and evidence you deliberately save are treated differently.
- Support and security records: for the request, investigation or protection purpose and any necessary follow-up or claims period; unnecessary financial content should not be included in routine diagnostics.
- Invoices and business records: for applicable accounting, tax and legal obligations and relevant claims periods. These obligations do not justify retaining every household document.
- Recovery copies: protected backups are separate from live records. The independent backup retention setting is 30 days; managed database recovery and provider copies have their own arrangements. Closure is not a promise that all backup/provider copies disappear immediately.
- Communication preferences: sufficient information to honour your choice and prevent unwanted marketing.
The automatic expiry policy applies only to new households admitted after its rollout whose owner accepted the matching Terms and this Privacy Notice at signup. Pre-existing households are not automatically included. Your Billing page explains when the policy applies.
For eligible households, the period is 30 days after trial or paid access ends, not after a cancellation request. We send the owner five-day and one-day warnings and preserve both full intervals after confirmed delivery. Delayed delivery extends the deadline; failed or unverified delivery, unresolved payments and relevant holds prevent automatic deletion. You can export, deliberately close the household or complete a subscription before the deadline.
Once eligible household records are deleted and the completion email is delivered, the original owner's unused sign-in is also removed. This removes its authentication credentials and sessions and scrubs direct profile details; a pseudonymous record may remain where needed to preserve retained evidence. An identity still needed by another household, pending membership, adviser access, another household's financial records or unresolved processing is preserved for review. Other registered members' sign-ins are not automatically removed; they can make separate requests about their personal data.
Deliberate household closure offers a separate, optional unused-sign-in choice. You can request deletion and use available owner-only closure controls without waiting for the automatic timer. Accounting, security, provider and protected backup records remain subject to their separate justified retention and disposition rules; neither household closure nor sign-in removal means every copy everywhere has immediately disappeared.
Deleting a household is different from deleting a global sign-in identity, another household's records or copies held by independent providers. Export before confirming irreversible closure. We will explain a justified retention exception rather than represent a partial deletion as complete erasure.
Cookies and browser storage
The app uses essential sign-in and security cookies. The current customer sign-in
uses fieldwell_secure_session for up to eight hours, fieldwell_auth_flow for
up to 15 minutes, and fieldwell_oauth_bind for up to ten minutes during the
relevant sign-in flow. Invitation and bank-authorisation flows also use temporary
security state.
Browser storage can remember interface choices such as hidden monetary values or chart ranges and coordinate household changes. Clearing it may reset those choices. Identity and payment providers explain their own technologies on their pages. The separate website notice covers its cookie controls; this notice does not authorise advertising trackers in the app.
Rights, complaints and changes
Depending on the circumstances, you can request access, correction, erasure, restriction, portability, or object to processing. You can withdraw a consent where processing relies on it without invalidating earlier lawful processing. Some rights are subject to legal limits or other people's rights.
Write to [email protected]. We may ask for proportionate verification and will explain any lawful limitation or extension. The usual response period for a rights request is one calendar month; a privacy complaint has a separate acknowledgement process.
We will acknowledge a data-protection complaint within 30 days, investigate it appropriately and respond without undue delay. You can also contact the Information Commissioner's Office.
The sign-in service is for adults. Authorised adults may maintain relevant dependent records; this does not create a child's login or remove our obligations to protect information about children.
We will explain material changes to this notice and new processing purposes where required. A later wording change is not retroactive permission for an unrelated use of your data.