Privacy & Cookie Policy

Last updated:

1. Who we are

Pulget turns the receipts, statements, and payment screenshots you already have into a clean money inbox with useful spending insights. Cublya (“we”, “us”) is the controller for the personal data described here. You can reach us at [email protected] about anything in this policy.

Pulget does not connect to your bank and does not use open banking. Nothing reaches us until you upload it.

2. What we process

  • Documents you upload: the receipts, invoices, bank or card statements, exports, and payment screenshots you choose to add, plus everything extracted from them: transactions, merchants, amounts, dates, account and card numbers shown on the document, and any other detail the document contains.
  • Account data: your name, email address, and password (stored only as a salted hash, never in readable form). If you sign in with Google instead, this comes from your Google account; section 4 covers that.
  • Consent records: which version of the Terms of Service you agreed to and which version of this policy you were shown, when, whether you created your account with email or Google, the language of the page, and the IP address and browser string of the request that recorded it. We write this on our server when you sign up. Your answers on product update emails and, when you are signed in to the app, on analytics and session replay (section 6) are recorded the same way. We are required to be able to demonstrate them.
  • Sign-in sessions: for each device you are signed in on, the IP address and browser string it signed in from, so you can see and end your sessions in the app.
  • Preferences stored on your device: settings, theme, language, and your cookie choice, held in your browser (section 6).
  • Technical data: IP address, browser and device type, and time zone, processed by our hosting providers to deliver and secure the service. To limit abuse we count requests per IP address (or per account when you are signed in); sign-in and contact-form counts are stored only as a keyed hash of the address.
  • Usage data: page visit counts and pseudonymous product analytics, only if you allow analytics in the cookie banner; and visit statistics from Lundot (section 6).
  • Session replays: only if you allow session replay in the cookie banner, a recording by Lundot of how you move through and use a page, with what you type, images and personal details masked before anything leaves your browser (section 6).
  • Communications: the content of any email or contact form message you send us, and your email address if you subscribe to the newsletter on our website.

Documents like receipts can incidentally reveal sensitive things: a pharmacy purchase, a payment to a clinic, a donation to a political party or religious organisation. We do not seek this data out or use it to categorise you, but you should know it can be present in what you upload, and you decide what to upload.

3. Why we process it, and on what basis

  • Running the service (extracting, organising, and displaying your transactions and insights): performance of our contract with you, Art. 6(1)(b). This is not optional; without it there is no service.
  • Creating and securing your account, including authentication, abuse prevention, and rate limiting: performance of the contract, and our legitimate interest in keeping the service available and safe, Art. 6(1)(f).
  • Keeping our own service working: error logs, uptime monitoring, and diagnosing failures. Legitimate interest in operating a reliable service, Art. 6(1)(f). You can object to this at any time, see section 10.
  • Analytics (Cloudflare Web Analytics, PostHog and Lundot): consent, Art. 6(1)(a), given through the cookie banner and withdrawable at any time. Cloudflare Web Analytics and PostHog do not load until you allow it; what Lundot does before then is in section 6.
  • Session replay (Lundot): consent, Art. 6(1)(a), given separately from analytics through the cookie banner and withdrawable at any time. Nothing is recorded until you allow it.
  • Product update emails and the newsletter: consent, Art. 6(1)(a), given by ticking the optional box at sign-up or by subscribing on our website. You can withdraw it at any time in the app’s notification settings or by writing to us.
  • Proving consent and acceptance: legal obligation, Art. 6(1)(c), read with Art. 7(1).

We do not train any model on your documents, and nobody at Cublya reads them to improve extraction. Where we measure extraction quality we do it on our own test documents. Our requests to the extraction providers in section 7 do not ask for zero retention, so what each of them keeps, and for how long, is governed by its own terms.

Providing this data is a contractual requirement in the sense that Pulget cannot work without the documents you choose to give it. There is no consequence to not providing them other than having nothing to show you.

4. Signing in with Google

Signing in with Google is optional; email and password work the same way. If you use it, we ask Google for two things, the email and profile scopes, and receive your email address, your name, your profile picture, and the account identifier that recognises you next time. We use them to create your account, sign you in, and show your own name in the app. Pulget does not request Gmail, Drive, Calendar, or Contacts, and holds no permission that would let it read them.

This data is stored and deleted with the rest of your account (sections 7 and 9), is never sold, and is never used for advertising. Our use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. You can disconnect Pulget at any time from your Google account permissions; that ends sign-in but does not delete your workspace, which you delete yourself under Privacy & data in the app.

5. Automated processing and AI

Extraction and categorisation are automated. A language model reads the document you upload and returns structured figures, which the app then shows you for review. This does not produce legal or similarly significant effects and is not automated decision-making in the sense of Art. 22: nothing is decided about you, and you can edit or delete every value it produces.

Pulget does not assess creditworthiness, score you, or make lending decisions, and we do not sell or share any profile of you.

6. Cookies and similar technologies

This covers anything stored on or read from your device, not only cookies: local storage and session storage count too.

  • Strictly necessary: the cookies that keep you signed in (and, during a Google sign-in, one that ties the round trip together); your cookie choice, kept for 12 months; once that choice is recorded with your account, a note in local storage of which choice was recorded for that account, so it is not sent again; and your language, theme, in-app preferences and progress, held in local storage. If you followed an invite link, we also keep its invite code on your device for that visit only (in session storage, gone when you close the tab) or until your new account claims it. If you sign up with email after following an invite link, the code is also saved with your new account until the invite is applied or turned down, so it still counts if you confirm your address on another device. These need no consent and cannot be switched off without breaking the app.
  • Optional analytics: Cloudflare Web Analytics, which counts page visits and reads page load timings without setting a cookie, and PostHog (hosted in the EU), which stores a pseudonymous identifier in a cookie and local storage to understand which parts of the app get used. Neither loads until you allow analytics.
  • Lundot visit statistics: Lundot’s script is on every page and sets no cookies. Before you allow analytics it collects cookieless visit statistics: the pages and titles you view, the referring site, campaign (UTM) tags, screen size, language, and a coarse location and device and browser derived from your IP address and browser string. Visits are grouped with a salted hash that changes every day, so they cannot be followed from one day to the next. Allowing analytics adds linking your visits to your account and ad click ids from the address; withdrawing it ends only that.
  • Optional session replay: Lundot records how you use a page, as a replay that we can watch to find where the app is confusing. It is a separate choice from analytics, off until you switch it on, and Lundot never starts recording on an analytics choice alone. Before anything leaves your browser, what you type is dropped, commonly formatted email addresses, phone and card numbers in the page are masked, video, audio, canvas and embedded frames are replaced by placeholders, and addresses lose their query string and fragment. Other page text and images are recorded. A recording can show which pages you opened, where you clicked and scrolled, and how long you stayed. We do not watch recordings routinely, and only people on our team with access to Lundot can. Lundot keeps replays for 30 days, and for at most 1 GB per site, after which the oldest are deleted first. A browser that sends Global Privacy Control or Do Not Track is never recorded.

The banner offers Reject all, Customize and Accept all with equal weight, and nothing optional is switched on in advance. You can change your mind at any time under Cookie settings in the footer, or in Privacy & data inside the app; withdrawing is exactly as easy as accepting. Withdrawing analytics stops PostHog and reloads the page without the Cloudflare beacon; withdrawing session replay stops Lundot recording and drops anything it had not yet sent. We ask again after 12 months, or when what we ask about changes. While you are signed in to the app, your answer for each category (analytics and session replay) is also recorded with your account, with the IP address, browser string and page language of the request (section 2); a choice you made before signing in is recorded the first time you open the app signed in.

If your browser sends a Global Privacy Control signal, we treat it as a refusal of optional analytics and session replay, and of any sale or sharing of personal information, and we honour it without you having to touch the banner.

7. Who else processes your data

We do not sell your personal data and we do not share it for advertising. We do use service providers, who process it on our instructions under a data processing agreement:

  • netcup (Germany): the server that runs our website, API, sign-in, background processing and database. Holds your account data and everything extracted from your documents.
  • Cloudflare: the network in front of the site, which every request passes through; file storage (R2), kept in the EU, which holds the documents you upload, the files derived from them, and workspace export files you upload to restore from, which are deleted once the restore ends or with your account; our encrypted database backups, also in R2 (section 9); and, only with your consent, Web Analytics.
  • Resend: sends our sign-in emails (address confirmation, password reset) and delivers the messages you send through our contact form to us.
  • OpenRouter and Google (AI Studio): document extraction. The contents of a document you upload are sent to OpenRouter, which passes them to one of these models, tried in this order until one answers: Anthropic Claude Haiku 4.5 on Amazon Bedrock; Google Gemini 3.8 Flash; OpenAI gpt-oss-120b; OpenAI gpt-oss-20b (free tier); NVIDIA Nemotron 3 Super (free tier). For every model but the first, OpenRouter chooses the company that hosts it. If none of them answers, the document goes to Google directly (Gemini 2.5 Flash-Lite).
  • Google: sign-in, if you choose to sign in with Google (section 4).
  • PostHog (EU): product analytics. Only with your consent, and never with the contents of your documents.
  • Lundot: visit statistics and, only with your consent, session replays of our pages, with what you type, images and personal details masked. It never receives the files you upload or what you type.
  • Grafana Labs (Grafana Cloud, hosted in Germany): our server’s logs and metrics, and error and performance traces of its requests and background jobs. The logs can contain request paths, IP addresses, account identifiers and error messages. The traces record timings, error details, IP addresses, browser strings and the identifiers of import jobs and documents. They normally name a request to our API by its route pattern rather than its full address, which leaves out the identifiers and search terms in the address. Prompts and model answers are not recorded, and none of this is meant to hold the contents of your documents, but an error message can include a short excerpt of the data that caused it, such as part of a model answer that could not be read.
  • Photon by komoot (Germany): place search. When you search for a place in the app, what you type is sent from your browser to Photon to suggest matching places. When we import a document, our server sends the city names found on its transactions (the name alone, not the amount, the merchant or your account) to Photon to check that they are real places.

We may also disclose data where the law requires it, or to establish or defend legal claims.

8. International transfers

Some of the providers above are established outside the EEA, mainly in the United States. Where personal data is transferred there, we rely on the European Commission’s Standard Contractual Clauses, which form part of our agreements with those providers, together with additional technical measures such as encryption in transit and at rest. Write to [email protected] for a copy of the relevant safeguards.

9. How long we keep it

  • Documents, transactions, and everything derived from them: until you delete them, or until you delete your account.
  • Account data: for as long as your account exists. Deleting your account removes it at once, together with your sign-in record, your sessions and any pending password reset link. We keep only the account’s random identifier on a list of erased accounts, so that restoring data can never bring the account back. If you sign up with email and never confirm your address, the account and its consent record are deleted 14 days after sign-up.
  • Consent records: for the life of the account, and deleted with it. Once the relationship ends there is nothing left to demonstrate consent for.
  • Backups: the database is backed up, encrypted, to Cloudflare R2, and about four to five weeks of backups are kept, so deleted data, a deleted account included, remains in them until they rotate out. One-off copies made when we moved the database to its current server are also held there, encrypted, while we decide how long to keep them.
  • Sign-in sessions: until you sign out or the session expires (seven days after it was last used); expired sessions are deleted within an hour.
  • Abuse limits: request counts per IP address or account last one minute; the hashed sign-in and contact-form counts last at most an hour and are deleted within the hour after that.
  • Newsletter: until you ask us to remove your address.
  • Lundot data: visit statistics for 25 months, heatmaps for 13 months, and session replays for 30 days (at most 1 GB per site, oldest first). Lundot deletes backups of deleted data within 35 days.
  • Server logs, metrics and traces: kept by Grafana Labs; the period is to be confirmed.
  • Support email: 12 months after the conversation ends.

10. Your rights

Wherever you live, you can ask us to:

  • give you a copy of your data, and of this policy’s details (access)
  • correct anything wrong (rectification)
  • delete it (erasure)
  • hand it over in a portable format (portability)
  • pause processing while a dispute is resolved (restriction)
  • stop processing based on legitimate interests (objection), which you can do at any time and for reasons particular to your situation
  • withdraw a consent you gave, without affecting what happened before you did

Two of these are buttons rather than emails: Exports in settings downloads your whole workspace, and Privacy & data deletes your account and everything in it. For anything else, write to [email protected]. We answer within one month.

If you are unhappy with how we have handled your data, you have the right to complain to your local data protection supervisory authority. You do not have to come to us first, though we would rather you did.

11. If you are in the United States

We do not sell your personal information and do not share it for cross-context behavioural advertising, as those terms are used in US state privacy laws. We honour the Global Privacy Control signal as an opt-out request. The rights listed in section 10 cover the access, correction, deletion, and portability rights those laws give you, and we will not discriminate against you for exercising them.

12. Security

Data is encrypted in transit, and uploaded files and database backups are also encrypted where they are stored. Access is limited to the people who need it, and our application code limits each request to the signed-in account’s own data, which automated tests check. No system is perfect; if a breach affects you and carries a high risk, we will tell you.

13. Children

Pulget is not for anyone under 16. We do not knowingly collect data from children, and we delete it if we find we have.

14. Changes to this policy

We update this page when our practices change, and revise the “Last updated” date above. When a change is material, we will not simply post it: the next time you use Pulget while signed in, a notice links to the new version until you dismiss it. A material change to the Terms of Service is different: you are asked to accept it before you carry on.

15. Contact

Questions about this policy or our data practices go to [email protected]. See also our Terms of Service.