Decimal LifeJoin the beta

Privacy Policy

1. Who we are

Decimal Life is operated by Decimal Life Private Limited, a company in India (“Decimal Life”, “we”, “us”). Under India’s Digital Personal Data Protection Act, 2023 (the “DPDP Act”), we are the Data Fiduciary for the personal data described in this policy.

This policy covers the Decimal Life apps for iPhone and Android, and the website and web app at decimallife.com.

Contact us at privacy@decimallife.com for anything in this policy. Our Grievance Officer is listed in section 14.

2. What we collect

2.1 Your account

  • Email address and name, from sign-up or from Google or Apple when you sign in with them.
  • Account identifiers: our internal user ID and the ID of your sign-in account.

Sign-in is handled by our authentication provider, Clerk, using one-time email codes, Sign in with Google or Sign in with Apple. We never see your Google or Apple password.

2.2 What you tell us about yourself

  • Your timezone, taken from your device.
  • Your onboarding answers: your role (for example founder or student), focus areas, priorities, planning style, workdays and working hours, and any office or school commitments.
  • Personal facts you mention to Deci, such as your birth year, height or weight. Deci saves these so it does not need to ask again.

2.3 What you create

Tasks, goals, milestones, habits, day plans, focus sessions, journal entries, notes and captures (including files and Apple Notes you import, and text you send from the iOS Back Tap shortcut or the Android share menu), your conversations with Deci, Startup OS records, and the people you add to Relationships (names, birthdays, anniversaries and when you last spoke).

The people you add to Relationships are entered by you. We never read your phone’s contacts.

2.4 Services you choose to connect

Nothing is connected by default. Each source is connected only after you approve it on that service’s own permission screen.

  • Apple Health (iPhone), Health Connect (Android) or Google Health. We read only the types you allow:
    • activity: steps, distance, calories, floors, workouts, exercise and stand time, VO2 max
    • heart and vitals: heart rate, resting heart rate, heart rate variability, blood oxygen, respiratory rate, blood pressure, body temperature, blood glucose
    • sleep, body measurements (weight, body fat, height), nutrition and water, mindfulness sessions
    We read health data. We do not write anything to Apple Health or Health Connect. On Android, Health Connect may also sync in the background if you allow it.
  • Calendars (Apple Calendar on your phone, Google Calendar, Outlook): event titles, times, location, a shortened description and meeting links, from 90 days back to 60 days ahead. We do not read attendee lists or birthday calendars.
  • Google Tasks: task titles, due dates and status.
  • Email (Gmail, Outlook):
    • for every synced thread: sender name and address, subject, date and a short preview of up to 220 characters
    • the full message, but only when you open it in Decimal Life
    • the address of the mailbox you connected
    Gmail access is read-only.
  • GitHub: repositories, pull requests, commit statistics and issues. Linear: issues and projects.

2.5 What we work out from your data

To answer with context, Decimal Life builds a personal knowledge graph from the data above. This includes summaries, links between items, and numerical “embeddings” used for search. It also produces:

  • scores such as the Life Score, Health Score and streaks
  • patterns in how you plan and work, for example which days tend to run long
  • inbox triage labels, the next steps it has learned, and draft replies

This is a profile of you, built to personalise the app for you. It is used only to run the app for you, and it is deleted with the data it came from.

2.6 Device and technical data

  • Push notifications: a push token for your device, the platform and the app version.
  • Approximate location, only if you allow it and only while the app is open. It is rounded to about 1 km before it leaves your phone, and is used to show local weather. We do not use precise or background location.
  • Security log: the IP address and device/browser details used for security-relevant actions on your account, such as sign-in, connecting a source or deleting data.
  • Crash and performance reports, sent to Sentry. They are not linked to your user ID, and request bodies, cookies and headers are removed before sending.
  • Server logs that record requests and errors.

2.7 On our website

  • Analytics: we run our own copy of Umami, a cookie-free analytics tool, on our own servers. It records the pages you visit, the referring site, your browser, device type and country (worked out from your IP address). No third party receives this.
  • Waitlist and closed testing: if you join the waitlist or apply to test, we store your email address, whether you signed up as a user or an investor, and where you came from. If you apply to test, we also store your role and the type of phone you use. We email you to confirm, and if you are invited to test, again with the link to install the app. These emails are sent through Resend. If you test on Android, we add your email address to our testers list on Google Play, which is how Google Play lets you install the test version.
  • Fonts: pages load fonts from Google Fonts, so your browser connects to Google, which receives your IP address.
  • Cookies: the website sets no advertising or tracking cookies. The web app uses cookies that are strictly needed to keep you signed in. Your colour-theme choice is saved only in your browser.

2.8 What we do not collect

We do not collect your phone’s contacts, precise or background location, payment card details, microphone audio, photos, or browsing history. We do not use advertising or attribution tools, and we do not track you across other companies’ apps or websites. The finance and voice features you may see referred to in the app are switched off during the beta, and no data is collected for them.

3. How we use your data

We use your data to:

  • run your account and keep you signed in
  • sync the sources you connect, and build and maintain your personal knowledge graph
  • plan your day, produce your brief, scores and insights, triage your inbox and let Deci answer with your context
  • send reminders and notifications you have turned on
  • keep the service secure, prevent abuse, and find and fix faults
  • understand, at an aggregate level, how people use our website
  • meet our legal obligations

We do not use your data for advertising, we do not sell it, and we do not share it with data brokers.

Our legal basis. We process your personal data on the basis of your consent: you give it when you create an account and each time you connect a source or grant a permission. You can withdraw consent at any time by disconnecting a source, turning off a permission, or deleting your account (section 10). Withdrawing consent does not affect processing that already happened. A few uses, such as keeping security logs and meeting legal obligations, rely on the legitimate uses the DPDP Act allows.

4. How AI is used, and what the AI providers see

Deci’s replies, and several features that run without you asking, are produced by large language models (LLMs) run by outside providers. These features are:

  • the daily brief
  • inbox triage and reply drafts
  • sorting your notes
  • learning from your messages
  • keeping your profile short enough to send

To produce an answer, we send the relevant parts of your data to the provider over an encrypted connection. Depending on what you have connected and what you ask, this can include:

  • health and fitness data
  • email subjects, previews and message content
  • calendar events, tasks and notes
  • your Deci conversation

The providers we use today:

  • Sarvam AI (India): our main provider for Deci and the other AI features.
  • OpenAI (United States): used for the same features when Sarvam is unavailable. OpenAI also creates the search embeddings for your notes, memories, graph items and email previews, and runs a safety check on messages to Deci and on its replies, to spot self-harm and harmful content. OpenAI says it does not train on or keep what is sent for that check. For other requests, OpenAI may keep them for up to 30 days to detect abuse, then deletes them. Sarvam AI keeps requests only as its API terms allow.

We will update this list before we add any other provider.

What the providers may do with it. The providers process your data only to return a result to us, under their API terms. Neither may use it to train their models.

Our own commitments:

  • We send only what a feature needs.
  • When the inbox-learning feature sends email subjects and previews, it first removes personal details such as addresses and phone numbers.
  • We do not use your content to train AI models, either our own or anyone else’s.
  • People at Decimal Life do not read your content, except in the cases listed in section 6.

Your controls. In Settings › Privacy you can turn sharing with Deci off for each area: health, email, calendar, work, journal, relationships. When an area is off, its data is left out of what we send to the AI providers. You can also hide individual notes from Deci.

AI output can be wrong. See our Terms of Service.

5. Health data

Health data needs extra care, so these commitments apply on top of the rest of this policy:

  • We use health data only to provide the health features you see in the app and to let Deci answer with your health context. This includes sending it to the AI providers in section 4, unless you turn health off in Settings › Privacy.
  • We never use health data for advertising, marketing or data mining for those purposes, and we never sell it or share it with data brokers, advertisers, insurers or employers.
  • We never store health data in iCloud.
  • Data from Apple HealthKit is used in line with Apple’s App Review Guidelines (5.1.3), and data from Health Connect in line with Google’s Health Connect permissions policy.
  • We read only the health types you approve, and only to show them back to you, calculate your Health Score and insights, and plan around them.
  • Decimal Life is not a medical device and does not diagnose or treat anything. See our Terms of Service.

6. Google user data

Decimal Life’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

This covers data from Google Calendar, Google Tasks, Gmail and Google Health. Data we receive through Google APIs is:

  • used only to provide or improve the features you can see in Decimal Life: planning, the daily brief, inbox triage and replies, health insights and Deci’s answers
  • transferred to others only to provide those features (including to the AI providers in section 4, which process it only to return a result to us), to comply with the law, or as part of a merger, acquisition or sale of assets, with notice to you
  • never used for advertising, including retargeting, personalised or interest-based ads
  • never sold, and never used to decide creditworthiness or for lending
  • never used to develop, improve or train generalised AI or machine-learning models
  • never read by a person, unless:
    • you ask us to look at specific data
    • it is needed for security, such as investigating abuse
    • the law requires it
    • the data has been aggregated and anonymised for internal operations

A note on our Google sign-up count. Until Google finishes verifying our app, Google limits how many people can connect it. To stay within that limit, we keep a record of which Google accounts have connected. The record holds keyed hashes, not your email address, and is kept even after you delete your account, so that we can count accounts correctly.

7. Who we share data with

We share personal data only with the service providers that run Decimal Life for us, only as much as each needs, and only under contracts that limit them to providing their service:

Services you connect (Apple, Google, Microsoft, GitHub, Linear) are the source of the data. We read from them with your permission.

People you choose to share with. If you create a share card or an availability link, anyone with the link can see what it shows. An availability link shows your name, the meeting title and your free times. Links can be revoked, and availability links expire after 14 days by default.

Push notifications can include short text, such as a task title, and pass through Expo and Apple or Google to reach your phone. They may appear on your lock screen. You can change this in your phone’s notification settings.

Legal and business reasons. We may disclose data where the law requires it, to protect people’s safety or our rights, or to a successor if Decimal Life is merged or sold. In a merger or sale, this policy will continue to apply to your data, or we will tell you before it changes.

8. Where your data is stored and transferred

Your account data, content and connected-source data are stored in India, in Amazon Web Services’ Asia Pacific (Mumbai) region.

Some of the providers in section 7 process data outside India, in the United States and the European Union. We transfer data to them only to provide the service, and only to countries the Government of India has not restricted under the DPDP Act.

9. How long we keep data

10. Your controls and rights

In the app (Trust Center):

  • Export a copy of your main data as a file. For a complete copy, email privacy@decimallife.com.
  • Delete an area, such as health, email or memory, without closing your account.
  • Disconnect a source to stop collecting from it.
    • When you disconnect Google Calendar, Google Tasks or Google Health, we also ask Google to cancel our access.
    • For Gmail, Outlook, GitHub and Linear, also remove Decimal Life in that account’s own security settings.
  • Turn off sharing with Deci for any area (section 4).
  • Delete your account in the mobile app under Profile › Account. This deletes your data from our live systems and deletes your sign-in account. It also asks Google, GitHub and Linear to cancel our access. Microsoft and Apple don’t let us do that, so if you connected Outlook or an Apple calendar, also remove Decimal Life in that account’s settings. A GitHub token you created yourself is yours to delete in GitHub. If you can’t use the app, email privacy@decimallife.com from your account’s email address.

Your rights under the DPDP Act. You have the right to:

  • get a summary of the personal data we process and of who we have shared it with
  • correct, complete or update your data
  • have your data erased
  • withdraw your consent at any time
  • have your grievances dealt with
  • nominate someone to exercise these rights for you if you die or become unable to

To use any of these rights, write to privacy@decimallife.com. If you are not satisfied with our response, you can complain to the Data Protection Board of India once you have used our grievance process (section 14).

If you live outside India, you may have similar rights under your local law, such as rights to access, correct, delete or move your data, or to object to processing. Write to us and we will help.

11. Security

  • All traffic is encrypted in transit (HTTPS/TLS).
  • Our database is encrypted at rest.
  • Tokens for the services you connect are encrypted again inside our application (AES-256-GCM), and the keys are held separately in AWS.
  • On your phone, sign-in tokens are kept in the operating system’s secure keychain.
  • Access to production systems is restricted to the people who need it, and is logged.

No system is perfectly secure. If a breach affects your personal data, we will tell you and the Data Protection Board of India as the DPDP Act requires.

12. Age requirement

Decimal Life is only for people aged 18 or over. We do not knowingly collect personal data from anyone under 18. If you believe someone under 18 has given us data, email privacy@decimallife.com and we will delete it.

13. Changes to this policy

We will update this page when the product or our practices change, and revise the date at the top. If a change materially affects how we handle your data, we will tell you in the app or by email before it takes effect, and ask for your consent again where the law requires it.

14. Contact and grievances

We will acknowledge your grievance within 7 days and aim to resolve it within 30 days.