Essential cookies by default. The browser ID, load-time metrics and error replays only run if you choose "Accept all".
Last updated: 15 November 2026
SupStack is an experimental supplement research tool operated by Baher Alhakim, currently in the process of being established as a non-profit association (Verein) in Austria. We take your privacy seriously and collect only the minimum data needed to provide the service. This policy explains what we collect, why, and how it is handled.
The data controller responsible for your personal data is:
Baher Alhakim
(pending: SupStack Verein, Austria)
Email: hello@supstack.me
Once the Verein registration is complete, the association will assume the role of data controller.
When you create an account, we store your email address for authentication. You can sign in with a one-time link or code that we email you, or with Google. If you use Google, Google passes your email address to us and may also pass the name and picture of your Google account. We never see or store a password.
If you choose to fill in your health profile, we store information you provide such as age, weight, biological sex, health goals, health conditions, and medications. This data is used solely as a filter to refine which existing information is shown to you, for example, surfacing relevant safety warnings or narrowing supplement lists to match your selected goals. It functions as a refined search, not a personalization engine. No new content or individualized clinical assessments are generated from your profile. It is never used for clinical decision-making, and your saved profile is not shared with third parties. The quiz is separate: see "AI features on the website" below for where its answers go.
Your saved supplement stack, dosage notes, and experiment check-in responses are stored in your account to provide the service. Experiment verdicts are generated locally from your self-reported data.
We use Vercel Web Analytics to count page views and see aggregate usage. It does not use cookies and does not follow you across sites. It runs for every visitor, including if you choose "Essential only" in the cookie banner. Vercel Speed Insights (page performance) runs only if you accept analytics in the banner. For the public API (/api/v1, used by our CLI and MCP server), we count requests per endpoint and client type. Your IP address is turned into a one-way hash with a key we discard after a day, so we can estimate how many different callers there were without storing the address or being able to recognise you later.
If you choose "Accept all" in the cookie banner, your browser keeps a random browser ID (sup-anon-id) in local storage. It is created when you accept and stays until you clear site data or choose "Essential only", which deletes it. Until you accept, and if you choose "Essential only", no browser ID is created, and one left from an earlier visit is neither read nor sent. It is not a cookie. Once you have accepted, we attach it to four records in our database. The first is key steps (adding to a stack, signing in, clicking a buy link and a few stack-check steps), which also carry your account id if you are signed in. The second is quiz steps (which step of the quiz you reached). The third is searches that found nothing, with the search text and the page. The search text is whatever you typed, so it can hold anything you wrote in the box, including a name or an email address if you typed one. The fourth is where a visit came from: the referring site, any campaign tags in the link and the first page you landed on, once per browser session. For shared report and stack links we keep only the kind of page, not the link itself. Without the browser ID the same four records are still written, but with no ID on them, so they cannot be linked to each other or to your other visits. None of these records asks you for a name or an email address. We keep all four for 12 months and then delete them. Deleting your account deletes the key steps and quiz steps recorded while you were signed in, because they carry your account id. Key steps and quiz steps from before you signed in are not deleted with it. Searches that found nothing and where a visit came from have no account id at all, so deleting your account never deletes them. Everything that is left goes when the 12 months are up.
If you use the Telegram bot or phone agent, conversation history is stored to provide continuity. Telegram user IDs are stored for account linking. For phone calls, ElevenLabs sends us the caller's phone number and a transcript of the call. We log both for quality purposes, keep them for 90 days and then delete them. They are not shared externally. If your account has a phone number, calls from that number are included in your data export and deleted with your account.
AI processing disclosure: Telegram and phone conversations are processed by AI language models (Anthropic Claude for text, ElevenLabs for voice). Your messages are sent to these providers in real time to generate responses. These providers may process your data under their own privacy policies. We do not use your conversations to train AI models.
Four features on the website send what you give them to Anthropic (Claude), which processes it for us and returns the result. Each one runs on its own at that step of the flow, and none of them needs an account.
Anthropic is a US company (see section 9) and handles this data under its own privacy terms. We do not use it to train AI models.
If you sign up for the research digest, or tick the box for updates when you get your quiz report, we store your email address, that you agreed, where and when you agreed, and the date you unsubscribed if you do. Every one of these emails carries an unsubscribe link. After you unsubscribe we keep a record, marked as unsubscribed, so that we do not send you further subscribed updates. It stays until you delete your account or write to us. Resend sends these emails for us, and also the quiz report you ask us to email you and notifications from your account. The quiz report stays stored with that address. Deleting your account deletes the subscription records and the quiz reports emailed to your account email.
Three forms take an email address without an account. The API key request asks for a name, an email address, what you will use the key for, and optionally a company and a website. If we issue a key, we keep it as a one-way hash together with your name and email, the date it was last used and how many requests it made. The feedback form stores your text, what kind of issue it is, the supplement it concerns if any, and an email address if you give one. The suggestion form stores your text and an email address if you give one. We keep requests, feedback and suggestions for 24 months, and a key for 24 months after it is revoked. A key that is still active is kept while it is active. Your data export and account deletion include these records when you sent them under your account email, and deletion revokes an active key first. For anything you sent under a different email address, write to hello@supstack.me.
To stop abuse we limit how often one visitor can use our forms, the AI features and the API. The counters live in Upstash (Redis). A counter is named with a one-way hash of your IP address, made with the same daily key as above, and never with the address itself. For the API key request form the counter is named with a keyed hash of the email you typed, because that limit lasts 24 hours and a daily key would reset it part way through. For signed-in features the counter carries your account id, and for the Telegram bot your Telegram id. A counter lasts as long as its limit window, from one minute to 24 hours. We also keep the ids of recent Telegram messages in Upstash for about an hour, so that a message is not handled twice. They hold no message text.
We do not sell or rent your personal data, and we do not use it for advertising or to make clinical decisions. We share it only with the service providers listed in section 8, which process it for us. That includes Anthropic for the AI features in section 3.
Under the EU General Data Protection Regulation (GDPR), we process your data on the following legal bases:
Health-related profile data (conditions, medications) is processed under explicit consent (Art. 9(2)(a)) as a special category of data. This data is used only as a content filter and is never used for profiling, automated decision-making, or clinical purposes.
Automated decision-making (Art. 22): SupStack does not engage in automated decision-making that produces legal or similarly significant effects. Experiment verdicts are algorithmic summaries of your own self-reported data, provided for personal reflection only. They carry no legal, medical, or binding significance.
Your data is stored in Supabase (hosted on AWS infrastructure) with row-level security policies that restrict access to your own data. Authentication is handled by Supabase Auth. All data is transmitted over HTTPS.
As a beta project, we implement reasonable security measures but cannot guarantee absolute security. Do not store highly sensitive information (financial data, government IDs) in your SupStack profile.
Data breach notification: In the event of a personal data breach that poses a risk to your rights and freedoms, we will notify the Austrian Data Protection Authority within 72 hours (per GDPR Art. 33) and inform affected users without undue delay (per GDPR Art. 34).
SupStack uses only essential cookies: the Supabase session tokens for authentication (names starting with sb-), supstack-consent, which remembers your choice in the cookie banner, and NEXT_LOCALE, which remembers the language you chose. We do not use advertising cookies, tracking cookies, or third-party cookies. Local storage is used to save UI preferences like your supplement goal selection, and, only if you choose "Accept all", the random browser ID described in section 3 and a session flag that stops one visit being counted twice.
We use the following third-party services:
Each service has its own privacy policy. We only share the minimum data required for each service to function.
Some of the third-party services listed above may process your data outside the European Economic Area (EEA). Specifically:
Where data is transferred outside the EEA, these providers rely on appropriate safeguards such as Standard Contractual Clauses (SCCs) approved by the European Commission, or adequacy decisions. We only share the minimum data necessary for each service to function.
SupStack is for adults (18+) only. We do not knowingly collect personal information from anyone under 18. If you believe a minor has provided us with data, please contact us and we will delete it.
Under the GDPR, you have the following rights regarding your personal data:
For restriction or objection requests, contact us at hello@supstack.me. We will respond without undue delay and in any event within one month.
During beta, data may also be deleted as part of development updates. We will try to notify users before any planned data resets.
We retain your data for as long as your account is active. Some records go sooner: Telegram conversations after 90 days without a new message, phone call records 90 days after the call, the site records described in section 3 (key steps, quiz steps, searches that found nothing and where a visit came from) 12 months after they were created, and API key requests, feedback and suggestions 24 months after they were sent. An API key is kept for 24 months after it is revoked, and while it is active. The record of your unsubscribe from our subscribed updates is kept so that we do not send you further subscribed updates, until you delete your account or write to us. If you delete your account, all associated data (profile, stack, experiments, conversations) will be permanently deleted. If you delete a single experiment in which you reported a serious reaction that stops SupStack from starting that product again, we keep a short record of your account, the product and the reason for the hold, but none of your answers, so that a new experiment with that product stays refused, and we delete that record with the rest of your data when you delete your account. Aggregate analytics counts carry no personal data and are kept.
If you believe your data protection rights have been violated, you have the right to lodge a complaint with a supervisory authority. The relevant authority for SupStack is:
Austrian Data Protection Authority (Datenschutzbehörde)
Barichgasse 40-42, 1030 Vienna, Austria
Website: www.dsb.gv.at
We may update this policy as the project evolves. Material changes will be noted on the What's New page. Continued use after changes constitutes acceptance.
Questions about your privacy? Contact Baher Alhakim at hello@supstack.me or via the About page.