What DueNotice does in your Stripe account, and on what authority.

You are the trader. DueNotice acts as your appointed agent for the things listed below, and for nothing else. The statutory duties remain your own; DueNotice acts for you, not in your place. DueNotice does not give legal advice.

By connecting your Stripe account you appoint DueNotice as your agent to do the following, and you authorise each of them.

1. Send the statutory subscription notices to your customers. DueNotice calculates which notices are due for each of your UK consumer subscriptions and sends them at the times it calculates, from DueNotice's own sending domain on your behalf — or from your own domain once you have set one up. It sends only where your account is configured to send and the subscription is in scope; where it is not, the obligation is shown to you as outstanding rather than sent.

2. Host the cancellation page, and cancel on a customer's request. DueNotice hosts the page your customers use to cancel. When a customer cancels, DueNotice cancels that subscription in your Stripe account immediately, without asking you first.

3. Pay a cooling-off refund out of your Stripe balance. Where DueNotice calculates that a cancelling customer is owed a refund, DueNotice pays it from your Stripe balance immediately and without further approval from you. It pays no more than the original charge can return, and it refuses rather than guesses where the charge is disputed, cannot be found, or already carries refunds DueNotice did not make — in which case it tells you and leaves the payment to you.

4. Record each of these, and tell you when Stripe refuses. Every notice, cancellation and refund above is recorded in your audit log, which is append-only: DueNotice cannot later alter or delete what it recorded. If a call to Stripe fails — a cancellation Stripe refuses, a refund that does not go through — DueNotice records the failure and raises it on your dashboard for you to act on.

What DueNotice does not do. It does not create anything in your Stripe account other than the cancellations and refunds described above. It does not change your prices, your products or your subscriptions. It does not retain customers or interpose anything between a customer and their cancellation. Two duties owed before a contract is entered into — the pre-contract information and the payment-obligation acknowledgement — are yours and are not something DueNotice can discharge for you; DueNotice lists them, and records what your Stripe checkout reported, so that you can see where they stand.

You can revoke this. Disconnecting your Stripe account in Stripe, or asking DueNotice to disconnect it, ends the authority above. DueNotice stops sending, cancelling and refunding at that point. What is already recorded in your audit log stays recorded.

The obligations wording for this part is with our solicitor. What follows is a factual description of the processing as the system is actually built, and is accurate as of the version date above.

What DueNotice processes on your behalf. Your subscribers' email addresses and names; their Stripe customer and subscription identifiers; their subscription dates, prices and billing periods; and the outcome of each notice DueNotice sends them. Also your own users' email addresses and names, and what each of them did in DueNotice.

Who the data subjects are. Your consumer subscribers, and your own staff who use DueNotice.

What it is for. Calculating which subscription notices are due, sending them, hosting cancellations, calculating and paying cooling-off refunds, and keeping the record of all of it.

Where identifying data is, and is not. The audit log holds no identifying data at all: it carries opaque references, and the identities behind them live in a separate, deletable store. An erasure request destroys that mapping — after which the audit log entries remain, and can no longer be connected to a person.

Sub-processors in the path. Stripe (billing and payments), Postmark (sending email), Neon (database hosting), Vercel (application hosting), and Google Cloud KMS (planned, not yet in production — signing the audit log's checkpoints).

Retention. Audit log entries are kept for as long as the log exists; they cannot be deleted, which is the point of them. The identities they refer to are kept while the subscription is live and then as long as you keep your DueNotice account, and are destroyed on an erasure request.