Privacy policy
Last changed November 5, 2026.
snackbyte is Snackbyte LLC, a California limited liability company. This policy covers this site, its short links at go.snackbyte.io, and the snackbyte products you sign in to with Google. It says what we keep, why, for how long, and who sees it.
We don’t sell what we keep, and we don’t use it for advertising.
This site
snackbyte.io sets no cookies and runs no analytics. It serves its own typefaces. A page that shows a client’s own design may load that design’s fonts from Google Fonts, and then your browser asks Google for them.
Our server logs each request: your IP address, the page, what your browser says it is, and the time. We use the logs to keep the site running, and Google Cloud deletes them after 30 days.
A page that remembers a choice, such as a colour theme or answers you type, keeps it in your browser. It is never sent to us.
Short links
snackbyte’s short links, and the QR codes printed with them, go through go.snackbyte.io. Following one sends you on to where it points. Our server logs the request, as this site’s does: your IP address, the link, what your browser says it is, and the time. Google Cloud deletes those logs after 30 days. No click is counted, and nothing else about you is kept.
A link protected by a password sets one cookie when you unlock it, so you don’t type the password again for an hour. The pages go.snackbyte.io shows load nothing from any other site.
Signing in with Google
Today you sign in to snackbyte’s products with your Google account, through OpenID Connect. The part of snackbyte that does this is called nod. It stores no passwords, ever: Google checks who you are and tells us.
We ask Google for your account’s id, your email address and whether Google has verified it, your name, and your picture. We ask for nothing else in your Google account.
We use what Google sends to sign you in, and to tell the app you sign in to who you are.
What we keep
For each organisation whose apps you sign in to, which we call a tenant, we keep a separate record of you:
- You: an id we make for you, your snackbyte id, which is what an app knows you by; and whether your account is active.
- Each account you sign in with: the provider (Google, today), the provider’s id for that account, your email address and whether the provider verified it, and the name and picture the provider sent.
- Your email addresses, each marked verified or not.
- Each sign-in: your snackbyte id, the tenant, the app, the provider, your IP address, whether it worked, and when.
While you sign in, we hold the sign-in’s state, with its PKCE verifier encrypted. While you are signed in, we hold your session and its tokens. The sign-in servers also log each request, as this site’s server does, and so does nod’s landing page at nod.snackbyte.io.
How long we keep it
Your records have no set end. They are kept until you ask us to delete them.
Each tenant is set to keep sign-in records for a year, and older ones are deleted twice a day.
A sign-in in progress expires within an hour and is deleted within a day. A sign-in you start and do not finish leaves what Google sent about the account for fourteen days, then it is deleted. A sign-in you finish leaves its state, with your snackbyte id and the provider’s id for your account, for fourteen days or as long as your session lasts, whichever is longer. A session and its tokens last as long as the session. The request logs of the sign-in servers and nod’s landing page are deleted after 30 days.
Cookies on the sign-in pages
Signing in sets __Host-session, which keeps you signed in, and two cookies that carry a sign-in while it happens, for up to an hour. Each of these comes with a second cookie holding its signature. Signing out sets __Host-signed-out, which makes your next sign-in ask which account to use, kept until that sign-in or for up to 400 days. All of them are strictly necessary. The sign-in pages run no tracking and no analytics, and load nothing from any other site.
What an app receives
When you sign in to an app, it receives your snackbyte id, never your Google id, and which provider you used. It also receives your primary verified email address, your name and your picture; an app the tenant has not marked as its own asks you first.
What an app keeps
An app you sign in to keeps only what it needs to let you in and keep you signed in:
- Your session, under your snackbyte id, with the tokens nod gave it. A session ends within 30 days, and is deleted with its tokens.
- A sign-in, while it happens or after the app turns it away, for minutes.
- A record of you, under your snackbyte id: when you first signed in, and when you last did.
It sets only the cookies that keep you signed in and carry a sign-in while it happens, and runs no tracking and no analytics. Its server logs each request, as this site’s does, and Google Cloud deletes those logs after 30 days. All of it is held in Google Cloud, in the United States, and no one else receives it.
An app that keeps more than this has a section of its own on this page.
Where it is kept, and who sees it
It is held in Google Cloud, in Cloud SQL, in the us-central1 region of the United States. Provider credentials, signing keys and cookie keys are encrypted with Google Cloud Key Management Service.
The app you sign in to receives what is listed above, and Google Cloud holds all of it for us. No one else receives it.
What you can ask
Ask what we keep about you, and we will tell you. Ask us to delete it, and we will.
Changes
If what we keep, or who sees it, changes, this page changes first, and so does the date at the top.
Contact
Privacy questions: privacy@snackbyte.io. Security problems: security@snackbyte.io.