Privacy Policy

1. Who we are

This Privacy Policy describes how Saaniya Software LLC processes personal information in connection with Saarthee CoPlanner by Saaniya Software LLC (“Service”). The operator may publish additional entity details on saaniya-software.com.

2. Information we collect

2.1 Account and authentication

If you create an account or sign in, we may collect identifiers such as name, email address, profile identifiers from an identity provider, session tokens, and security-related logs (for example sign-in time and IP address) to operate authentication and prevent abuse.

OAuth provider passwords (Google, Microsoft, and Notion)

The Service does not ask you to enter your Google, Microsoft, or Notion account password into Saarthee, and we do not receive or store those provider passwords. When you choose Google, Microsoft, or Notion sign-in, you authenticate with that provider; we receive authorization results they issue (such as tokens and profile identifiers described in their documentation), not your password for their service.

Linked sign-in (Google, Microsoft, or Notion)

If you already have an account with an email and password, and you later choose Continue with Google, Continue with Microsoft, or Continue with Notion using the same email address, we may treat that as one account: we attach that sign-in to your existing profile instead of creating a second user. That way you can use either method to access the same data. We rely on those providers to have verified the email on their side before we link it. You can see which methods are on your account under Settings (Sign-in methods). If you believe someone linked the wrong provider to your account, contact us via Support.

2.2 Product usage and diagnostics

We may collect technical data such as app version, device type, error reports, and aggregated usage metrics to improve reliability and performance.

2.3 Content and integration data

When you connect third-party services (for example mail, calendar, cloud drives, or Notion), we process information needed to provide the features you enable. This may include message metadata, event details, file listings, page references, and similar data, according to the scopes you approve with each provider.

2.3a Google user data

If you use Continue with Google, we receive your Google account email, name, and profile identifier (OpenID). We do not receive your Google password.

If you later choose Settings → Add Google account, we request only:

• Calendar (read-only): event title, start and end time, location, and attendees, so we can show your events on Today and Calendar. We do not create, edit, or delete events in Google Calendar.
• Drive file (Google Picker): names and identifiers of folders and files you explicitly pick. We do not request your entire Drive. We do not use Drive as a content-delivery network. We do not bulk-delete files in your Google account from CoPlanner; disconnecting removes our stored folder list, not your Drive originals.

We do not request Gmail OAuth. Gmail in CoPlanner, if you enable it, uses a Google app password you create, not Gmail API scopes.

Use: Google user data is used only to provide and improve the user-facing features you turned on (sign-in, calendar display, and the Drive folders you pick). We do not use it for advertising, credit decisions, or sale to data brokers.

Sharing: We do not sell Google user data. We do not share it with other CoPlanner users. Hosting and database vendors (for example our cloud host and Postgres provider) process it only to run the Service.

AI and Google user data: If you use the in-app assistant or search and ask about your schedule or files, we may send snippets of already-synced metadata (for example event title and time, or a Drive file name you indexed) to an inference API so the assistant can answer you. That is a user-facing feature, not model training. Chat and related calls use, in this order as configured on the server: Google Cloud Vertex AI (Gemini), then the Google Gemini API, then OpenAI, then Anthropic. Optional semantic ranking may use Vercel AI Gateway embeddings (OpenAI embedding models). We select paid / API tiers and do not opt in to provider training on API payloads. We do not operate self-hosted copies of those models. You can turn AI off in Settings → Trust & data.

Protection: OAuth tokens stay on the server. Data is stored in your account in our database with access controls. You can Remove the Google connection in Settings or revoke access at Google Account permissions.

Retention and deletion: We keep connected Google calendar and file metadata while the connection is active and your account exists. After you Remove Google or delete your account, we delete that stored Google data from active systems, subject to short-lived backups and legal holds.

Google Limited Use: The use of raw or derived user data received from Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements. We do not use Workspace API data to develop, improve, or train generalized AI or machine-learning models, and we do not transfer that data to third parties that train their models on it.

2.4 Optional local features

If you use optional local automation, related commands and outcomes may be processed on your device and, where you enable cloud features, transmitted to the Service only as needed for the feature you chose.

3. How we use information

We use personal information to:

• Provide, secure, and improve the Service;
• Authenticate users and prevent fraud;
• Operate integrations you connect and sync data you request;
• Provide AI-assisted features where enabled;
• Communicate about the Service, security, and policy updates;
• Comply with law and enforce our terms.

4. Legal bases (EEA/UK users)

Where GDPR or UK GDPR applies, we rely on one or more of: contract (to provide the Service), legitimate interests (security, product improvement, and fraud prevention, balanced against your rights), consent (where required for optional analytics or marketing), and legal obligation.

5. Sharing and subprocessors

We may share information with vendors that help us run the Service (for example hosting, database, email delivery, error monitoring, and AI inference providers). Those vendors are bound by contractual obligations to protect data and process it only on our instructions. A representative list of categories appears on the Technology page and may be expanded over time.

We may disclose information if required by law, legal process, or to protect the rights, safety, and security of users, Saaniya Software LLC, or the public.

6. International transfers

The Service may be hosted in the United States or other regions. If you are in the EEA, UK, or Switzerland, we will use appropriate safeguards (such as Standard Contractual Clauses) where required for transfers.

7. Retention

We retain information as long as needed to provide the Service, comply with law, resolve disputes, and enforce agreements. You may request deletion of your account subject to lawful exceptions (for example security logs or backups for a limited period).

In-app assistant chat: when you use the Saarthee assistant, message text is stored in our database and tied to your account so history can sync across devices. We prune assistant chat messages after a retention window (default 90 days, configurable by operators). You can clear the current product-help conversation from the assistant panel at any time. Cleared or expired chat content is removed from active storage subject to ordinary backup cycles.

8. Security

We use administrative, technical, and organizational measures designed to protect personal information. No method of transmission or storage is completely secure; you should use strong passwords and protect your devices.

9. Your rights and choices

Depending on your location, you may have rights to access, correct, delete, export, or restrict processing of your personal information, and to object to certain processing. You may also have the right to lodge a complaint with a supervisory authority. To exercise rights, contact us via Support.

You can disconnect integrations in product settings where available. Browser or device controls may limit cookies or local storage where applicable.

We honor Global Privacy Control (GPC) when your browser sends the GPC signal: we treat it as essential-only consent and do not load optional analytics. You can also choose Essential only or Accept analytics via the cookie banner. See the Cookie Notice for categories and storage details.

10. Children

The Service is not directed to children under 16 (or the age required in your jurisdiction). We do not knowingly collect personal information from children. If you believe we have, contact us and we will take appropriate steps.

11. Changes to this policy

We may update this Privacy Policy from time to time. We will post the updated version and revise the effective date. Where required, we will provide additional notice.

12. Contact

For privacy requests, email saaniya@saaniya-software.com, use the channels on saaniya-software.com, or the Support page.