Privacy Policy

PurpleDue is a trading name of Cletus Osei-Kwame, a sole trader based in Scotland, United Kingdom. “PurpleDue”, “we”, “us”, and “our” refer to that sole trader. PurpleDue is not a registered company, is not incorporated, and is not VAT-registered.

This policy covers information processed through the PurpleDue web application at purpledue.com, including its public marketing pages, sign-up and sign-in, the invoice-handoff mailbox, and the authenticated product. It applies to information about you as a PurpleDue account holder, and to information about your own clients or customers that you choose to hand off to PurpleDue (see “Information about your clients” below).

Account information. The email address you sign in with (this is also how you authenticate — PurpleDue uses passwordless “magic link” sign-in, so we do not hold a password for your account); your name and, optionally, your business/trading name, collected during setup; the date you completed setup; a private, randomly generated inbound email address created for your account; and your subscription status (see “Payments”).

We deliberately do not currently ask for or store your business type, country, phone number, postal address, VAT number, company number, industry, revenue, employee count, or bank details.

Sender addresses. Any additional email addresses you choose to register as trusted senders for your account, so we know which incoming emails to accept as genuinely from you.

Invoices you hand off, once confirmed by you. Client/customer name, client/customer email address, invoice number, invoice date, due date, currency, original amount, and current outstanding amount; the invoice document itself (the PDF you sent or forwarded); a record of what happens to that invoice over time (follow-ups prepared and marked as sent, notes you add, pauses/“snoozes”, and — where relevant — the Resolution and Formal Payment Request history described on the product page).

Invoice documents you hand off, before you confirm them. When an invoice email first arrives, PurpleDue also holds, separately from the confirmed fields above: the raw sender/recipient email addresses on that message, and whatever an automated reading of the PDF returned before you reviewed it. This raw, unconfirmed data is never treated as accurate until you confirm it (see “AI-assisted extraction” below).

PurpleDue's data-protection role depends on which information is involved. For account and authentication information, subscription and billing metadata, security and fraud-prevention records, service administration, and product analytics and operational records, PurpleDue acts as the controller — we decide why and how that information is processed.

For invoice, receivable, and client/customer personal data you submit for receivables-management purposes, PurpleDue processes that information as a processor, acting on your instructions as the controller of your own client's information, except where PurpleDue independently determines a separate purpose of its own (for example, using invoice-document data to detect abuse of the invoice-handoff mailbox, or for the security and service-administration purposes described above).

When you hand PurpleDue an invoice, you are giving us personal and business information about your own client or customer (typically their name, email address, and the amount they owe you) so that PurpleDue can track and help you follow up on it. You are the one who decides to share that information with us, and you are responsible for having a lawful basis to do so (for example, because it is necessary to pursue payment for a contract you already have with that client).

You hand off an invoice by BCCing or forwarding it to your own private PurpleDue address. That email is received by our email-infrastructure provider, Resend, which passes PurpleDue a notification and lets us fetch the message and its attachment.

• We only accept invoices from an email address you have specifically registered as trusted for your account (your own sign-in email is registered automatically). An email from an address we do not recognise is not processed as an invoice — we keep a record that it arrived and was rejected, rather than silently discarding it or creating anything from it.
• We look for a single PDF attachment. If there is no attachment, more than one possible invoice PDF, or the file is not readable, nothing is created automatically — you can still enter the invoice by hand, referencing the file if one was stored.
• We currently store the PDF attachment; we do not separately store the plain-text body of the email itself. The raw sender and recipient addresses on the message are kept as part of the invoice record described above, for traceability and to help pre-fill your client's email address for you to confirm.

To save you re-typing an invoice, PurpleDue sends the invoice PDF you hand off to Anthropic's API (the Claude Sonnet 5 model) so it can attempt to read out the client name, client email, invoice number, amount, currency, issue date and due date. The complete PDF is sent for this purpose — not a summary or an excerpt.

This is extraction only, not a decision: the model is instructed to leave a field blank rather than guess, and nothing it returns is treated as accurate or acted on until you personally review and confirm it (or correct it) on the confirmation screen. If extraction fails or times out, you can still enter the invoice by hand.

Invoice documents may be transmitted to Anthropic for this extraction step. Anthropic states that inputs and outputs from its commercial API products are not used to train its models by default.

We use the information above to:

• let you sign in and operate your own account;
• receive, read, and let you confirm invoices you hand off;
• track each receivable's status, prepare follow-up drafts for you to review and send, and calculate the UK statutory information described on the product page;
• process your subscription and billing, once applicable;
• understand, in aggregate, how the product is used so we can improve it (see “Analytics”); and
• keep the service secure and prevent misuse of the invoice-handoff mailbox.

Legal basis (UK GDPR). For account holders, processing is generally necessary to perform our contract with you (providing the service you signed up for) or is a necessary step before entering into that contract. Security-related processing (such as rejecting unrecognised senders) is carried out under our legitimate interest in keeping the service safe and reliable. We do not rely on consent as the basis for the core service, since it would not be genuinely optional and still let the product work.

PurpleDue is built on a small number of specialist providers, each used only for the function named below — we do not sell or share your information for anyone else's marketing purposes.

• Vercel — hosts and runs the PurpleDue application itself.
• Supabase — our database, sign-in system, and private file storage (EU region — see “International processing”).
• Resend — delivers sign-in emails and receives the invoices you BCC or forward to your PurpleDue address.
• Anthropic — reads invoice PDFs to help pre-fill invoice details, as described above.
• PostHog (EU) — records anonymised product-usage events, described under “Analytics” below.
• Stripe — handles subscription billing and payment card details; see “Payments”.

No other external provider currently receives PurpleDue account or invoice data.

Subscription payments are handled entirely by Stripe. When you subscribe, you enter your card details directly with Stripe — PurpleDue never receives, sees, or stores your full card number or other card details. What we store on our side is limited to your Stripe customer reference, your subscription reference, and your current subscription status (for example, active, cancelled, or past due), so we can tell whether new invoices can currently be admitted.

We use PostHog, hosted in the EU, to record a small, fixed set of product-usage events — for example, that an invoice was confirmed, a follow-up was reviewed, or a Resolution case was started — together with simple counters and categories (such as how many invoices an account has confirmed, or how many days a receivable has been overdue). This runs on our own servers, not in your browser: PurpleDue does not use any client-side analytics or advertising-tracking script.

These events never include your client's name or email address, an invoice number, an amount, or any content from an invoice PDF. This is enforced by routing every analytics event through one shared piece of code whose data shape simply cannot carry those fields — not only a house rule.

PurpleDue only sets the cookies needed to keep you signed in (issued by our authentication provider, Supabase). We do not set analytics, advertising, or cross-site tracking cookies, and our analytics runs server-side rather than through your browser. Because the only cookies in use are strictly necessary for the service to function, we do not currently show a cookie-consent banner. If that changes — for example, if we ever add browser-based analytics or advertising — we will update this section and add appropriate consent controls first.

We apply a number of concrete technical safeguards:

• Your account's data is isolated at the database level, so it is only ever readable by your own signed-in session — not merely hidden in the interface.
• Invoice PDFs are stored in a private file store with no public web address. When you view your own invoice PDF in the app, we generate a link that only works for a few minutes and only for you.
• We check that anything submitted as an invoice attachment is genuinely a PDF before storing or processing it.
• Provider API keys and other secrets are held only on our servers and are never included in the code sent to your browser.
• Error messages shown to you are generic by design — technical details are logged privately on our side, not displayed to you or to anyone else.

No online service can guarantee complete security, and we do not claim “bank-grade” security, formal certification, or that any particular standard has been independently audited. During this beta, some protections that a larger, established product might have — for example, automated email-authenticity checks (SPF/DKIM/DMARC enforcement) beyond the sender-registration check described above, or a dedicated deletion self-service tool — are handled manually rather than automatically; see “Retention and deletion”.

Some service providers may process personal data outside the UK.

Where a restricted international transfer occurs, PurpleDue relies on appropriate recognised safeguards or contractual mechanisms made available through the relevant provider arrangements, where required.

PurpleDue retains personal data only for as long as reasonably necessary to:

• provide and administer the service;
• maintain the receivable and account history you need as a PurpleDue user;
• protect the security of the service and prevent abuse;
• resolve disputes;
• maintain legitimate business records; and
• comply with applicable legal obligations.

There is currently no automatic deletion or expiry process. If you would like your account and data deleted, contact us (see “Contact”) and we will action your request using our existing manual deletion process — deleting your stored invoice documents, your account's database records, and your sign-in account by hand — subject to any data we must reasonably retain for legal, security, dispute, billing, or backup/log purposes. This is currently a manual process we carry out on request, rather than an automatic, self-service, or immediate deletion tool — during this beta, this is an appropriate and honestly-disclosed limitation given the small number of accounts involved, not a hidden gap.

Depending on the circumstances and the lawful basis for processing, UK data-protection law may give you rights including: asking what personal data we hold about you and getting a copy of it; asking us to correct inaccurate data; asking us to delete your data (see above); objecting to or asking us to restrict certain processing; and asking for your data in a portable format. You can also complain to the UK Information Commissioner's Office (ico.org.uk) if you think we have handled your data incorrectly. To exercise any of these rights, contact us using the details below.

You are responsible for the accuracy of the invoices you hand to PurpleDue and for having the right to share your client's or customer's information with us for the purpose of tracking and following up on that invoice. PurpleDue does not verify that you are entitled to collect a given debt, and does not itself contact your clients — every follow-up and Formal Payment Request is reviewed and sent by you.

You can contact PurpleDue, including to exercise any of the rights described above or to request deletion of your data, at support@purpledue.com.

PurpleDue is in beta and this policy may change as the product develops. We will update the “last updated” date at the top of this page when we make changes, and will flag material changes more prominently where appropriate.