StackTail · Legal

Privacy Policy

Last updated: 11 October 2026

1. Who we are

StackTail is provided by ChainCore Industries OÜ, a company registered in Estonia (registry code 17368514, Kruusa tn 3a, 10911 Tallinn, Estonia) ("we", "us", "our"). We are the controller of the personal data described in this policy.

This policy covers the StackTail apps for iPhone and Android and the StackTail web app at app.stack-tail.com (together "StackTail"). It explains what personal data we collect, why, how long we keep it, who helps us process it, and the rights you have under the EU General Data Protection Regulation (GDPR), the UK GDPR and other applicable privacy laws.

Contact for anything in this policy: contact@chaincoreindustries.com, subject line "Privacy Request — StackTail".

2. The short version

  • Your organizer stays yours. Setups, rooms, items, notes and photos live on your phone. If you use cloud backups or the web organizer, they are encrypted on your phone or in your browser before they reach us, with a key that only you and your devices have. We store those encrypted copies but cannot read them.
  • We keep what we need to run your account: username, email address, a password hash, your plan and credits, your sign-in sessions and the browsers you have linked.
  • No advertising and no tracking. StackTail contains no advertising and no tracking, and we run no analytics of our own. The web app uses a single sign-in cookie and nothing else. One thing to know: in the Android app, the barcode scanner is a component from Google that sends Google some technical data (see section 3.9).

3. Data we collect

3.1 Account data

When you create an account we store:

  • your username and email address;
  • your password as a one-way hash (Argon2id). We never store or see your password itself and cannot recover it;
  • whether your email address is confirmed, and short-lived single-use codes for confirming your email or resetting your password;
  • your plan (Free or Pro), when your Pro subscription ends, when you created your account, and the time of a deletion request if you make one.

3.2 Sign-in sessions

Each phone or browser you sign in on gets a session. For each session we store whether it is a phone app or the web app, the device or browser description your app or browser sends (its "user agent"), when it started and was last renewed, when it expires, and when and why it ended.

In the web app, your session lives on our web server. Your browser only holds a cookie called __Host-st_sid containing a random identifier; the sign-in tokens themselves are encrypted on our server and never reach the web page.

Cookies and browser storage. The web app sets exactly one cookie, __Host-st_sid. It keeps you signed in, is set when you sign in, is removed when you sign out, and ends by itself after 15 minutes without use. It is strictly necessary for the service you asked for, so we do not ask for consent for it, and there is nothing to accept or decline.

If you link a browser to your organizer, that browser also stores the key it received from your phone in its own storage (IndexedDB), so it can open your encrypted backup. It never leaves the browser and is removed when you unlink it.

We set no other cookies: none for analytics, advertising or tracking, and none from other companies.

3.3 Credits and purchases

We store how many AI scan and barcode lookup credits you have left and when your monthly free credits are next added. For each purchase we store the transaction identifiers from Apple or Google, the product, the credits granted and the date. Apple and Google also tell us when a subscription renews, is cancelled or is refunded. Apple or Google processes the payment; we never receive your card or bank details.

When you buy in the Android app, the app gives Google Play an identifier worked out from your account number, which does not reveal the number. It lets us make sure a purchase is only credited to the account that made it.

3.4 Encrypted cloud backups (Pro)

If you use cloud backups, your phone encrypts your organizer (setups, rooms, storage units, items with their names, quantities, notes, tags, groups and expiry dates, and your photos) with AES-256-GCM before uploading it. Each account has a key of its own. We never receive it.

Where the key is kept:

  • iPhone: the key comes from a key in your iCloud Keychain, so your other Apple devices on the same Apple account have it too.
  • Android: the key is created on your phone and kept in the phone's protected storage. It is not part of Google's device backups.
  • Passing it on: you can pass the key to another phone or to a browser yourself (section 3.5), and the app can show it to you as a recovery code to write down. We never see the key or the recovery code.
  • A new key: if you choose to start over with a new key, it is created on your phone and kept only there until you pass it on.

We store the encrypted files together with technical information needed to manage them: their size and checksum, when they were saved, a version number, which app saved them (iPhone, Android or web), a key fingerprint (it identifies which key was used, but cannot be used to decrypt anything) and, for photos, identifiers and sizes derived in a way that reveals nothing about the photo.

Because we don't have your key, we cannot read your backups, and we cannot restore them for you if you lose access to your key: that is, if none of your devices holds it any more and you don't have your recovery code.

While the app is open with automatic syncing on, it asks our server about once a minute whether another of your devices has saved a newer version. Only the version number is exchanged for that.

If your Pro subscription ends, we keep your encrypted backups for 90 days so you can continue if you subscribe again, then delete them (see section 9).

3.5 Web organizer and linked browsers (Pro)

To open your organizer in a web browser you link that browser by scanning a code with your phone:

  • the browser creates its own key pair. Its private key never leaves the browser; it is stored there for 30 days, or only for the open tab if you choose that;
  • your phone sends your backup key to the browser, encrypted so that only that browser can open it. Our servers pass it on but cannot read it;
  • the browser decrypts your organizer itself. Changes you make in the browser are encrypted in the browser before they are saved.

For each linked browser we store the name the browser gives itself (for example "Safari on Mac"), the key fingerprint, when it was linked and last used, when the link expires, and when it was removed. These records are deleted 30 days after the browser is removed or its link expires. While a link is being set up we also store the short-lived link request.

A phone that doesn't have your key yet can get it the same way: it shows a code, a phone that has the key scans it and approves, and the key travels encrypted so that only the asking phone can open it. For this we store only the short-lived request.

You can see and remove linked browsers at any time in the app or in the web organizer's settings. The web organizer locks itself after 15 minutes without use (unless you have unsaved changes), and you can lock it at any time. Locking removes the decrypted data from the browser.

3.6 Emails

We send only emails about your account: email confirmation, password reset, password changed, sign-out notices, account deletion, and notices when a browser or another phone was given your key or such a request was declined. We do not send marketing emails.

3.7 Security and server logs

Our servers keep technical logs to keep StackTail secure and working: IP address, time, the address requested, the result and the device or browser description. To protect against abuse we also count recent attempts per IP address or per (hashed) account name for a limited time, for example failed sign-ins. The web app also records reports of blocked content from browsers (the page and what was blocked), which helps us detect attacks.

3.8 AI photo scanning and barcode lookups

When you use AI photo scanning, the photo you choose is sent to our server and passed to Anthropic for item identification. When you look up a barcode, the barcode number is passed to EAN-Search. We do not store the photos or the barcode numbers.

3.9 Barcode scanning in the Android app (Google)

To read barcodes with the camera, the Android app uses a component from Google (ML Kit). The camera pictures are analysed on your phone and are not sent anywhere. The component itself sends Google technical data for diagnostics and usage statistics: device information (such as manufacturer, model and system version), the app's name and version, an identifier for the app installation, and performance and error figures. We cannot switch this off, we do not receive this data, and Google's privacy policy applies to it.

The iPhone app reads barcodes with Apple's built-in framework, which sends no such data.

4. Data we do not collect

  • Your organizer in readable form. We only hold encrypted copies we cannot open.
  • Location data.
  • Advertising identifiers or cross-app tracking identifiers.
  • Analytics, tracking or advertising cookies.
  • Usage statistics or crash reports. We use no analytics or crash-reporting tools; the one exception is the technical data that Google's barcode component collects in the Android app (section 3.9), which goes to Google and not to us.
  • Payment card or bank details. Apple and Google handle all payments.

5. Why we use your data (legal bases)

To provide StackTail to you (performance of a contract, GDPR Art. 6(1)(b)): creating and running your account, signing you in, credits and purchases, storing and returning your encrypted backups, the web organizer and browser linking, and the emails needed for these (email confirmation, password reset, account deletion).

For our legitimate interests (GDPR Art. 6(1)(f)): keeping StackTail and your account secure, which includes server logs, limits against abuse and security notices such as "password changed" or "a browser was linked"; finding and fixing faults; and defending legal claims. You can object to this processing (see section 10).

To comply with the law (GDPR Art. 6(1)(c)): where we have to keep or hand over information by law.

We do not use your data for advertising or profiling, and we make no automated decisions that have legal or similarly significant effects on you.

6. Who helps us (service providers)

We use these providers. Each processes data only on our instructions and under a data processing agreement:

  • DigitalOcean (servers, database and storage for encrypted backups). Our servers, database and backup storage are located in Frankfurt, Germany.
  • Anthropic (AI photo scanning). Receives the photo you choose to scan. Anthropic does not use this data to train its models and deletes it after a limited period under its data retention policy.
  • EAN-Search.org (barcode lookups). Receives only the barcode number, which is not personal data.
  • Postmark (account emails). Receives your email address and the content of the email.

Two companies provide their own services to you directly, under their own terms and privacy policies:

  • Apple (App Store, in-app purchases and subscriptions, iCloud Keychain). Apple handles payments and subscription renewals for the iPhone app, and iCloud Keychain holds your key on Apple devices.
  • Google (Google Play, in-app purchases and subscriptions, and the barcode scanning component in the Android app). Google handles payments and subscription renewals for the Android app and receives the technical data described in section 3.9.

7. International transfers

Your account data and encrypted backups are stored in the EU (Frankfurt, Germany). Some providers are based in the USA (Anthropic, Postmark, DigitalOcean as a company, and Apple and Google for their own services). Where personal data is transferred outside the EU/EEA, the transfer is protected by the European Commission's Standard Contractual Clauses (GDPR Art. 46(2)(c)) or, where the provider is certified, the EU-US Data Privacy Framework.

8. How we protect your data

  • End-to-end encryption for backups and the web organizer: only your devices hold the key.
  • Encrypted connections (TLS 1.2 or higher) everywhere, including a private, mutually authenticated connection between our web server and our API.
  • Passwords stored only as Argon2id hashes.
  • Sign-in tokens kept out of the web page, and in your phone's protected storage in the apps (the Keychain on iPhone, encrypted storage on Android).
  • Limits against password guessing and other abuse, and notices by email for important account events.
  • Linked browsers expire after at most 30 days and can be removed at any time, and you can sign out on all your devices at once.
  • Regular automated security testing.

No system is completely secure. If a personal data breach occurs, we notify the supervisory authority within 72 hours where required (GDPR Art. 33) and inform you without undue delay if the breach is likely to put your rights and freedoms at high risk (GDPR Art. 34).

9. How long we keep data

  • Account, credits and purchase records: until you delete your account. Deletion is carried out automatically within 48 hours of your request and removes all your data, including your encrypted backup files.
  • Encrypted backups: while you have Pro, and for 90 days after your Pro subscription ends, so you can continue where you left off if you subscribe again. After those 90 days they are deleted automatically. Deleting your account deletes them straight away (within 48 hours).
  • Older backup versions: we keep a version history of the last 50 versions plus one version per day for the last 7 days. Older versions are deleted automatically.
  • Sign-in sessions: until they end. Records of ended or expired sessions are deleted 30 days after their last use. Web app sessions end after 15 minutes without use (the web organizer keeps the session open while you are using it or have unsaved changes) and at the latest after 7 days.
  • Linked-browser records: 30 days after the browser is removed or its link expires.
  • Link requests (while linking a browser or passing your key to another phone): deleted within a day after they finish or expire.
  • Server logs: up to 30 days.
  • Abuse-limit counters: from a few minutes up to an hour.
  • Emails: our email provider keeps delivery records for up to 45 days.
  • Database backups: our hosting provider keeps backups of our database for 7 days, so deleted data disappears from those backups within 7 days.

10. Your rights

You have the right to:

  • access the personal data we hold about you;
  • rectification of inaccurate data;
  • erasure: delete your account at any time in the app (Profile → Delete Account), by following the steps on our account deletion page, or by emailing us;
  • restriction of processing while a question about your data is being resolved;
  • data portability: your organizer can be exported in the app, and we can send you your account data in a machine-readable format;
  • object to processing based on our legitimate interests;
  • withdraw consent where processing is based on consent (we currently do not rely on consent).

You can also remove linked browsers yourself at any time, and sign out on all your devices at once: in the web app's menu, or in the app under Profile → Sign Out on All Devices. Resetting your password does the same.

To exercise your rights, email contact@chaincoreindustries.com with the subject "Privacy Request — StackTail". We reply within one month. You can also complain to a data protection supervisory authority: our lead authority is the Estonian Data Protection Inspectorate (www.aki.ee), or you can contact the authority where you live (list of EU authorities).

11. Children

StackTail is not meant for children under 16. We do not knowingly collect personal data from children under 16. If you believe a child has given us personal data, contact us and we will delete it.

12. Changes to this policy

We may update this policy when StackTail or the law changes. The date at the top shows the latest version. If we make important changes, we will tell you in the app or by email before they take effect.

13. Contact

ChainCore Industries OÜ, Kruusa tn 3a, 10911 Tallinn, Estonia

Email: contact@chaincoreindustries.com

Subject: "Privacy Request — StackTail"

← Back to StackTail