Privacy Policy
Effective date: October 11, 2026
This Privacy Policy explains what personal information SynthGap ("we," "us") collects when you use the SynthGap web application and related services (the "Service"), how we use and share it, and the choices and rights you have. We are the controller of the personal information described here. We are based in Cyprus, in the European Union. You can reach us at alikesen54@gmail.com or Sehit Dumenci Street No 10, 99010 Nicosia, Cyprus.
The short version
- You sign up with your email address and a password, or by continuing with Google. We use your email to identify your account and to contact you about it, not for advertising, and other users never see it.
- We check new email addresses with Verifalia (to reject invalid or disposable ones) and send our account emails, such as the link to confirm your address or reset your password, through Resend.
- Stripe handles payments. We never see or store your card number.
- Your research content is private: other users cannot open it, and runs cannot be shared.
- To produce results we send your content to AI and infrastructure providers (listed on our Subprocessors page). We do not sell personal information and we do not use your content to train AI models.
- We set one essential cookie to keep you signed in, and a second short-lived one while you continue with Google. No analytics cookies. Advertising measurement by Google is off unless you accept it in a notice on our public pages (never asked in the app, which loads Google's tag only for up to twenty seconds to report a sign-up or first payment, and only if you accepted).
- You can delete your account and all your data yourself, any time, from the Account menu in the app. To ask for a copy of your data or a correction, email alikesen54@gmail.com.
1. Information we collect
Information you give us
- Account information. Your email address and password. (Accounts created before we asked for an email may use a username instead, and can add an email under Settings in the account menu.) The password is stored only as a salted, one-way hash, so we cannot read it. Each new account also gets an automatically generated ID. We use it internally. Your email address is never shown to other users. When you sign up or change your email, we also check the address with a third-party service (Verifalia), which tells us whether it can receive mail and is not a disposable address, and deletes the address a few minutes after the check. We keep only the result it returns (for example "deliverable"), and we record whether you have confirmed the address and when.
- Your content. The research topics and clinical areas you enter; the topics you choose to analyse; for each, the version of the topic the Service worked out (what it changed and why), the studies it looked at, whether it included or took out each one and why, what it assessed of each included study (whether it has enough data, its design, size and finding), the preview meta-analysis (the numbers an AI entered for each study, the short sentence each number was taken from, the results and the pictures) and the reports. For runs created under earlier versions of the Service it can also include data extracted from studies, pooled results, protocols and PICO questions, search strategies, screening decisions, risk-of-bias judgments, PRISMA entries, manuscript text and notes, and files you uploaded (PDF or text; we keep both the original file and the text extracted from it). It also includes your chat conversations with the run assistant (your questions and its answers), kept with the run, and the text we extract from any PDF you upload to an analysis (we keep that text, not the PDF itself, and you can remove it again yourself at any time) and the results the Service generates from these inputs. For a sweep it also includes the order of the topics it found, and, kept with the sweep and not shown in the app, the assessment an AI agent made of each topic (a score and a short note), which is used only to make the order; write to us if you would like a copy. It also includes the topics you reserve: for each, its title, the PMIDs of its included studies, its PICO and the run it came from. A reserved topic is compared with the topics that other users' discoveries find, so that it is not shown to them, and nobody is ever shown another user's reservation or who holds it.
- If you sign up or log in with Google. Your browser goes to Google's own sign-in page, and we never see your Google password. Google tells us your email address, whether it has verified it, and a stable identifier for your Google account. We ask for nothing else: no name, photo, contacts or calendar. We keep that identifier and that address with your account. We do not send an address Google has already verified to Verifalia. An account made this way has no password until you ask for a reset link.
- Messages to us. If you email us, we keep your message and our reply.
Billing information
When you top up, subscribe or upgrade from Plus to Pro, you are sent to a page hosted by Stripe, which collects your payment method, billing name, billing email and other billing details and processes the payment. We never receive or store full card numbers. We send Stripe your email address (so receipts and payment notices reach you), an internal reference to your SynthGap account, and what you are buying (the plan you chose, the amount of the top-up, or that you are moving from Plus to Pro and the amount of the difference). If you change the email on your account, we update it at Stripe too. Stripe sends us back a customer ID and, for a plan, a subscription ID and your subscription status, which we store in your account record; and for a top-up or an upgrade, what was paid. The Free plan needs no card: we collect no payment details for it. In Stripe's dashboard we can also see your billing email and the brand and last four digits of your card, which we use for billing support. When you open Settings, the Service asks Stripe for your recent receipts and invoices so it can show them to you, and Stripe may email receipts and payment notices to your billing email. Where sales tax or VAT applies, Stripe also uses the billing address and any tax ID you enter at checkout to calculate it. Stripe's use of your information is governed by its own privacy policy.
Information collected automatically
- Account and usage records. When you created your account, your plan and its billing period, how much of the current month's usage you have used and the date that month's usage counts from, the last few things that used it (the kind of work, when, and its share of the month), the credit you have bought, when, and how much of it is left, the upgrades from Plus to Pro you paid for (the amount, the billing period and when), any runs you bought before the plans changed and how many of them you have used, which version of our Terms you accepted and when, each time you confirmed the renewal terms of a plan before checkout (which plan, when, and which version), and whether your last payment failed.
- Which of our links you came from. Some of the links we share end in a short label we chose, for example
?ref=newsletter. While you move between our pages the label stays in the web address, and if you then create an account we save it with your account record, so that we can see which of our own links bring people to the Service. The label names a link, not you, and anyone can type one into an address. We don't use a cookie or browser storage for it, the Service keeps nothing else about where you came from, and we don't use it for advertising or to build a profile of you. - Advertising measurement (only if you accept it). We advertise SynthGap with Google Ads. On our public pages (not the app page) a notice asks whether Google's advertising tag may load. Until you press Accept, nothing is requested from Google. If you accept, Google's tag runs in your browser and Google receives the pages you view on those pages, the address you came from, any ad-click identifier in the address, cookie identifiers, your IP address and details of your browser and device. We see the results in our Google Ads account (for example how many visits followed an ad click, and how many of those visitors then signed up or subscribed). To count that, the app page does not load the tag while you work, but for up to twenty seconds right after you create an account, or right after your first plan payment is confirmed, it opens a hidden page of ours that loads the tag and reports the sign-up or payment. That report happens only if you accepted the notice in its current wording (the one that mentions sign-ups and subscriptions) and your browser is not sending Global Privacy Control. Besides what the tag always sends (which, from that hidden page, includes the address of the app page, /app, and nothing you have written or found), Google then receives the kind of event, a random order number made for the purpose (not your account name, your email address or any Stripe number) and, for a payment, the amount. The tag is set up for measurement only: ad personalisation (remarketing) is switched off, so your visit is not used to show you ads elsewhere. Your choice is kept on your device, not by us. See the Cookie Policy.
- Run records and logs. For each discovery run, a log of what the AI agent did (searches issued, papers examined, its output), timestamps, and model-usage statistics.
- Technical data. Your IP address, browser type and request details are processed by our hosting infrastructure when you use the Service and may appear in infrastructure logs kept by our hosting provider for security and troubleshooting.
- Cookies and local storage. See our Cookie Policy.
2. How we use your information
| Purpose | Examples | Legal basis (EEA/UK) |
|---|---|---|
| Provide the Service | Create and secure your account and let you sign in with your email or Google; run discovery and the deep analysis of the topics you choose; store your work; enforce plan limits | Contract |
| Take payments and manage subscriptions | Checkout, subscription status, invoices, refunds | Contract; legal obligation (tax and accounting records) |
| Confirm your email and reset your password | Email you a link to confirm your address, or to choose a new password | Contract; legitimate interests (keeping accounts secure) |
| Keep the Service safe | Detect abuse and misuse, for example by screening for invalid or disposable email addresses, requiring new Free accounts to confirm their email, pausing the Free plan for the rest of a day when all Free accounts together have used a daily cap (a total, kept without names), and stopping a deleted account's email address from opening a new account for 12 months; protect accounts and infrastructure | Legitimate interests (keeping the Service secure and the Free plan fair) |
| Support and service messages | Answer your emails; contact you about your account, billing or security; tell you about changes to our Terms and Policies | Contract; legitimate interests |
| Reliability and troubleshooting | Diagnose failed runs; monitor performance and cost; fix bugs | Legitimate interests |
| Learn which of our links work | Count the sign-ups that came from each link we share (the link label in Section 1), so we know where it is worth sharing the Service | Legitimate interests (knowing which of our own links bring visitors) |
| Measure our advertising | If you accept the advertising notice on our public pages: Google's tag tells us whether an ad of ours led to a visit, a sign-up or a first payment (Section 1) | Consent, which you can withdraw at any time (Cookie Policy) |
| Legal compliance and record-keeping | Keep records of the Terms you accepted; respond to lawful requests | Legal obligation; legitimate interests (proving what you agreed to) |
Your account information and your content are never used for advertising or to build advertising profiles. The only advertising use is the optional measurement above, which concerns visits to our public pages and the sign-up or first payment that follows, and runs only if you accept it. We do not make automated decisions about you that have legal or similarly significant effects. (The AI in the Service drafts suggestions about research literature, which you review. See our AI Output & Research Disclaimer.)
3. AI processing of your content
To produce your results, the Service sends parts of your content to AI model and embedding providers listed on our Subprocessors page. Depending on the stage, that can include your chat questions together with a summary of the run they are about, your topic text and its PICO, the search phrases the AI writes from them, article titles and abstracts, short passages of full text (from open-access articles retrieved through Europe PMC or an open-access PDF link, or from PDFs you upload), around keywords the AI chooses, which we use to assess the studies and to write the report together with the reviews found on the topic. To look up open-access copies of articles we send article identifiers (PMIDs and DOIs) to OpenAlex, Semantic Scholar and Unpaywall. We use these providers through their commercial APIs; their own terms and privacy policies govern how they handle data they process for us. We do not use your content to train AI models. Please don't enter information that identifies a patient or other individual.
To keep a reserved topic from the users it is reserved against, when another user's discovery finds a topic that shares studies with a reserved one, the titles and PICO of the two topics are sent to the AI model provider, which says whether they are the same. The result of that comparison is not kept except as the other user's result (the topic is left out of it).
4. How we share information
- Service providers. We share information with the providers on our Subprocessors page so they can host the Service, process payments and run the AI features. They may use it only to provide those services to us, except where their own policies say otherwise (for example, Stripe's use of payment data for fraud prevention and legal compliance).
- Google, if you choose it to sign in. Pressing "Continue with Google" sends your browser to Google, which learns that you are signing in to SynthGap and handles your sign-in under its own privacy policy. We send it only what the sign-in needs: our application's identifier, the address to return you to, and a signed one-time value that ties the reply to your browser. Signing in loads no Google script or button into our pages.
- Google, if you accept advertising measurement. If you press Accept in the notice on our public pages, Google's tag runs in your browser and Google receives the information described in Section 1. Google handles it under its own privacy policy. We send Google no account information and none of your content. The tag is not loaded on the app page while you work, apart from the short report of a sign-up or first payment described in Section 1, which carries no account information either.
- Legal and safety. We may disclose information if we believe it is required by law or legal process, or necessary to protect the rights, safety or security of users, the public or the Service.
- Business transfers. If we are involved in a merger, acquisition or sale of assets, information may be transferred as part of it. We would give notice in the Service before it became subject to a different privacy policy.
- With your direction. We share information when you ask us to.
We do not sell personal information, and we do not share it for cross-context behavioral advertising. We have not done either in the past 12 months. (The advertising measurement you can accept is for measurement only: ad personalisation is off.)
5. International transfers
We and our providers process information in the United States and other countries, which may have data-protection laws different from those where you live. Where the law requires it, we rely on safeguards such as the European Commission's Standard Contractual Clauses (with the UK Addendum where relevant) or a provider's certification under the EU-U.S. Data Privacy Framework.
6. How long we keep information
| Information | Retention |
|---|---|
| Account record (email address, account ID or username, password hash, plan and usage counters, Stripe IDs, record of accepted Terms, the label of the link you signed up from, the identifier a Google sign-in gave us) | Until you delete your account, which removes it immediately |
| Reserved topics (the title, the PMIDs of the included studies and the PICO of a topic you reserved, and the run it came from) | Until you release it, or you delete your account, which removes it immediately |
| Your content (runs, logs, chat conversations, uploaded files) | Until you delete the run, or your account; either removes it from our active systems immediately. The text kept from a PDF you added to an analysis can also be removed on its own, at any time, and goes at once. We do not currently delete content automatically |
| Billing records (held by Stripe and by us) | Stripe keeps transaction records as long as tax, accounting and other laws require, typically up to seven years. Deleting your account also deletes your customer profile and saved payment methods at Stripe |
| Deleted usernames | Reserved for 14 days after deletion, so an old sign-in can't be used on a new account with the same name, then removed |
| A fingerprint of a deleted account's email address (a keyed one-way hash, never the address itself) | 12 months after deletion, so the address can't be used to open a new account; then removed. It cannot be turned back into the address |
| Short-lived counters that cap how many emails we send and addresses we check (keyed by an internal account ID or a one-way hash of an address) | Up to 2 days |
| Infrastructure logs | For a limited period set by our hosting provider |
| Emails to us | As long as needed to handle your request and keep a reasonable record |
When you delete your account we immediately delete your account record, every run you started and all files you uploaded from our active systems, and we cancel any subscription. Copies may remain for a short period in routine backups kept by our hosting provider, and in anything others copied from a run while runs could still be shared. Topic-based search indexes built from public PubMed records (which may be named after a topic) are shared infrastructure, are not linked to your account, and are not deleted with it. Stripe keeps transaction records as the law requires.
7. Your rights and choices
Everyone. You can delete your account yourself at any time: open the account menu at the bottom of the sidebar, choose Settings, then Delete account. We immediately and permanently delete your account, all of your runs and uploaded files, and your customer profile at Stripe, and we cancel any subscription (Section 6 explains what we keep). The one thing we keep is a one-way fingerprint of the email address, for 12 months, so that it can't be used to open a new account straight away. You can also delete any single run yourself, from your history or the run's own page (this removes the run and its uploaded files immediately). You don't need to contact us or give a reason. To get a copy of your personal information, to have it corrected, or if you can't sign in, email alikesen54@gmail.com from the address on your account (or, on an older account without an email, with your username).
Verifying it's you. Before acting on a request sent by email, we may need to confirm that the account is yours, for example by checking that the request comes from the email address on the account, by giving you a phrase to enter into your account, or, for subscribers, by matching the billing email Stripe holds. We respond within the time the law requires (generally one month, or 45 days for California residents).
If you are in the EEA, the UK or Switzerland, you also have the right to restrict or object to processing based on our legitimate interests, to receive your data in a portable format, and to complain to your local data-protection authority.
If you are in California or another US state with a privacy law, you may have the right to know, access, correct and delete your personal information, to receive a portable copy, and not to be discriminated against for exercising your rights. You may also have the right to opt out of the sale or sharing of personal information and to limit the use of sensitive personal information; we do not sell or share personal information, and we use account credentials only to provide the Service. You can use an authorized agent to make a request on your behalf, and we may ask them to prove their authority. If we decline a request, you can appeal by replying to our response with the word "Appeal," and you may contact your state attorney general if you are unhappy with the outcome.
Categories of personal information we collected in the last 12 months (California):
| Category | Examples | Source | Disclosed to |
|---|---|---|---|
| Identifiers | Email address; account ID or username; the identifier Google gives us for your account; IP address; cookie identifiers (only if you accept advertising measurement) | You; Google if you sign in with it; your browser | Hosting provider; Stripe (email address, if you subscribe); Google (IP address and cookie identifiers, only if you accept advertising measurement) |
| Commercial information | Plan, subscription status, usage and credit, Stripe customer and subscription IDs | You; Stripe | Stripe; hosting provider; Google (only the amount of a first payment, and only if you accept advertising measurement) |
| Internet or network activity | Usage counters, run history and logs; the label of the link you signed up from; pages viewed on our public pages, any ad-click identifier, and whether you then signed up or subscribed (only if you accept advertising measurement) | Our systems; the link you followed; your browser | Hosting provider; Google (only if you accept advertising measurement) |
| Other information you provide | Research topics, the topics you choose to analyse, PDFs you upload for individual studies (we keep the extracted text only) and other content | You | Hosting and AI providers |
| Sensitive personal information | Account log-in credentials (stored as a password hash) | You | Hosting provider |
Do Not Track and Global Privacy Control. We do not track you across websites. We treat a Global Privacy Control signal as a decline of advertising measurement: with it on, we show no notice and load nothing from Google. We do not sell or share personal information.
8. Security
We use measures including encrypted connections (HTTPS), one-way salted hashing of passwords, a signed, HttpOnly, Secure, SameSite=Strict session cookie, and access controls that limit each run to its owner. No system is perfectly secure, so we cannot guarantee absolute security. If a breach affects your personal information we will notify you and regulators as the law requires, in the Service and, for subscribers, by email to the billing address on file.
9. Children
The Service is not directed to anyone under 18 and we do not knowingly collect information from them. If you believe a child has an account, contact us and we will delete it.
10. Cookies and similar technologies
We set one essential cookie to keep you signed in and use a little browser storage for convenience (including your answer to the advertising notice). We do not use analytics cookies. Cookies for advertising measurement are set only by Google's tag, and only if you accept it on our public pages (the tag also runs in the app for up to twenty seconds after a sign-up or a first payment, as Section 1 says). A link label (Section 1) travels in the web address, not in a cookie or in browser storage. If you continue with Google we also set a second essential cookie, for at most ten minutes, that protects that sign-in against forgery. Details are in our Cookie Policy.
11. Information about authors in the literature
The Service processes publicly available bibliographic records, such as article titles, abstracts and author names, from PubMed and PubMed Central. That information is about published research, not about you. We use it only to provide the Service and do not build profiles of authors. If you are an author with a question or request about how your published information appears in the Service, contact us.
12. Changes to this policy
If we make material changes we will give notice in the Service and, where required, ask you to accept the updated Terms and Policies. The effective date above shows the current version.
13. Contact
SynthGap · Sehit Dumenci Street No 10, 99010 Nicosia, Cyprus · alikesen54@gmail.com