Privacy Policy: Invoice Late Fees
What the Invoice Late Fees app for the Stripe Dashboard reads, stores and deletes. Our general Privacy Policy covers this website and our other apps. Back to the app page.
Last updated: November 11, 2026
Who is responsible
- Invoice Late Fees is provided by OZET, a trade name of Zambounis Technology, Av. Eugène-Rambert 30, 1005 Lausanne, Switzerland. OZET and Zambounis Technology are trade names of Orestis Zambounis, sole proprietor, not registered companies.
- Privacy questions, requests about your data and support: [email protected]. Security reports: [email protected].
What the app reads from your Stripe account
The app uses the four permissions you grant when you install it, and nothing else:
- invoice_read: your open invoices, their due dates, amounts, payments and status, to decide whether an invoice is overdue and to calculate the fee.
- invoice_write: to create, finalize, send and void the separate late-fee invoice, to delete an unfinished fee draft, and to write a link to the fee invoice into the metadata of the overdue invoice.
- payment_intent_read: to check whether a payment on the overdue invoice is still processing, so no fee is billed on a payment that is on its way.
- event_read: to receive invoice events (paid, voided, marked uncollectible, overdue) and install and uninstall events.
Invoices and events that Stripe sends to the app contain your customers' names, email addresses and addresses. The app reads them in memory to do its work and does not store them.
What the app stores
The app keeps one database on its own server. It holds:
| Record | Contents |
|---|---|
| Install | Your Stripe account id, the environment (live, sandbox or test), install status and dates, the date and Stripe user id of the first settings save (the setup record), and, when given, the date and Stripe user id of the confirmation for automatic mode and of the confirmation for fees on all customers |
| Fee settings | Your fee rule (preset, flat fees, percentage, interest, reference rate and the date you checked it, minimum, caps), grace period, customer scope, fee invoice terms, delivery, mode, run cap, and the Stripe user id of the last person who saved |
| Customer flags | A Stripe customer id with "exempt" and "business customer" switches, and the Stripe user id of who changed them |
| Waivers | A Stripe invoice id, when it was waived and the Stripe user id of who waived it |
| Fee ledger | For each fee: the overdue invoice id and number, the customer id, currency, amounts, the fee components, the rule used, status, the fee invoice id and number, dates, the Stripe user id of who created or voided it, the customer credit balance Stripe applied, and an error message without customer data |
| Automatic runs | Per day: how many invoices were examined, billed and held back, and why invoices were skipped |
| Invoice locks | Short-lived locks (an invoice id) so two actions on one invoice never run at once |
| Plan | Free or Pro, subscription status, trial end, period end, and the customer and subscription ids on OZET's billing account |
| Webhook jobs | Event id, type, account id, object id and a few non-personal fields (ids, statuses, dates); never the event payload |
| Uninstall record | Account id, environment, the uninstall event id and the dates of uninstall, scheduled deletion, deletion and reinstall; no business data |
The app does not store customer names, email addresses, postal addresses, tax ids, invoice PDFs, card or bank details, or anything in Stripe's Secret Store. It stores no API keys or tokens for your account: it calls Stripe with the platform access Stripe grants on install.
Personal data and legal basis
- Your team: the Stripe user ids (usr_...) of the people who saved settings, gave a confirmation, waived, created or voided a fee or changed a customer switch. They show who did what and are deleted with the rest of your data.
- Your customers: Stripe customer ids, invoice ids and invoice numbers. If a customer is a person, these ids relate to that person; the app does not store their name or contact details. You decide whose invoices get fees; by default only business customers.
- Roles: for this data you are the controller and OZET processes it on your behalf to run the app. A data processing agreement is available on request at [email protected].
- Legal basis: we process this data to perform our contract with you and in our legitimate interest in operating and securing the service.
Where the data is stored and who processes it
- Fly.io: the app's server and database are hosted by Fly.io in Frankfurt, Germany. Fly.io lists its own sub-processors at fly.io/legal/sub-processors.
- Stripe (your invoices): all invoice data stays in your Stripe account.
- Stripe and Link (buying Pro): the Pro plan is sold through Stripe Checkout with Stripe Managed Payments on OZET's billing account. Link, Stripe's merchant of record service, is the seller for that purchase: it collects your name, email address, billing address and payment details, processes the payment, calculates tax, sends receipts and handles payment support, refunds and disputes, under Link's and Stripe's own privacy terms. OZET never sees card numbers. For the billing data OZET receives from Stripe and Link (the billing customer id, the subscription id and status, the trial end and the period end), OZET is an independent controller, to run the subscription. Stripe keeps the customer, subscription and payment records in OZET's billing account, where OZET can see them; OZET uses them only to provide the plan, answer support requests and send the notices in the terms. If you ask Stripe to delete your Managed Payments data, Stripe cancels the subscription and deletes that data, including the records in OZET's billing account, and tells OZET.
- ozet.ch: the ozet.ch website, including the pricing page, is hosted on Cloudflare Pages. The pricing page sets no cookies, uses no browser storage and loads no analytics; it sends your Stripe account id and the link token from the app to the app's server only when you press a button.
- Apart from OZET's own error tracker described under Logs, no other service receives data from the app. The app sends no email; Stripe sends its own invoice email when the delivery setting says so.
Logs
The app's server writes its logs to Fly.io. Log lines contain ids (account, invoice, customer, fee and event ids), event types, counts and status codes, and no customer names or email addresses.
If the app's server hits an unexpected error, it sends an error report to OZET's own self-hosted error tracker (Bugsink), which runs on Fly.io in Frankfurt, Germany, so that we can find and fix the error. A report contains the error type and message (with keys, tokens and email addresses removed), the place in the code where it happened, the request path or the name of the background job, the app version, the Stripe environment (live, sandbox or test), and the Stripe account id, event id and event type. It contains no request bodies, headers, customer names, email addresses or invoice contents. Expected outcomes, such as a refused request, are not reported.
How long the data is kept
- While the app is installed, the data is kept so the fee history, waivers and exemptions keep working.
- Webhook job rows are deleted 30 days after they arrive.
- Automatic-run rows and the fee ledger are kept until you uninstall.
When you uninstall
- When Stripe sends the uninstall event, the app stops at once: no automatic run, no fee work, no change to your Stripe account.
- 72 hours after the event, the app checks with Stripe and deletes every record of your account listed above (except the uninstall record), including its webhook jobs. If Stripe does not answer, the deletion waits, but never longer than 96 hours after the event.
- Server backups (Fly.io volume snapshots) are kept 5 days, so the deleted data leaves the backups within 9 days of the uninstall at the latest.
- If you reinstall and open the app before the deletion, your settings, setup record and fee history are kept; automatic mode is turned off and its confirmation is cleared, so you confirm it again if you want it.
- Fee invoices the app created stay in your Stripe account; they are your invoices.
- The uninstall record (account id, environment and dates, no business data) is kept as proof of the deletion and is deleted 30 days after the uninstall.
You can also ask for deletion while the app is installed by writing to [email protected] from an address we can verify for the account. We delete the data within 30 days.
Security
- All traffic uses HTTPS. Every request from the app's views is signed by Stripe and checked by the server before anything runs; every webhook is checked against its signing secret.
- The app uses standard cryptography only (Node.js crypto and the Stripe SDK).
- The server keeps its own Stripe keys and signing secrets as Fly.io secrets, never in the code or the database.
- Report a security issue to [email protected]. If a breach affects data the app holds, we notify the affected merchants without undue delay and Stripe as our agreement with Stripe requires.
Your rights
You can ask what data the app holds about your account, ask for a copy, ask for corrections or ask for deletion by writing to [email protected]. If you are in Switzerland, the EU or the UK, you can also complain to your data protection authority.
Changes
OZET announces changes to this policy on this page at least 30 days before they take effect.