Privacy Policy
What we collect, why, where it lives and how to reach us. Effective 18 October 2026.
Who we are
jstash is run by Neonook Pty Ltd (ABN 80 124 800 853), Australia. We handle personal information in line with the Australian Privacy Principles. Questions or requests: support@jstash.app.
What we collect
- Your account (if you sign in): your GitHub user ID and username, display name, avatar URL, your email if GitHub shares it or you add it; or, for Google sign-in, your Google account ID, name, picture URL and your email only if Google has verified it; your plan, your API key names, and when things were created and last used. Each sign-in method creates its own jstash account: signing in with Google and with GitHub using the same email creates two separate accounts; jstash does not merge accounts by email.
- Credentials: API keys, session tokens and edit tokens are stored only as one-way hashes. We can’t read them back.
- Your bins: the JSON you store, plus its name, size and timestamps. For trial bins, we also note whether the JSON ever contained a web link, a long block of encoded data or script code, to spot abuse; the note stays with the bin if you claim it.
- Usage counts: daily counts of bins created, updated and privately read per account. Trial counts per network use a daily hash of the IP address (IPv6 by /64) that changes every day. We keep monthly write and read counts per account for about 14 months. Monthly counts contain nothing about content.
- Website and sign-up analytics: when you visit jstash.app or the sign-in page of the dashboard, your browser sends us the page path, whether this is the first page of your visit, how your visit began (the UTM tags on the link you followed, or the hostname of the website that linked to us), a rough country, and whether you use a phone, tablet or computer. We add it to daily counts. To count each visitor once a day we keep a hash of your IP address and browser type that is made with a secret key and the date, so it can’t be turned back into your address or matched across days; we delete these hashes after two days and never store the raw address. This runs in your browser’s session storage for that visit only (nothing is kept after you close the tab, and there are no cookies), and it does nothing if your browser sends Do Not Track or Global Privacy Control. If you then create an account, we keep how your visit began (the campaign or referring website and the first page you landed on) with your account, so we can tell which marketing works. We use no third-party analytics, and nothing from it is sold or shared. We keep the daily counts for up to about two years.
- Billing: we hold your Stripe customer ID, subscription status, plan and dates. We never see card numbers. Stripe holds payment and billing details. Link also holds these details where it acts as seller.
- Security log: sign-ins, sign-outs, API key changes, claims, creating, changing and deleting apps, changes to your account details (which details changed, never their values), deleting an app user’s data, account deletion, moderator actions (including a moderator viewing a bin’s content) and addresses blocked after repeated failed sign-ins, with a keyed hash of your IP address that changes every month — never the raw address.
- Request logs: for each API request, the time, method, path, status and duration, the website that sent the request if it isn’t one of jstash’s own, the account, key, app and bin IDs involved, and a keyed hash of your IP address that changes every month. Never the raw address, request bodies, credentials or cookies.
- If you use an app built with jstash Apps: the documents that app saves for you, with their names, sizes and save times, when you first and last saved, and daily counts of your saves and reads. They’re filed under a one-way hash of your user ID from the app’s login provider; we never see your password, and we don’t keep your email address or other details from your login. The app’s developer decides what’s stored, and their privacy policy covers it — ask them first about access or deletion. Cloud Notes, our demo at jstash.app/demo/, is an app built with jstash Apps that jstash runs itself, so this policy covers it.
- Things you send us: support messages and the reply email you give, abuse reports (your email is optional; we keep a keyed hash of your IP address that changes every month), and your email if you request a Pro invite or ask to hear about Max.
We don’t use third-party analytics, advertising or tracking cookies. The website sets no cookies of its own. On our Cloud Notes demo (jstash.app/demo/), Google’s sign-in script sets one cookie, g_state, for Google’s sign-in. Signing in to jstash sets one session cookie on api.jstash.app (30 days) and a short-lived cookie during GitHub sign-in.
Why we use it
To run jstash: store and serve your bins, sign you in, enforce limits, prevent and investigate abuse, answer support requests and reports, send notices about the service, and send the Pro invites and news you asked for. We don’t sell personal information or use it for advertising.
Public bins
Anyone with a public bin’s URL can read it. We ask search engines not to index bins, but we can’t control who shares a URL. Don’t put personal information in a public bin. See the acceptable use rules.
Where it’s stored and who helps us
- Cloudflare hosts jstash. Our database, bin storage and backups are located in Cloudflare’s Oceania region. Cloudflare places them there on a best-effort basis rather than guaranteeing it. Public bins are also cached on Cloudflare’s global network so they load quickly, and request logs are kept by Cloudflare for up to 7 days.
- GitHub handles sign-in.
- Google handles sign-in to the Cloud Notes demo.
- Stripe handles payments and holds payment and billing details. Link does so where it acts as seller. Card details are entered on Stripe’s pages and never reach jstash.
Cloudflare and GitHub are US companies, so some information may be handled outside Australia. They act for us under their own data protection terms. The companies that handle data you store with jstash are listed on our subprocessors page.
How long we keep it
- Account details and bins: until you delete them or your account. Deleting your account removes your personal details straight away; your bins and app documents are then deleted in the background, usually within two hours (very large accounts can take several days). Our database keeps an automatic recovery history, so deleted account details can remain there for up to 30 days. Backups are covered below. If we delete an account ourselves (one closed for breaking the Terms, or a suspended account deleted at its owner’s request), we keep its GitHub user ID, and nothing else from the profile, so that GitHub account can’t sign up again.
- Trial bins: 7 days, unless claimed.
- Usage counts (trial, account and app): about two days. Monthly write and read counts: about 14 months.
- Billing records: jstash keeps billing records for at least 5 years. Stripe keeps its own records after a jstash account is deleted. Link also keeps its own records where it acts as seller.
- App documents: until you, the app’s developer or the developer’s account deletes them (account and app deletions usually finish within two hours; very large apps can take several days).
- Security log entries: kept for security, linked only to an account ID that no longer identifies you once the account is deleted and any support messages from you have been removed (within 12 months), unless we deleted the account ourselves and kept its GitHub user ID (above).
- Invite and launch requests: deleted once we’ve invited you or announced the plan.
- Support messages and reports: while we handle them, then up to 12 months.
- Backups: once a day we back up our database and the contents of bins and app documents, encrypted, to separate storage. Each backup is deleted automatically after 31 days (Cloudflare can take up to a day longer to remove it). So anything deleted from jstash, including account details, bins, app documents, support messages, reports and invite requests, can remain in backups for up to 32 days after it’s deleted. We use backups only to recover jstash after a fault, never to restore individual items on request. If we ever have to recover from a backup, things deleted since that backup can come back: we’ll delete again what we know was deleted, tell account holders, and delete anything else you point out.
Your choices and rights
You can see and correct your name and email in the dashboard, and delete your account at any time (if it’s suspended, email us and we’ll do it). To ask for a copy of your information, or for anything else, email support@jstash.app. If you think a bin contains your personal information, report it at jstash.app/report. If you’re not happy with our response, you can complain to the Office of the Australian Information Commissioner at oaic.gov.au.
Security
Everything is served over HTTPS. Credentials are stored only as hashes, public and private bins live in separate storage, and the moderation console sits behind its own sign-in. Report a security issue to support@jstash.app (see security.txt). No system is perfectly secure; if something goes wrong that affects your information, we’ll tell you as the law requires.
Changes
If we change this policy we’ll update the date above, and tell account holders about significant changes.