Privacy Policy

Your genome file never leaves your computer. Nothing about this policy changes that. An account, where one exists at all, is only ever for a paid subscription, a purchased snapshot, or the referral program — never for anything to do with your genetic data.

The MyGeneLog™ desktop app

MyGeneLog™ is free — no account, no license key, nothing to buy. The app collects no telemetry and never uploads your genome file or your analysis results anywhere; parsing happens entirely in memory, on your own machine.

The app makes exactly two outbound network calls, neither carrying any user- or genome-identifying data:

• An optional, anonymous version check against the public GitHub install repository.
• A fetch of the public reference-data feed from this site (mygenelog.com/reference-data.json), which lets the app recognize newly-added variants without an app update. This happens automatically at most once a day, or on demand from About → "Check for updates." It's a one-way, unauthenticated request — nothing about you, your genome, or your results is sent.

This website (mygenelog.com)

This site is free to read and collects no payment for that — there is no purchase flow to read a page. Depending on how you use the site, we collect:

• Basic site analytics, on every visit. The page path you visited, referrer, UTM campaign parameters if present, source/medium, approximate device and browser type, and your IP address. The IP address is used to derive an approximate location (country, and usually region/city) and is not otherwise looked up or shared; it is not linked to a genome file or analysis result, because neither of those ever reaches this site. We also record whether a request looks like it came from a known automated crawler (including named AI systems), separately from human visits, so the figures on /data can honestly say which is which.
• Account details, only if you create one. An email address and a username are required; a password is stored as a salted hash, never in plain text, unless you sign in with Google instead, in which case we receive your Google account's email, name, and a stable account identifier from Google and never see a password at all. At signup we also ask, once, who is reading — a short, optional-to-skip-by-choosing-"something else" category (for example: genome-file owner, student, clinician) used only to understand our own readership, never sold or used to target you individually.
• Anything you submit through a contact/support form — your email address and message, so we can reply.
• Payments, subscriptions, and donations. Stripe collects your name, email, and payment details to process a donation, a subscription, or a snapshot purchase. We do not see or store your card number; we store that a payment happened, its amount, and which product or plan it was for, so we can honor it. Stripe's own privacy policy governs the payment data it holds.
• The referral program, if you use it. A referral link or code tied to your account, and a count of how many people used it, so a free pass can be credited correctly.
• A session cookie, if you sign in. It identifies your logged-in session to our server and nothing else; it is not a third-party tracking or advertising cookie, and we do not run third-party ad-network tracking pixels on this site.

What we don't do

We don't sell your data. We don't run ad-network tracking pixels. We don't build an advertising profile on you. The account system exists to run a subscription, a snapshot purchase, and the referral program — not to track what you read; the analytics above are collected the same way whether or not you are signed in.

How long we keep it

Analytics rows (page path, referrer, approximate location, crawler/human flag) are kept indefinitely in aggregate form to show the growth and readership figures on /data, but are not actively used to build a profile of any one visitor. Account data is kept for as long as the account exists, plus whatever a paid product's own terms require (for example, a completed purchase's billing record, which we keep for tax and accounting purposes even after an account is closed). Support messages are kept as long as needed to resolve the issue and for a reasonable period after, for our own record.

Your choices & rights

You can ask us, at any time, what personal data we hold about you, to correct it, or to delete your account and associated personal data (billing records we are legally required to retain are the one exception). Send that request the same way as any other question — see Contact, below — from the email address on the account, so we can verify it is really you asking. We aim to respond within a reasonable time and will tell you directly if some part of a request cannot be completed and why.

Children

This site and app are not directed at children under 13, and we do not knowingly collect personal information from a child under 13. If you believe a child has created an account or submitted information to us, contact us and we will delete it.

Where data is processed

This service is operated from the United States, and data described on this page is processed and stored there. If you are visiting from outside the United States, you are sending information to a country whose privacy laws may differ from your own.

Changes to this policy

We may update this policy as the site changes; the current version is always at this address, with the Effective date above showing the latest revision.

Contact

Questions about this policy, or a request to access, correct, or delete your data, go to the maintainer via GitHub Issues.