Privacy and your data

You choose how email reaches DUE, and you do not have to change how you work:

• Your DUE brand-work email address. The address is reserved; sending and receiving through it are not live yet. Using this address alone gives DUE no access to your personal inbox.
• An optional Microsoft Outlook connection that you choose to turn on and can disconnect at any time from Connected email. This separately authorises DUE to read relevant messages in the connected mailbox.
• Paste or upload a brief, email text, PDF or screenshot yourself.

You can also use DUE without email at all — Collabs, documents, invoices, bank CSV imports and payment tracking all work on their own.

DUE records a small set of product milestones in its own database: landing and signup steps, onboarding, brief capture started, succeeded or failed (with a general error category only), first collab, deliverable progress, invoices created, payments you record and return visits. It stores the landing path and, when present, UTM source, medium, campaign and content, keeping the first campaign link you arrived from separately from the most recent one. Links in DUE’s own outreach may carry a random code; that code contains no name or email address, and its meaning is visible only to the DUE owner. It does not use external analytics, session recording or analytics cookies, and uses no advertising pixel unless DUE offers optional Google Ads measurement and you choose Allow. It does not store IP addresses, and does not copy names, email addresses, mailbox content, client details, invoice contents or document text into these events.

The DUE owner can view a dated activity timeline for an individual account showing which of these steps happened and when, so the product can be improved. It never shows brief, email or invoice content.

The product owner can see aggregate totals, and an account-level list limited to the address you signed up with, when the account was created, the country you chose to declare (or the one on your invoice details, in which case it is labelled as such), where you first arrived from if that was captured, whether you have created a job, and your plan and email-preference state. This never includes email content and never includes your clients' details.

DUE works with a small number of creator-education partners who share a link such as brieftopaid.app/r/their-code. If you open one, DUE records that visit in its own database — the partner's code, the time, and an anonymous browser identifier — and remembers it in your browser for up to 90 days. If you create a DUE account in that browser within those 90 days, the account is attributed to that partner so any agreed partner terms can be settled later. The partner never sees your name, email address, account or activity; only the DUE owner can see the program records.

No commission rate, discount, price or payout is promised to anyone until it is agreed in a versioned schedule, and no commission can ever come from a free account, a demo or test account, a duplicate or existing account, or a failed, unpaid or refunded payment.

Some emails are required: notices about your account, your access, and any payment you make. These are sent whatever your preferences say, because they describe the service you are using.

Optional emails — occasional product updates, tips and reminders — are only sent if you tick the opt-in box at signup or in Settings. It is never ticked for you, existing accounts are not opted in, and reserving a DUE address never counts as consent. When you opt in, DUE records the date, where you did it and the wording you agreed to.

Every optional email carries a direct unsubscribe link that works without signing in. Opening the link does not change anything on its own; you confirm on the page. You can also change the setting at any time in Settings.

Each creator can reserve one address at collabs.brieftopaid.app. Sending and receiving through the reserved address are not live yet, so it is not currently a capture route. Paste, upload, manual entry and optional connected Outlook remain available.

Notification copies and replies through the reserved DUE address are not active while sending and receiving are off.

No brand mail is being received through the reserved DUE address while the feature is off.

Connecting Outlook is optional. When you connect, DUE looks at recent messages to spot work-related ones — a brief, an accepted quote, a contract, an invoice request or a payment advice. For messages it treats as relevant, it stores a limited copy: sender name and address, subject, date, conversation identifiers, a short excerpt or message body used for extraction, and the names and types of attachments. Mail DUE can confidently tell is an automated non-work notice is skipped before anything is stored. DUE does not send, reply, modify, label or delete anything in your Outlook mailbox.

Text, PDFs or images you submit for AI Capture, and relevant messages from a connected Outlook mailbox, may be sent through Lovable's AI gateway to a configured Google Gemini model to pull out structured facts such as client name, project, fee, dates and deliverables. The reserved DUE address is not receiving mail yet. Review the result before saving; uncertain email suggestions wait for your review.

Accepted results become or update a job in DUE — the client, scope, fee, dates and items. DUE never marks money as received on its own: a payment advice email records that a client said they paid, and nothing more.The reserved DUE address is not sending email yet. DUE flags overdue invoices and, once you confirm one is still unpaid, prepares an editable draft; you review it and send any follow-up yourself.

Your DUE data is stored in the database behind Lovable Cloud, which hosts this application. The reserved DUE address is not currently receiving or sending email. If you connect Outlook, access happens through Lovable's connector gateway, which holds the authorisation from Microsoft; DUE stores your connection reference encrypted and never in your browser. AI extraction requests travel through Lovable's AI gateway to the model provider.

What we have confirmed (checked 30 September 2026). DUE's database and private file storage run in Amazon Web Services' Mumbai region (ap-south-1), according to this project's hosting settings.

Resend (brand-work email). DUE's email domain uses Resend's Tokyo sending region (ap-northeast-1). Resend says the sending region controls how email is routed, not where it is stored. It says it stores customer data, including message content, delivery logs, webhook payloads and account records, in the United States. It keeps email and log data for 30 days on its Free, Pro and Scale plans, and backups for 7 days. Remaining data is deleted within 90 days after a customer (here, DUE) closes its Resend account. That applies to DUE's whole Resend account, not to deleting your DUE account (Resend GDPR page).

AI extraction. Lovable's privacy policy (effective 15 September 2026, section 5) says it does not use data from people using apps built on Lovable, including app usage data, to train its models (Lovable privacy policy). Google says prompts and responses sent to the paid Gemini API are kept for 55 days to detect misuse (Gemini API abuse monitoring). We have not confirmed that Google's policy applies to requests sent through Lovable's AI gateway. We have also not confirmed how long the gateway or model provider keeps each request.

Stripe. Stripe keeps payment data under its own privacy policy.

Still unknown: where database backups for DUE are held and how long they are kept, and where Lovable's AI gateway and the model provider process requests. We do not promise a location, zero retention or deletion time for these.

Free during early access; we will give notice before any future paid plans. No automatic charges. Those payments are handled by Stripe on Stripe-hosted pages. Stripe receives what it needs to take the payment — for example your email address and the card details you give it — and DUE never sees or stores your card number. DUE keeps only the outcome: which plan you are on, when it renews or ends, and the Stripe customer and session references.

This is only about paying for DUE itself. The invoices you send your own clients, the payments you record against them and any bank CSV you import are not sent to Stripe; they stay in DUE. Full terms, including cancellation and refunds, are on the terms page.

DUE does not sell your data, and does not share it with anyone beyond the providers described above.

You keep the rights to the client material you put in DUE. Processing it to provide the service is different from making it public. DUE does not publish client material, identifiable feedback, testimonials or screenshots without separate, explicit permission. Content-free product milestones help us improve DUE; the measurement described above does not include brief, email, invoice or document text.

Stop using your address by no longer giving it to brands. Disconnect Outlook at any time from Connected email; DUE stops checking it immediately. Anything already received stays in your account.

Remove email data from Connected email stops that Outlook connection and removes imported messages, conversations and notes linked to that mailbox. Manually entered or older notes without a proven mailbox link stay; the confirmation reports them. Business records remain. For messages and attachments stored for your professional brand-work address, write to hello@brieftopaid.app to request removal of individual items, or delete your whole account as described below.

Download my data in Settings (also shown if your paid access has ended) gives you a JSON file. It contains your profile, business details, brand-work address, collabs, timeline, deliverables, contacts, documents list, notes, invoices and line items, payments and match history, bank imports, stored email conversations, messages, participants, attachment details, delivery status, usage, connected-mailbox and connected-app details (without their keys), preferences, feedback, and your subscription and DUE receipts. It also links to every file DUE stored for you (uploaded documents, invoice PDFs, email attachments). The file itself does not include copies of those files. The links stop working after 60 minutes, so save each file you want before then; if they expire, download your data again for new links. With many or large files, you may need to save them one by one. Passwords, sign-in and connection keys, internal security tokens and card details are left out. So are messages still in your Outlook mailbox or held at Resend. If a link can't be created for a file, the export marks that file as unavailable so you know to try again. This is a copy of your records as data, not a full backup.

Delete my account in Settings asks you to type a confirmation. It then does these steps in order. First, it locks your account: while deletion runs, nothing can add, change or remove your records or stored files — not a device that is already signed in, and not DUE's own background jobs — and new sign-ins are paused. Only one deletion can run at a time. Then it cancels any active DUE subscription with Stripe immediately, so it cannot renew. Next, it disconnects Outlook, then removes all your stored files and all your records. It checks again that no records or files are left, including anything added while it worked, and closes your sign-in last. If any step fails, you'll see a message and the lock is lifted, sign-in is restored, and you can try again. After a successful deletion, a record that the account ID was deleted is kept so nothing can be recreated for it. We never report success for a step that did not finish. Some records are kept on purpose. Receipts, checkout and refund records for payments you made to DUE stay as financial records. They keep your former account ID and Stripe payment references, so they can still be linked to you through Stripe. A one-way fingerprint used to stop repeated free trials also stays. Deleting a single invoice or document also removes its stored file.

Deleting your account does not remove copies held by providers. That includes messages at Resend, requests kept by the AI provider, data held by Stripe, and database backups. Those copies stay under each provider's own retention rules, and we cannot promise when they will be removed. Messages that are still in your Outlook mailbox stay there.

If self-service export or deletion doesn't work for you, or for a question about this page, or a request about your data — write to hello@brieftopaid.app.