Your Data and Privacy

Your privacy and trust are fundamental to CelestiOS.

We designed the system to collect only the information necessary to generate helpful insights for your day.

What Data We Use

Celesti may use the following information to generate daily guidance:

calendar events (time and schedule information)
sleep or energy signals you provide
priorities you choose to share
health data from connected devices (Oura, Fitbit, Garmin, Apple Health)

This data helps celesti understand your daily context.

What We Do With Your Data

Your data is used only to generate insights and recommendations for you.

Celesti does not sell or share your personal data with third parties.

Your information is not used for advertising.

Security

We take security seriously.

All user data is encrypted at rest and in transit using industry-standard encryption protocols (AES-256 and TLS 1.2+).

Access to systems is restricted and monitored to protect your information.

We do not use your emails, calendar data, or any personal information to train AI or machine learning models. Your data is used solely to generate insights for you and is never fed into model training pipelines.

Tenant data is logically isolated — your information is kept separate from other users' data and is never commingled or accessible across accounts.

Google Calendar API Usage

Celesti uses the Google Calendar API to provide personalized scheduling insights and schedule optimization.

When you connect your Google Calendar, celesti accesses the following information:

Event titles, start times, and end times
Event duration and availability windows
Organizer status (whether you organized the meeting)

We use the following Google Calendar API scopes:

https://www.googleapis.com/auth/calendar.readonly — to read your calendar events
https://www.googleapis.com/auth/calendar.events — to create focus blocks and reschedule meetings

Celesti's use and transfer of information received from Google APIs adheres to Google API Services User Data Policy, including the Limited Use requirements.

Calendar data is used solely to:

Generate daily schedule insights and recommendations
Identify available time blocks for focused work
Create protected "Focus Block" events when burnout risk is detected
Reschedule low-priority meetings to less congested time slots

All calendar writes require explicit user action. You must click "Fix my day" to trigger any changes. No automatic or background modifications are ever made without your consent.

We do not access event descriptions, attendee lists, attachments, or video conference links.

You can disconnect your calendar at any time from your settings.

Gmail API Usage

Celesti uses the Gmail API to detect email overload as part of our burnout prevention algorithm.

When you connect your Gmail account, celesti accesses the following metadata only:

Sender name and email address
Email subject line
Timestamp (when the email was received)
Gmail importance flag (high, normal, or low)
Unread status and count

We use the Gmail API scope: https://www.googleapis.com/auth/gmail.readonly

Celesti's use and transfer of information received from Google APIs adheres to Google API Services User Data Policy, including the Limited Use requirements.

Gmail metadata is used solely to:

Count unread important emails to measure communication load
Identify emails from leadership (CEO, VP, Director) for priority awareness
Feed email volume into our burnout detection algorithm as a cognitive load signal
Display email insights on your dashboard (e.g., "50 important emails unread")

We do NOT access:

Email body content
Email attachments
Contact lists or address book
Drafts, sent emails, or trash

We never send, modify, archive, or delete any emails. Gmail metadata is used for real-time analysis only and is recalculated on each check-in. No email content is permanently stored.

Gmail integration is entirely optional. All other CelestiOS features work without it.

You can disconnect Gmail at any time from your integrations settings. When disconnected, all stored Gmail tokens and connection data are immediately deleted.

Health Data API Usage

Celesti integrates with health and fitness devices to provide personalized energy and readiness insights.

Connecting your health devices is optional. When you connect a supported device, celesti accesses the following information:

Sleep data: Total sleep time, sleep quality score, sleep stages (deep, REM, light)
Readiness/Recovery: Daily readiness score, recovery metrics, body battery
Heart rate data: Resting heart rate, heart rate variability (HRV)
Activity data: Step count, active minutes, workout sessions

Supported health platforms:

Oura Ring: Via Oura Cloud API (read-only access to daily sleep, readiness, activity, and heart rate data)
Fitbit: Via Fitbit Web API (read-only access to sleep, activity, and heart rate data)
Garmin: Via Garmin Connect API (read-only access to sleep, wellness, and activity data)
Apple Health: Via HealthKit on iOS (read-only access to health and fitness data)

Health data is used solely to:

Auto-fill your daily energy level based on sleep quality and readiness scores
Provide personalized recommendations for work intensity and task scheduling
Identify patterns between your health metrics and productivity
Suggest recovery or rest when your body shows signs of fatigue

Celesti's use of health data adheres to each provider's API terms and data policies. We request only the minimum data necessary to provide personalized insights.

Important: Health data from connected devices is not verified or validated by celesti. Insights generated from this data are for informational purposes only and should not be used for medical diagnosis or treatment decisions.

You can disconnect any health device at any time from your integrations settings. When disconnected, all health data from that source is immediately deleted from our systems.

Jira Integration

Celesti integrates with Atlassian Jira to provide ticket-aware daily planning and workload insights.

When you connect your Jira account, celesti accesses the following information via the Atlassian Cloud REST API:

Assigned issues: Ticket keys, summaries, priority levels, status, and time estimates for issues assigned to you in active sprints
Sprint information: Active sprint name, end date, and days remaining
Completed work: Issues you moved to "Done" today for plan-vs-reality tracking
User profile: Your Jira account identifier for issue lookup (read-only)

Jira data is used solely to:

Include your ticket workload in morning schedule recommendations
Detect potential overload when ticket hours exceed available calendar time
Provide evening plan-vs-reality reviews comparing recommended vs completed tickets
Generate AI-powered insights that reference your actual work items

Celesti uses OAuth 2.0 (3LO) for Jira authentication with the following scopes: read:jira-work and read:jira-user. We request read-only access and never modify your Jira data.

You can disconnect Jira at any time from your integrations settings. When disconnected, all stored Jira tokens and connection data are immediately deleted.

OrangeTheory Fitness Integration

Celesti integrates with OrangeTheory Fitness to incorporate your workout data into daily energy and scheduling insights.

When you connect your OrangeTheory account, celesti accesses the following information:

Booked classes: Upcoming OTF class times and locations
Workout performance: Splat points, calories burned, heart rate zones, and active minutes
Session history: Recent workout sessions for fatigue pattern detection

OrangeTheory data is used solely to:

Protect booked OTF classes from being moved during calendar optimization
Factor workout intensity into energy and burnout detection (e.g., adjusting break recommendations after intense sessions)
Provide post-workout recovery suggestions in your daily schedule

You can disconnect OrangeTheory at any time from your integrations settings. When disconnected, all stored OTF data is immediately deleted.

Data Retention

We retain your data only as long as necessary to provide our services.

Data retention policies:

Calendar events: Stored temporarily and refreshed daily; historical data kept for up to 90 days for insights
Health data: Daily aggregated metrics kept for up to 90 days for trend analysis; deleted immediately upon device disconnection
Check-in data: Retained for the duration of your account to provide personalized recommendations
Account information: Deleted within 30 days of account deletion
Jira data: OAuth tokens and connection metadata deleted immediately upon disconnection; ticket data is fetched live and not permanently stored
OrangeTheory data: Workout and class data deleted immediately upon disconnection
OAuth tokens: Revoked immediately upon disconnection

Control

You remain in control of your data.

You can:

Disconnect calendar and health device integrations at any time
Delete your account and all associated data
Export your data in standard formats
Revoke access to Google Calendar from your Google Account settings
Revoke access to health devices from their respective platforms (Oura, Fitbit, Garmin, Apple Health)
Revoke Jira access from your Atlassian account settings
Disconnect OrangeTheory from your integrations page

at any time.

Transparency & Contact

Celesti is designed to be transparent about how it uses your information.

If you have questions about privacy, data usage, or API access (Google, Atlassian Jira, Oura, Fitbit, Garmin, Apple Health, OrangeTheory), please contact us:

Email: support@celesti.life
Feedback form: Submit feedback

We're committed to protecting your privacy and will respond to inquiries within 48 hours.

Your data is protected. Your trust is earned.