Privacy Policy

Effective Date: September 13, 2026

Samvise is operated by Inference Labs LLC, a Washington limited liability company located in Seattle, Washington, United States ("Samvise", "we", "us", or "our"). Inference Labs LLC is the data controller responsible for your personal information under this Privacy Policy.

At Samvise, we take your privacy seriously. This Privacy Policy explains how we collect, use, and protect your information when you use our intelligent task scheduling service.

1. Information We Collect#

1.1 Account Information#

When you create an account we collect your email address and, if you choose to give one, your name. You can sign up with an email address and a password, or, in the Samvise iOS app, with Sign in with Apple, in which case we receive the email address Apple releases to us, which is a private relay address if you chose to hide your real one.

Connecting Google Calendar is a separate and optional step, described in section 1.3; creating a Samvise account does not require it, and Samvise does not use your Google account to sign you in.

1.2 Analytics Data#

We use Vercel Analytics to collect anonymized usage data to improve our service. This includes:

• Page views and navigation patterns
• Browser type and version
• Device type (desktop, mobile, tablet)
• Geographic region (country/city level, not precise location)
• Referral sources

Vercel Analytics is privacy-focused and does not use cookies for tracking. It does not collect personally identifiable information and complies with GDPR without requiring cookie consent. For more information, see Vercel's Analytics Privacy Policy.

1.3 Google Calendar Data#

To provide our scheduling services, we request access to your Google Calendar. We request exactly two permissions (OAuth scopes), and no others:

• https://www.googleapis.com/auth/calendar.readonly (read only). We use this to read events from the calendars synced on your account, so that Samvise knows when you are busy and never schedules a task on top of an existing commitment. When you first connect a Google account, Samvise starts by syncing your primary calendar and shows you the full list straight away, so you can change that selection immediately or at any time in Settings. Listing your calendars so you can choose between them is also covered by this scope. A narrower scope is not sufficient: Samvise has to see the events themselves, not only free or busy status, in order to show you what a conflict is and to let you reason about your week with the assistant.
• https://www.googleapis.com/auth/calendar.app.created (read and write, limited to calendars this app created). We use this to create a single dedicated "Samvise" calendar in your Google Calendar and to write, update, and remove the time blocks Samvise schedules for your tasks. This scope deliberately cannot touch any other calendar or any event Samvise did not create. We chose it over the broader calendar and calendar.events scopes for exactly that reason.

What we actually store from your calendar. For each event on a calendar you have selected, we store only:

• the event title
• the start time and end time
• whether the event is all day
• the number of other attendees, as a count only
• Google's opaque identifiers for the event and for the calendar it came from

We do not access or store event descriptions, locations, conferencing links, attachments, guest names, guest email addresses, or organizer details. The attendee figure is a plain integer (for example, 3), computed by counting the guests on the event and excluding you and any meeting rooms or resources. It is used to display "3 attendees" on an event in the Samvise timeline. No identity of any attendee is retrieved or retained.

Note that a Google calendar identifier is not always opaque: the identifier of your primary calendar is your Google account email address, so that address is stored alongside events synced from it.

If you connect more than one Google account, each connection is stored separately, and disconnecting one leaves the others untouched.

1.4 Task and Schedule Data#

We collect and store information you provide about your tasks, including titles, descriptions, due dates, priority levels, and scheduling preferences.

1.5 Usage Data#

We collect information about how you use Samvise, including interactions with our AI assistant and scheduling features, to improve our service.

1.6 In-App Purchases#

For mobile subscriptions, we use RevenueCat to validate store purchases, restore access, and manage subscription entitlements. RevenueCat receives your Samvise account identifier, purchase history, and subscription status. These records are linked to your account and are also used for subscription analytics. Samvise does not send your calendar events, task content, chat messages, name, or email address to RevenueCat. Apple processes payments for iOS purchases; Samvise and RevenueCat do not receive your full payment-card details.

1.7 Mobile Notifications and Support Diagnostics#

When you enable mobile push notifications, we store your Expo push token, device identifier, platform, and app version with your Samvise account to deliver notifications to the right device. On iOS, the device identifier is Apple's identifierForVendor; on Android, it is the Android ID. We also use the device identifier to update or remove a notification registration. These identifiers are used for notification functionality, not advertising or tracking across other companies' apps or websites. You can manage notification permission in your device settings.

When you submit feedback in the mobile app, we receive your report and any attachments you choose to include, linked to your account email and user ID. The Include diagnostics option adds your app version, device model, and operating system version so we can investigate the problem. This option is enabled by default, and you can turn it off before sending each report.

2. How We Use Your Information#

• To provide and improve our task scheduling service and its chat assistant
• To detect calendar conflicts and suggest optimal scheduling times
• To create and manage scheduled tasks in your Google Calendar
• To personalize your experience and provide intelligent recommendations
• To communicate important service updates and changes

3. AI Assistant and Data Processing#

Samvise has two separate scheduling mechanisms, and only one of them involves an AI model. It matters which is which, so we describe both.

3.1 Automatic Scheduling Does Not Use an AI Model#

The engine that places your tasks into free time is a deterministic program running on our own servers. It compares your tasks against your availability and your calendar busy times using ordinary arithmetic. No AI or machine learning model is involved, and no data leaves our infrastructure for this purpose.

3.2 The Chat Assistant Does Use an AI Model#

When you use the Samvise chat assistant, we send a request to our AI provider, Google Gemini (the Gemini API operated by Google LLC). To let the assistant answer questions like "when am I free on Thursday" or "move this off my meeting day", that request includes:

• Your conversation: messages and custom instructions you provide.
• Your planning context: time windows, your schedule, and your time zone.
• Your task data: task titles, descriptions, due dates, priorities, durations, projects, and scheduling metadata.
• Your Google Calendar data: the title, start time, end time, and all-day flag of your upcoming calendar events, and the attendee count described in section 1.3. These are the busy times Samvise has synced from the calendars selected on your account. They are included in the assistant's context so it can reason about your real commitments, and they may also be returned to the model when the assistant runs one of its read-only lookup tools on your behalf.

For Google Calendar events, only the fields listed in section 1.3 are available to the model. Event descriptions, locations, guest names, and guest email addresses are never sent, because Samvise never retrieves them in the first place.

This transfer happens only after you grant permission to use Google Gemini for chat. It supports your conversation and its generated title. If you decline permission or do not use chat, no Google Calendar data is sent to the assistant. Files require separate permission.

We send these requests to Google Gemini to provide your conversation and its title. Samvise does not use your content to train or improve generalized AI models. Section 4 explains our restrictions on Google Calendar data.

We use the paid Gemini API for the assistant. The Gemini API Additional Terms of Service state that Google does not use paid-service prompts and responses to improve its products and processes them under its Data Processing Addendum. Paid-service treatment depends on using a project associated with an active Cloud Billing account. Samvise does not use the unpaid tier for the assistant.

Paid service does not mean zero retention or no human review. Google's abuse-monitoring policy specifies 55 days of retention for prompts, context and output for safety, policy enforcement and required legal or regulatory disclosures. Authorized Google personnel may review flagged content. Google limits the use of these logs to policy enforcement and prevention, including models used specifically for that purpose, rather than general model training. These provider-held logs are separate from Samvise's own records and from optional developer logging and data sharing. Deleting your Samvise account does not immediately erase Google's abuse-monitoring records.

3.3 Chat Attachments#

Files you attach in chat are sent to the AI provider only after you grant explicit consent, which you can revoke at any time in Settings.

4. Important Restrictions on Google Data Usage#

We limit our use of data obtained through Google APIs to providing and improving the user-facing scheduling features that are prominent in the Samvise interface: conflict detection, automatic task scheduling, the calendar timeline, and the chat assistant. These restrictions apply to the raw data we receive from Google as well as to anything aggregated, anonymized, or derived from it.

In compliance with the Google API Services User Data Policy, Samvise explicitly does not:

• Transfer or sell your Google user data to third parties such as advertising platforms, data brokers, or information resellers
• Transfer, sell, or use your Google user data for serving advertisements, including retargeting and personalized or interest-based advertising
• Transfer, sell, or use your Google user data to determine credit-worthiness or for lending purposes
• Use your Google user data to create, train, or improve any generalized or non-personalized artificial intelligence or machine learning model, including foundational models. We do not retain Google user data for any such purpose. Google user data is used only to execute the user-facing features described in this policy for the individual user it belongs to

4.1 Human Access to Your Data#

We do not allow humans to read your Google user data, except in these narrow cases:

• You have given us your explicit, affirmative agreement to view specific data, for example when you send us a support request that requires it
• The access is necessary for security purposes, such as investigating abuse or a suspected compromise
• The access is required to comply with applicable law or regulation
• The data has been aggregated and anonymized, and is used only for internal operations

4.2 Limited Use#

Samvise'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.

5. Data Security#

We implement industry-standard security measures to protect your data:

• Google OAuth access and refresh tokens are encrypted with AES-256-GCM authenticated encryption before they are written to the database, using a key held outside the database. They are never logged and never exposed in plaintext
• All data is protected by Row-Level Security (RLS) policies in our database, enforced at the database level rather than only in application code
• Communications are encrypted in transit using HTTPS/TLS
• Access to your data is restricted to only your authenticated account
• We regularly review and update our security practices

Our full security posture is described in our Security Practices page.

6. Cookies and Tracking Technologies#

Samvise uses minimal cookies and tracking technologies:

• Essential Cookies: We use session cookies to maintain your authentication state and remember your preferences. These are strictly necessary for the service to function.
• Analytics: Vercel Analytics collects anonymized usage data without using cookies. No tracking cookies are placed on your device for analytics purposes.

We do not use advertising cookies, third-party tracking cookies, or sell data collected through cookies to third parties.

7. Data Sharing#

We do not sell your personal information. We share data only with the service providers below, each of which processes it on our instructions and only as needed to run Samvise.

For more information about RevenueCat's processing, see its Privacy Policy.

Vercel Analytics and Vercel Speed Insights collect the anonymized, non-identifying usage measurements described in section 1.2. They receive no calendar data, no task content, and no Google user data.

We may also disclose information if required by law, or where necessary to protect our rights, our users, or the safety of others. If Samvise is ever involved in a merger, acquisition, or sale of assets, we will not transfer your Google user data without first obtaining your explicit prior consent.

8. Your Rights and Choices#

You have the following rights regarding your data:

• Access: You can access all your data through the Samvise application and settings page
• Export: You can export your data at any time from your account settings. Exported data includes all tasks, scheduling history, and preferences in a machine-readable format.
• Delete: You can delete your account and all associated data from your account settings
• Disconnect Calendar: You can disconnect a Google account from Samvise at any time in Settings, and keep your Samvise account. When you disconnect, Samvise revokes its own access token with Google, stops watching that calendar for changes, and deletes every calendar event it had synced from that account. If you connected more than one Google account, disconnecting one leaves the others connected. You are also offered the choice to delete the "Samvise" calendar from your Google Calendar at the same time, or to keep it.
• Revoke Access: Independently of the above, you can revoke Samvise's access from Google's own permissions page at myaccount.google.com/permissions. Revoking access stops Google Calendar synchronization until access is restored. Your Samvise tasks and scheduling remain available.
• Opt-out: You can disable chat history storage by toggling the chat history setting in your account preferences

9. Data Retention#

We retain your data for as long as your account is active. Specific retention periods:

When you delete your account. You start deletion from your account settings and verify your identity using an available method: a fresh Sign in with Apple confirmation in the iOS app, your password, or an email code. The iOS app offers Delete now to start deletion immediately, or Delete in 24 hours to schedule it after a grace period. You can cancel a scheduled request in account settings during that period. After the period ends, deletion begins automatically; you do not need to confirm again. If cleanup is interrupted, it retries automatically. Deletion permanently removes your authentication record and associated data, including synced calendar event records and stored Google OAuth tokens. This is not a soft delete and it cannot be reversed once processing begins. Deleting your Samvise account does not cancel an Apple subscription; manage or cancel it in your Apple Account subscription settings.

We tell Google, before we delete anything. Immediately ahead of destroying your account, Samvise contacts Google for every Google account you had connected and revokes its OAuth grant, and stops the channel Google uses to notify us of calendar changes. Every connection is covered, including any we had marked as errored or paused, because those can still hold a live grant. Destroying our copy of your tokens would already end our access; revoking asks Google to retire the grant at its end too, so the Samvise entry should disappear from your Google account on its own.

This step is deliberately best-effort and can never block your deletion. If Google is unreachable at that moment, or a token cannot be read, we record the failure and proceed with deleting your account anyway. Your right to delete outranks a tidy revoke. Because of that, we cannot promise the revoke always succeeds: check myaccount.google.com/permissions if you want to confirm, and remove any entry still listed there.

One thing does survive account deletion by design. Events that Samvise created in your Google Calendar remain in your Google Calendar. That is your own data sitting in your Google account, removing it cannot be undone, and nothing in the deletion flow asks for your permission to do so, so we leave it for you to decide. To remove it, delete the "Samvise" calendar in Google Calendar, or use the delete-the-calendar option offered when you disconnect, before deleting your account.

Sign in with Apple authorization. When you sign in with Apple, we validate Apple's identity token and authorization code and retain an encrypted refresh token so we can ask Apple to revoke access when you delete your account. We do not retain the authorization code, identity token, or access token from this exchange. The refresh token is deleted with your account, even if Apple cannot be reached. Older accounts may not have a stored token, so revocation may require you to remove Samvise from Sign in with Apple yourself. Missing tokens or an Apple outage do not prevent account deletion.

10. Children's Privacy#

Samvise is not intended for users under the age of 13. We do not knowingly collect information from children under 13. If we discover we have collected such information, we will delete it immediately.

11. Data Breach Notification#

We take data security seriously and have implemented measures to protect your information. However, in the unlikely event of a data breach that affects your personal information, we will:

• Notify affected users: We will notify you via email within 30 days of discovering a breach that is reasonably likely to result in harm, in compliance with Washington State law (RCW 19.255.010)
• Describe the incident: Our notification will include a description of the breach, the types of information involved, and the approximate date of the breach
• Explain our response: We will describe the steps we are taking to investigate the breach, mitigate harm, and prevent future incidents
• Provide guidance: We will offer recommendations on steps you can take to protect yourself, such as changing passwords or monitoring your accounts
• Contact information: We will provide contact information for you to ask questions or obtain additional information about the breach

If a breach affects a large number of users, we may also post a notice on our website and within the application. We maintain incident response procedures and regularly review our security practices to minimize the risk of breaches.

12. International Data Transfers#

Samvise is operated from the United States and uses US-based application and database hosting. Our service providers may also process data in other countries. In particular, Google's Gemini API terms permit transient storage or caching in countries where Google or its agents maintain facilities. If you use Samvise from outside the United States, your data may be transferred to the United States and other countries where our providers operate.

Where personal data is transferred out of the European Economic Area, the United Kingdom, or Switzerland, we rely on the data processing terms offered by the service providers listed in section 7, which include the European Commission's Standard Contractual Clauses. We apply the same technical protections described in section 5 to that data wherever it is held.

13. Changes to This Policy#

We may update this Privacy Policy from time to time. We will notify you of significant changes by email or through a prominent notice in the application. Your continued use of Samvise after changes are posted constitutes your acceptance of the updated policy.

14. Google API Services User Data Policy Compliance#

Samvise'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.

We limit our use of Google user data to the practices this published policy discloses. Section 1.3 lists every scope we request and every field we store. Section 3 describes the one path by which that data reaches an AI model. Section 4 sets out the restrictions we hold ourselves to, including our commitment never to use Google user data to create, train, or improve generalized or non-personalized AI or ML models. Section 9 states how long we keep it and how it is deleted.

15. Contact Us#

If you have questions about this Privacy Policy or our data practices, please contact us at:

Inference Labs LLC Seattle, Washington, United States amolvikramsingh@gmail.com

---

Last updated: September 13, 2026