Privacy Policy

1. Who we are

Diatrack is operated by Jagdeep Singh Kalsi , 435, White City, Sector 114, Mohali. 140307 (“Diatrack”, “we”, “us”). We are the data controller for the information described in this policy. You can reach us at info@diatrack.app .

2. What Diatrack does

Diatrack lets you keep a diabetes logbook for one or more people (“profiles”): blood glucose readings, insulin doses, meals and physical activity, with notes. You can share a profile with other people you trust (“helpers”) and, if you choose, connect an AI assistant that can read and add entries on your behalf. Diatrack is a record-keeping tool. It is not a medical device and does not give medical advice.

3. Information we collect

3.1 Your account

When you sign in with Google or GitHub we receive your name and email address from that provider. We also store your timezone and display preferences (glucose unit, time format). If password sign-in is enabled for your account we store a hashed password and, when you turn them on, two-factor authentication secrets and passkeys. We record when you accepted these terms and gave consent, and which version.

3.2 Profiles — the people you track

For each person you add: a name, and optionally an email address, phone number and date of birth. These are used to label the profile, to show ages, and to match the same person across accounts when you share. Most profiles are children of the account holder.

3.3 Health information

Everything you log in a profile: blood glucose readings and when they were taken; insulin doses and their type (bolus or basal); meals, including the foods, portions and our nutrition estimate; physical activity with its duration and intensity; and any free-text notes. We also record which account logged each entry so shared profiles can show who added what.

This is health data — “special category” data under the GDPR and equivalent laws. We only collect it because you enter it, and only with your explicit consent (section 4).

3.4 Foods and combos

Foods and meal combinations you create: names, brand, ingredients, nutrition values and a 1–10 healthiness rating. If you use “AI fill”, the food name you typed is sent to Google’s Gemini API to suggest nutrition values (section 8). Nothing else about you or the profile is sent.

3.5 Sharing

When you invite a helper we store the email address you entered, the role you gave them (viewer or editor), and when the invitation was accepted or expired.

3.6 AI assistant tokens

When you create an access token for an AI assistant we store its name, a hashed form of the token, what it is allowed to do, when it expires and when it was last used. We never store the token itself.

3.7 Activity log

For every profile we keep a log of who viewed, added, changed, exported or shared what, when, from which IP address and device, and whether it was done in the app or through an AI assistant. The owner of a profile can see this log. We keep it for 12 months.

3.8 Technical information

Like every web service, our servers record IP addresses, browser or app version, the pages requested and timestamps, and our error-monitoring tool records failures and response times so we can keep Diatrack working. Session cookies keep you signed in (section 13).

3.9 What we do not collect

No advertising identifiers, no analytics or tracking pixels, no location, no contacts, no payment details, and no automatic readings from meters, pumps or continuous glucose monitors — every entry is typed in by a person or an assistant you connected.

4. Why we use it and our legal grounds

• To provide Diatrack to you — storing and showing your logbook, reports and suggestions, syncing between the web and the mobile app, and running sharing and assistant features you set up. Legal ground: performance of our contract with you (GDPR Art. 6(1)(b)).
• To store health information — legal ground: your explicit consent (Art. 9(2)(a)), which you give when you create your account and can withdraw at any time by deleting the profile or your account, or by contacting us. Withdrawing consent does not affect processing that already took place.
• To keep Diatrack secure — the activity log, rate limiting, abuse detection and error monitoring. Legal ground: our legitimate interest in protecting the service and your data (Art. 6(1)(f)), and where health data is involved, the same explicit consent.
• To meet legal obligations — such as responding to lawful requests or to your rights requests (Art. 6(1)(c)).

We do not use your information for advertising, for profiling, for automated decisions that affect you, or to train machine-learning models. We never sell it.

5. Children and people you add

Diatrack accounts are for adults. You must be at least 18 (or the age of majority where you live) to create one. Profiles for children are created and controlled by their parent or legal guardian, who gives consent on the child’s behalf and is responsible for who they share the profile with. When you add another adult, you confirm that they agree to you keeping their logbook.

A person whose data is in a profile — including a child who is old enough to ask — can exercise the rights in section 12 through the account holder or by contacting us; we will verify the request with the account holder.

If you live in India, the Digital Personal Data Protection Act treats the parent’s consent as the verifiable parental consent it requires for a child’s data. We do not track children’s behaviour or show them advertising.

6. Sharing with helpers

Sharing only happens when the owner of a profile invites someone by email. The invitation must be accepted by that person after they sign in, and expires after 30 days if it is not. A viewer can see everything in the profile; an editor can also add, change and delete entries, foods and combos. Helpers cannot share the profile onward, cannot see your other profiles, and cannot see your account settings. The owner can change a helper’s role or remove them at any time, and can see what they did in the activity log.

Helpers are bound by the same Terms of Service and must use the profile only for the purpose you shared it. If you are a helper, the owner controls the profile and its data; leaving the profile removes your access but not the entries you added, which stay in the owner’s logbook without your name.

7. AI assistants you connect

You can create an access token on the Account page and give it to an AI assistant or tool of your choice (for example Claude, Cursor or another MCP-compatible client). From then on that assistant can read and add entries in the profiles you allowed, exactly as you could. The provider of that assistant is your choice, not our service provider: whatever the assistant reads from Diatrack is processed under that provider’s own terms and privacy policy, and we cannot see or control what it does with it. Do not connect an assistant you would not trust with a paper copy of your logbook.

Tokens expire after 90 days, can be limited to one profile and to read-only access, can be revoked at any time, and everything done through one is recorded in the activity log.

8. Service providers

We use a small number of companies to run Diatrack. Each receives only what it needs, under a contract that restricts it to acting on our instructions.

We do not share your information with anyone else, except where the law requires us to, or to protect the rights and safety of a person in an emergency. We will tell you about any new provider by updating this policy.

9. Where your data is stored

Our servers, database and error-monitoring data are in the European Union (Frankfurt, Germany). We run Diatrack from India. Sign-in providers and the Gemini API are operated from the United States. When your data leaves the country you live in — for example the EU — we rely on the safeguards the law there recognises, such as the European Commission’s Standard Contractual Clauses or, for providers in the United States, the EU–US Data Privacy Framework. The mobile app also keeps a copy of your logbook on your phone so it works offline; that copy is protected by your device’s lock screen and file-system encryption and is removed when you sign out or uninstall the app.

10. How we protect it

• Everything travels over TLS. Our hosting and database providers encrypt data at rest.
• Names, email addresses, phone numbers, dates of birth and free-text notes are additionally encrypted by Diatrack itself before they reach the database, so a raw copy of the database cannot tell whose health record is whose.
• Only the account holder and the helpers they invited can open a profile; every access path — the app, the mobile app and AI assistants — is checked against the same rules.
• Sign-in goes through Google or GitHub, with two-factor authentication and passkeys where password sign-in is enabled. Assistant tokens expire and can be revoked.
• We keep an activity log, limit request rates, monitor our dependencies for known vulnerabilities and publish a security contact at /.well-known/security.txt.
• If a breach ever affects your data we will notify the supervisory authority within 72 hours and tell you without undue delay, explaining what happened and what we are doing about it.

No system is perfectly secure. Keep your Google or GitHub account protected, and only share profiles and tokens with people and tools you trust.

11. How long we keep it

• Your logbook — for as long as your account exists. Delete a profile and its entries are removed immediately; delete your account and every profile you own goes with it. Entries you logged in someone else’s profile stay in their logbook, without your name.
• Backups — deleted data disappears from backups within 7 days.
• Activity log — 12 months. Server logs — 30 days. Sessions — until you sign out, or after 7 days of inactivity.
• Invitations — an unaccepted invitation and the email address in it are deleted after 30 days.
• AI food cache — food names and the nutrition answer, with no link to any account, for 100 days.
• Consent records — kept for as long as required to demonstrate consent, and 3 years after your account is deleted.

12. Your rights and controls

Most of these you can do yourself in the app; the rest, by contacting us. We answer within 30 days and never charge for it.

• See and download everything about a profile — Profiles → ⋯ → Download data gives you JSON and CSV files.
• Correct anything by editing it.
• Delete a single entry, a whole profile, or your account — Account → Delete account.
• Withdraw consent for health data at any time by deleting the profile or account, or by writing to us.
• Object to or restrict processing, and complain to a data protection authority — ours is the Data Protection Board of India ; you can also complain to the authority where you live (in the EU, your national data protection authority).
• If you are in India, you may also nominate a person to exercise these rights on your behalf and raise a grievance with us at the contact below.
• If you are in a US state with a consumer health data law (for example Washington), you have the right to know who has received your health data, to withdraw consent, and to have it deleted; we never sell consumer health data and never share it except as you direct.

13. Cookies

Diatrack uses only strictly necessary cookies: a session cookie that keeps you signed in and a CSRF token that protects forms. Your light/dark theme preference is kept in your browser’s local storage. There are no advertising, analytics or third-party cookies, which is why you do not see a cookie banner.

14. Changes to this policy

When we change this policy in a way that matters — a new provider, a new use of data — we will ask you to read and accept the new version the next time you open Diatrack, and the version number at the top will change. Minor clarifications are posted here without a prompt. Earlier versions are available on request.

15. Contact

Jagdeep Singh Kalsi
435, White City, Sector 114, Mohali. 140307
info@diatrack.app

We have not appointed a Data Protection Officer because of the size of the service; the contact above handles all privacy questions.