Legal

Privacy policy

Last updated: 14 November 2026

The current app stores your documents and client data in your browser on your device. AI requests go directly from your browser to OpenRouter and its providers. Our servers handle sign-in, licences, purchases and reading credit, but do not receive your documents through these features. Optional encrypted sync is planned separately and is not available yet. We do not use analytics or advertising trackers. The app uses a browser identifier cookie to help prevent repeated free trials.

1. Who we are

Sumskeeper (contact: [email protected]) handles the licence, purchase, support and website information described below. You decide which documents to process, including documents belonging to your clients, and why. We do not receive those documents through the app.

2. Your documents and your clients' data

Local storage. Documents, extracted values, supplier defaults, imported accounting data and settings are saved in your browser. Sumskeeper does not keep a server copy.
Document reading (AI processing). Reading a document means it is processed by an AI model. Your browser sends documents, selected areas or extracted text directly to OpenRouter, which routes the request to an AI provider. Requests use your trial credit, licence credit (included or purchased), or an optional OpenRouter API key of your own. Supported structured e-invoice data can be extracted locally without AI.
Provider retention. In Settings, you can restrict requests to providers that support zero data retention. OpenRouter and its providers handle requests under their own policies. If you connect your own OpenRouter account, your use of that account is also subject to your agreement with OpenRouter.
Backups and exports. You choose where to save downloaded files. If you enable automatic backups, the app writes backup files to the folder you select. Your storage provider handles any cloud syncing you set up for that folder.

Planned sync and collection services. These are not part of the current app. The roadmap proposes optional end-to-end encrypted sync, with workspace data encrypted in your browser before upload, and encrypted storage for incoming forwarded documents. This policy will be updated before those services become available to explain their data handling and the choices you have.

3. Your OpenRouter key

If you connect your own OpenRouter account or enter your own API key, the key is saved in your browser and sent to OpenRouter to process requests and check your balance. Sumskeeper does not receive or store your own key on its servers. Keys issued for included reading credit are also stored by our activation service, as explained in section 4. You can manage your OpenRouter connection in Settings.

4. Sign-in, licences and reading credit

Licence codes are verified on your device. To activate included reading credit, the app sends your licence code to our activation service. The service creates an OpenRouter API key with a spending limit and returns it to the app. It stores the licence ID, plan and issued key so you can access the same remaining credit on another device and so we can disable the key after a refund. It does not receive documents, file names, client names or extracted values. Usage of included credit is recorded under our OpenRouter account.

When online, the app checks for refunded licences at most once a day. The request contains licence IDs, not client or document data.

To help prevent repeated free trials, the app sends a randomly generated browser identifier when you sign in. This identifier is saved in local storage and a cookie. Our service also receives your network address. Trial records store the browser identifier and a salted hash of the network address, rather than the address itself. Network trial counters expire after 30 days. We also log declined trial attempts, including the email address, reason and shortened browser and network identifiers, to review potential abuse.

Stripe handles payments for reading credit. We receive the payment confirmation and associated licence, then increase the spending limit on that licence's AI key. We do not receive your card details.

When you sign in with Google or email, we store your email address and the licence codes linked to it. This lets you access your licence on another device. For email sign-in, our email provider sends a one-time code. For Google sign-in, we verify a Google-issued token containing your email address and its verification status. Our email provider is Resend. Purchases made directly with us are linked to the email used at checkout. Signing in restores access to your licence, not your documents. Documents and client data stay in each browser and are never sent to us.

If you ask to be notified when Sumskeeper Office (our optional subscription, including encrypted sync) launches, we keep your email address on that list and use it only to tell you once, when it is available. You can ask us to remove it at any time.

5. Information we do receive

When you buy: your name, email address and purchase details, from the store you buy through, so we can deliver your licence and support you. Direct purchases are processed by Stripe; marketplace purchases by AppSumo.
Error reports: when the app hits an unexpected error, it sends us the error message, where in the app it happened and your browser type, so we can fix it. Email addresses, file names and quoted text are removed first; documents and client data are never included.
Support requests: your email address and the information you send us, so we can respond.
When you visit this website: our host processes standard technical information (such as IP address and browser) to serve pages and keep the site secure. Our host is Cloudflare, which serves the website and app and runs our account service. We don't keep request logs of our own; Cloudflare keeps short-term operational logs under its own policy.

We do not sell your information or use it for advertising. We share information only with the services described in this policy, as needed to provide Sumskeeper and support purchases.

6. Cookies and tracking

We do not use analytics or advertising trackers. The app stores a random browser identifier in local storage and a first-party cookie to help prevent repeated free trials, as described in section 4. The cookie is set to expire after two years and is renewed when you sign in. Browser storage also saves your workspace and preferences, including your theme and fonts, on your device.

7. Data retention

Workspace data stays in your browser until you remove it or the browser clears its storage. If you set a retention period for original files, the app may remove originals that meet those conditions. Separately saved backups and exports remain wherever you saved them.

We keep information only as long as we need it:

Purchase records: 7 years, for tax and accounting.
Licence records, linked email addresses and issued reading keys: while the licence exists, then up to 7 years after a refund or deletion request, to handle refunds and disputes.
Support emails: 2 years after our last exchange.
Sign-in codes: deleted within 1 hour.
Free-trial abuse checks: scrambled network addresses for 30 days; the browser identifier record for up to 12 months; turned-down attempts for 90 days.
Error reports: 30 days.
Limits against automated abuse: scrambled network addresses with a request count, for 2 hours.
The Sumskeeper Office waiting list: until we send the launch notice, then deleted.

8. Your rights

Depending on where you live, you can ask to see, correct or delete information we hold about you, or object to how we use it. Email [email protected]. You can also complain to your data protection authority. In the United States, that's your state attorney general or the Federal Trade Commission. In the UK, it's the Information Commissioner's Office (ICO); in the EU, your national data protection authority.

9. Changes

If this policy changes, we will publish the updated version here with a revised date.