Privacy Policy
Last updated: 12 November 2026
GammaGrid is a small, independent project. This policy describes what the hosted service at app.gammagrid.io stores about you, why, and what you can do about it. It is written to be read rather than to be survived, and it says what actually happens in the software — every item below can be checked against the source code, which is public.
Who is responsible
The GammaGrid service ("GammaGrid", "we") decides what personal data is collected here and why, and is the controller for it.
GammaGrid is currently operated by an individual and does not yet trade through a registered company. The operator's formal identity and registered details will be published in this section as soon as that changes. Until then, every request under this policy reaches a person at hello@gammagrid.io, and that address is monitored.
What we store, and why
Only what the service needs to work. There is no advertising, no profiling and no third party buying anything from us.
| What | Why | Where it comes from |
|---|---|---|
| Email address | Identifies your account and is how we reach you about the service | Your Google or GitHub sign-in |
| Sign-in provider and its account identifier | Lets you sign back in as the same person | Your Google or GitHub sign-in |
A sign-in cookie (gg_session) | Keeps you signed in between visits | Created by us when you sign in |
| Your watchlist — the tickers you add | It is the product: we collect option chains for the symbols people are watching | You |
| Contracts you pin | Keeps your pinned list between visits | You |
| The dates you opened the app | Counted so we know how many people use the service. A date per person | Your visits |
| Which tab you opened, and when | So we can see which parts of the tool are worth the work and which nobody opens. The tab's name and the time — Screener, 19:40 — and nothing about what you looked at there: not the ticker, not the contract, not what you typed. Recorded when you MOVE between tabs, so it is a handful of rows per visit rather than a running log. Since 19 September 2026 each of those rows also carries one word — mobile, tablet or desktop — worked out from the name your browser sends with every request; that name itself is not kept. Each row also says whether the tab was open in your browser or in GammaGrid installed as an app on your home screen or dock — browser or standalone, as your browser reports it | Your visits |
| That you installed GammaGrid as an app, and when | So we can tell whether installing the app is worth offering at all. One row per install: the time and the same one word — mobile, tablet or desktop. Only Chrome, Edge and other Chromium browsers tell a site that it was installed, and only while you are signed in; Safari does not, so an install there is never recorded | Your browser, once, when the install completes |
| Which lesson of the Guide you opened from the app, and when | So we can tell whether the links from the app to the Guide on gammagrid.io are used at all. The lesson and the tab you clicked it from, and the time — max-pain, Max Pain / GEX, 19:40 — nothing else. Recorded only when you click one of those links; the Guide itself does not know who you are | Your clicks |
| Tickers you asked for but could not add | Shows us which symbols people want when they hit the free limit | You |
| Which site linked you here, and the campaign tag on that link, if any | So we know which of the things we write actually reaches people. We keep the site's name only — reddit.com — never the full address, because a full one can carry someone else's search terms | Your browser, once, when you first sign in |
| Which of our emails you were sent, and whether you opened the app through the link in one | So we know whether an email was worth sending at all, and stop sending the kind that nobody opens. The email's tag and the time — digest-2026-09, 19:40 — nothing about what you did once inside; and the list of who a sent email went to, so a delivery hiccup never sends it to the same person twice | Your visits, when the address carries the tag from one of our emails; our own send log |
| Whether your address is unsubscribed from our emails | So we stop sending, and keep stopping. When you unsubscribe through the link in one of our emails, our email provider records it and we mirror that back here — otherwise the settings screen would keep telling you email is on, and you would have no way to turn it back on if you changed your mind. The address, why the provider stopped sending to it, and when | The unsubscribe link in our emails, through Postmark |
| If you turn on push notifications: your browser's delivery address for them | So an update we send can reach this device. When you press Enable push notifications, your browser gives us an address at its own push service and two keys that let us encrypt a message only that browser can read. We keep those, the time, and the name and version your browser sent with that request (its User-Agent, as it sent it — nothing reads it today). One row per device; and, as with email, the list of who a sent notification went to | Your browser, when you turn push on under Notifications |
| Your browser's timezone and language | A rough idea of where in the world people are asking for this. Europe/Berlin — a continent, not a place | Your browser |
| Feedback you send through the form, and requests for data your AI assistant sends us on your behalf | So we can read it and fix things, and see which data people need that we do not have | You, or your assistant once you agree to send |
We do not store your name, your payment details (the service takes no payments), your IP address in the application, your broker, your positions, or anything about trades you make. GammaGrid has no connection to any broker and cannot see your account anywhere.
That promise about your IP address is worth being specific about, because the row above says we note roughly where in the world you are. We do not look your location up from your IP. The software can see that address and does not read it; what it reads is the timezone your browser announces on its own, which is how the charts already show you times in your own day. It says Europe/Berlin and nothing narrower, a VPN or a holiday changes it, and it is kept as one word next to your account.
Your Google or GitHub password never reaches us. Signing in happens on their side; we receive only the email address and an identifier.
Why we are allowed to store it
- To provide the service you asked for — your account, your watchlist, your pinned contracts and the sign-in cookie. Without these there is no service. (In GDPR terms: performance of a contract, Article 6(1)(b).)
- Our legitimate interest in knowing how much GammaGrid is used and in keeping it working and free of abuse — the per-day visit count, which tabs get opened, and the record of tickers people asked for. These are counted, not profiled: they tell us that the Screener is opened twice as often as the IV surface, which decides what gets built next. They do not tell us what any individual was doing — the tab's name and the time are recorded, never the ticker, the contract or anything you typed — and nothing here is used to make a decision about you. (Article 6(1)(f).)
- Your consent to be emailed about the product you signed up for — new views, fixed bugs, things worth knowing about GammaGrid. We send these through Postmark (see the table below); every one carries a one-click unsubscribe, and the same promise as always: that address is used for nothing else, and is never sold or shared. Until 11 September 2026 this section read differently — it said there was no mailing list and no newsletter provider, which was true until this feature existed.
- Your consent to push notifications, given twice — when you press Enable push notifications and in your browser's own permission prompt. Turn off in the same place takes it back, and so does blocking notifications in your browser. (Article 6(1)(a).)
Who else touches it
Running a service means other companies handle parts of it. These are all of them, and the list is deliberately short:
| Provider | What it does for us | What it sees |
|---|---|---|
| Supabase | Handles the Google and GitHub sign-in | Your email address and sign-in identifier |
| netcup | Hosts the servers and holds the backups, in Germany | Everything stored, at rest |
| Cloudflare | Serves the gammagrid.io website, and stands in front of the app: every request to app.gammagrid.io passes through its network, which also keeps the app's static files and — for signed-in visitors — ready-made screens close to you | The traffic in transit, including your session cookie on its way to our server; it does not store your account or your email address. A screen is handed out from its cache only after a signature check that names no account. The website's analytics use no cookies and do not identify visitors |
| Sentry | Tells us when the software breaks — on our servers or in your browser — so it gets fixed rather than reported | The error itself: which line of our code failed and in which release, and for an error in your browser, the page it happened on, the browser's name and version, its interface language (two letters, such as es) and whether the page was machine-translated. Your account number travels with it so we can tell "one person is affected" from "everyone is" — not your email address, and not your IP address. Stored in Frankfurt, Germany |
| Grafana Labs | Holds the service's own operational measurements and the software's log messages | Counts and sizes — how many tickers are being collected, how large the database is, how long a query took, how many people opened each tab — and the messages our software writes about its own work. Totals and averages only: nothing that identifies a person, and no account number. Stored in the EU |
| Postmark | Delivers the occasional email we send about the product — an owner decides what goes out and to whom, nothing automated per account | Your email address, and the content of that one email. No open or click tracking — we turned it off |
| Your browser's push service — Google (Chrome and most other Chromium browsers), Microsoft (Edge), Mozilla (Firefox) or Apple (Safari) | Carries a push notification from our server to your device. We do not choose it — your browser does, and the address it gives us names it | Only if you turned push on. When you do, your browser registers with that service itself, so it knows a browser subscribed to GammaGrid's notifications. When we send one, it sees that address, the time, the size of the message, and our server's address and contact email — not the message: it is encrypted for your browser before it leaves us. Not your email address and not your account. Where it is stored is set by the company that makes your browser |
| TradingView | Draws the price chart at the bottom of the Overview tab — the one part of the app that is not ours. It comes from TradingView's servers straight to your browser; our servers send TradingView nothing | When the price chart at the bottom of the Overview tab comes into view — you scroll down to it, or open it under the other charts — in the app and on the demo pages, your browser asks TradingView for the chart; until then it asks TradingView for nothing. TradingView then sees your IP address, your browser's name and version (its User-Agent), that the page was on app.gammagrid.io, and the ticker you are looking at, with the chart's settings: dark theme, English, UTC. Not your email address and not your account. The chart may set TradingView's own cookies and browser storage (see Cookies below); what TradingView keeps, where and for how long is covered by its own privacy and cookie policies, not by this one |
Until 11 November 2026 this policy did not mention push notifications at all, although the setting to turn them on has been in the app since 11 September 2026. It should have: the row for push in the table above and the push-service row in this one are what was missing.
Until 12 November 2026 this policy did not mention TradingView either, although its chart has been on the Overview tab from the start, and the Cookies section said there were no third-party trackers in the application — which that chart made untrue. The TradingView row above and the corrected Cookies section are what was missing.
Two honest notes about Sentry and Grafana Labs, because "no personal data" is a claim worth qualifying rather than repeating:
- Error reports are generated by software, and software occasionally puts something unexpected into an error message. We have turned off the setting that would attach the contents of variables to a report, precisely so that cannot happen by accident, and we do not send your email address at any point. A report from your browser records which requests the page made and which screens it moved between just before the error — not what you typed, and not what you clicked.
- Log messages describe what the service did — which ticker it collected, which query was slow. They are not written to contain personal data and we do not put email addresses in them.
An AI assistant you connect yourself is not on this list either, and the reason is different: it is not ours. GammaGrid can be connected to an assistant — Claude, or another one that speaks the same protocol — so you can ask about your own watchlist in your own words. If you do that, you authorize it yourself, through a consent screen that names what it may read, and you can take that authorization back. From then on the assistant receives what you ask it for on your behalf: the figures GammaGrid has for the tickers on your watchlist, and nothing about anyone else. It is your tool, working under your account, not a company we hand your data to — what it does with your questions and its answers is covered by your agreement with whoever runs it, not by this policy. Everything it can do is read-only, with one exception: when GammaGrid does not have the data you asked for, it can send us a request for that data — after showing you the wording, and only once you agree. The request lands in the same inbox as the feedback form, under the same rules.
The market-data provider that supplies option chains is not on this list, and deliberately: we ask it about ticker symbols, never about people. It has no way of knowing whose watchlist a symbol came from.
Where any of these process data outside the European Economic Area, they do so under their own published data-processing terms.
How long we keep it
- Your account and everything attached to it — until you ask us to delete it, or until the service closes. That includes which tabs you opened: it is attached to your account and goes when the account goes.
- Error reports and operational measurements — 30 days at Sentry and 14 days at Grafana, after which they are removed by those services and not by us. Neither is a record we keep; both exist to notice a problem while it is still happening.
- The sign-in cookie and its record on our side — 30 days from your last visit, then it is deleted automatically. Signing out deletes it immediately. We store only a one-way hash of the session token, never the token itself.
- Push notification addresses — until you turn push off for that device, or delete your account. If you block notifications in your browser's settings instead, the browser does not tell us; the address is removed the next time we send, when the push service answers that it is gone.
- Backups — the five most recent daily backups are kept and older ones are removed as new ones are made. This is worth stating plainly: after a deletion, your data can still exist in a backup for up to five days, and then it is gone from those too.
What you can ask for
You can ask us to show you what we hold, correct it, delete it, or send it to you in a portable form. You can object to the counting described above. You can also complain to your national data protection authority if you think we have handled something badly.
How: email hello@gammagrid.io. We will answer within 30 days, and in practice much sooner — the service is small enough that a person reads it.
There is no self-service delete button in the app yet. Until there is, deletion is done by hand on request, which is slower but not less complete.
What deletion does and does not remove
Deleting your account removes your account record, your watchlist, your pinned contracts, your visit dates, which tabs you opened, your push notification addresses, your ticker requests and your sessions.
Two things survive, and you should know about both:
- Feedback you sent us stays readable, with your name detached from it. If you wrote "the GLD chart is empty", that sentence remains in our inbox as a bug report with no author. If you want the text itself gone as well, say so in your deletion request and we will remove it.
- The market data collected for the tickers you watched stays. It is option prices and open interest — facts about contracts traded on a public exchange, not information about you. Once a symbol has been collected, that history exists independently of who asked for it, and other people are watching the same symbols.
Cookies
Ours: one. gg_session, which keeps you signed in. It is strictly necessary — remove it and you are signed out. We set no advertising cookies and no analytics cookies.
One part of the application is not ours: the TradingView price chart at the bottom of the Overview tab, in the app and on the demo pages (see Who else touches it). It loads from TradingView once it comes into view, and TradingView may set its own cookies and browser storage through it, under its own policies. We do not choose them, do not read them and receive nothing from them; your browser's settings for third-party cookies apply to TradingView's cookies. Until 12 November 2026 this section said there were no third-party trackers in the application, which that chart made untrue.
The gammagrid.io website counts page views through Cloudflare Web Analytics, which works without cookies and without identifying visitors.
The demo pages at app.gammagrid.io/demo show the free list without an account and set no cookie of ours — the TradingView chart above may set TradingView's own. They count four things, anonymously and without any identifier: that a page was opened, that a view was switched, that a sign-in button was pressed, and that a link to the Guide was followed — totals per minute, nothing about who. If you sign in from a demo page, the sign-in records that you came through the demo, the same way it records a referring website.
Security
Traffic is encrypted in transit. Sign-in tokens are stored as one-way hashes, never in a form that can be replayed. The database is not reachable from the public internet, and backups are held on storage that only the production machine can reach.
GammaGrid is a beta operated by one person. That is not a reason to expect it to be careless, and it is a reason not to store anything here that you would not want to lose — which, given the list above, is nothing you have not already given to a search engine.
Children
The service is not intended for anyone under 16, and we do not knowingly hold data about anyone under 16.
Changes to this policy
We will change this document as the service changes. The date at the top always moves when it does, including for small corrections, so that you can tell whether you have read this version. Every past version exists in the project's version history.
Contact
hello@gammagrid.io