Privacy Policy

Last updated 13 September 2026

Draft

Draft for review. This document has not yet been reviewed or approved by the operator of Bucksy and is not legally binding in its current form. Bracketed values are placeholders.

This policy explains what Bucksy collects, why, who processes it on our behalf, and how long we keep it. The controller is [COMPANY NAME], [REGISTERED ADDRESS]. Questions and requests go to [CONTACT EMAIL].

1. What we collect

Account details — your email address, and any name or avatar you give our identity provider when you sign up.
Receipt images you upload, and the line items, prices, totals, dates, stores and categories extracted from them or entered by you.
Household sharing data — the spaces you belong to, who else is in them, and invitations you send or accept.
Payment data — your plan and subscription status, and, once paid plans go on sale, the billing identifiers our payment processor gives us. Card details are handled by that processor and never reach our servers.
Operational data — server logs, error reports and basic request metadata such as IP address and browser, kept to run and debug the service. We do not run third-party analytics or advertising trackers.

2. Why we use it

Where the law requires a legal basis, we rely on performance of our contract with you for the first three, and on our legitimate interest in a secure, working service for the fourth.

To provide the service: reading your receipts, categorising items and showing your spending.
To authenticate you and keep accounts and shared spaces separate and secure.
To take payment for a paid plan and to tell you about changes to your subscription.
To diagnose faults, prevent abuse and meet our legal obligations.

3. Automated processing of receipt images

When you upload a receipt we send the image to Anthropic's API so a model can read the line items. Anthropic processes the image as our provider and, under its commercial terms, does not use it to train models. Extraction is automated and produces no legal or similarly significant effect about you; you can review, correct or delete anything it produces.

4. Processors we use

Each acts on our instructions under a data processing agreement. Some are based in the United States, so your data may be transferred there under the transfer mechanism [TRANSFER MECHANISM]. We do not sell your data or share it for advertising.

Clerk — accounts, sign-in and session management.
Railway — application hosting and the PostgreSQL database holding your receipts and extracted items.
Vercel — hosting for the web frontend.
Cloudflare R2 — object storage for receipt images, once images are stored there rather than in our own database.
Anthropic — automated extraction of line items from receipt images.
Stripe — subscription payments, once paid plans go on sale.
Sentry — error reporting, when enabled.

5. How long we keep it

Receipts, images and extracted items are kept until you delete them or close your account, because the point of the service is the history. Account and billing records are kept for as long as your account exists and afterwards only as long as tax and accounting law requires. Logs and error reports are kept for [LOG RETENTION PERIOD].

Deleting your account removes your receipts, images and extracted data from our live systems promptly; residual copies in encrypted backups age out within [BACKUP RETENTION PERIOD]. Data in a shared space that another member created stays with that member.

6. Your rights

Depending on where you live you may ask us for a copy of your data, correct it, delete it, restrict or object to processing, or receive it in a portable form. Write to [CONTACT EMAIL] and we will respond within one month. You can also delete your account yourself from your account settings, and you may complain to your local data protection authority.

7. Security

Traffic is encrypted in transit, data is encrypted at rest by our hosting providers, access to production is limited to the people who operate the service, and every query is scoped to the signed-in account. No system is perfectly secure; if a breach affects you we will notify you as the law requires.

8. Children

Bucksy is not intended for children under 16, and we do not knowingly collect their data. If you believe a child has an account, contact us and we will delete it.

9. Changes to this policy

We will update this page when our processing changes and revise the date above. Material changes will be announced in the service or by email before they take effect.