Privacy Policy

Solin · Last updated: October 12, 2026 · Effective Date: October 26, 2026 · Version 2.5

Version 2.5 takes effect on October 26, 2026. It adds two things: the iPhone app sends an error report to Sentry when it crashes or hits an unexpected error, and you can turn this off in Settings (Sections 3.2, 6.1 and 9.4); and Solin keeps the notes (description) of your calendar events, to show them with each event (Sections 3.1 and 10.1). The iPhone app does not send error reports, and Solin does not keep event notes, before October 26, 2026. Until then, Version 2.4 applies from October 17, 2026, and Version 2.3 (in effect since October 2, 2026) applies before that. The wording of each passage where they differ is at the end of this page.

Version 2.4 was published on October 3, 2026 and takes effect on October 17, 2026. One part of it is already available: Solin can change an event in your Apple calendar when you edit that event in Solin yourself, exactly as Section 10.4 describes (only events you organise, title and times only, with Undo, never in the background or by the AI). Editing Google Calendar events will not be available before October 17, 2026. Version 2.4 adds Sections 10.4 and 10.5 and changes the passages listed in the version history.

1. Introduction and Scope

This Privacy Policy ("Policy") governs the collection, use, disclosure, retention, and protection of personal information by Solin ("Solin," "we," "us," or "our") in connection with our website at solinapp.com and our mobile and desktop applications (collectively, the "Services").

Solin is operated by Sydney Poshayi, a sole proprietor, from the Province of Quebec, Canada (contact details in Section 17). This Policy is designed to comply with:

the Act respecting the protection of personal information in the private sector, CQLR c P-39.1, as amended by An Act to modernize legislative provisions as regards the protection of personal information, SQ 2021, c 25 (Quebec Law 25, formerly Bill 64; in force in stages from September 22, 2022 to September 22, 2024);
the Personal Information Protection and Electronic Documents Act, SC 2000, c 5 (PIPEDA); Canada's Anti-Spam Legislation, SC 2010, c 23 (CASL); and
all other applicable Canadian federal and provincial privacy and electronic communications legislation.

By accessing or using the Services, you acknowledge that you have read, understood, and agree to the terms of this Policy. If you do not agree, you must immediately discontinue use of the Services.

2. Definitions

"Confidentiality Incident" means any unauthorized access to, use, communication, publication, or loss of Personal Information, as defined under Quebec Law 25.

"Personal Information" means any information about an identifiable individual, including name, email address, usage data, and any other data that can be used, alone or in combination, to identify a person.

"Processing" means any operation performed on Personal Information, including collection, storage, use, disclosure, transmission, deletion, or destruction.

"Sensitive Personal Information" means Personal Information that, due to its nature or the context of its use, requires heightened protection, including health information, financial information, biometric data, and information that may be used for identity theft.

"Services" means all products, applications, websites, APIs, and related services offered by Solin.

"User" means any individual who accesses or uses the Services.

3. Personal Information We Collect

3.1 Information You Provide Directly

Account information: Email address, display name, and authentication credentials provided through sign-in with Google, sign-in with Apple, or magic link authentication.
User-generated content: Tasks, notes, calendar entries, schedules, goals, habits, and any other content you create or input within the Services.
Calendar integration data: When you connect Google Calendar or Apple Calendar, or let the iPhone app read the calendars on your iPhone, we access calendar event details (titles, dates, times, locations, attendees, and each event's notes) to provide scheduling features and to show you your events. We do not access the attachments of calendar events. Calendar data is never sold, shared with advertisers, or used to build profiles for third-party purposes. See Section 10 for full calendar data provisions.
Communications: Messages, feedback, support requests, and other communications you send to us, including questions you ask in Ask Solin.

3.2 Information Collected Automatically

Usage data (only if you opt in to analytics): pages visited and a small set of named product events (for example, "task completed"). See Section 9.
Device and technical data: Browser type and version, operating system, time zone, language preferences, and your IP address as it appears in our servers' and hosts' standard request logs.
Log data: Server logs and error reports from the website, our servers, and the iPhone app (Section 9.4). These do not include the content of your tasks, notes, or messages.
Cookies and similar technologies: We use strictly necessary session cookies and functional cookies. Analytics requires your prior consent under Quebec Law 25. See Section 9 for full details.

3.3 AI Interaction Data

What is sent. When you use AI-powered features (such as natural language task entry, scheduling suggestions, DraftMyDay, replanning, Ask Solin, and the short lines Solin writes in your day), the text you input, together with the task, habit, routine, schedule, and calendar-event context (titles and times) the feature needs, is transmitted to our AI provider, Anthropic (in the United States), to generate a response. Some AI features also run in the background without you pressing a button (for example, a nightly draft of your next day, and your weekly summary); they use the same kinds of data. When a feature works on a task, such as sorting it into a category or suggesting steps for it, the task's notes go along with its title. Once you have written five or more reflections, a daily background job also sends your recent reflections and the names of your habits to Anthropic, to build the working picture described in Section 3.6. We do not attach your account identifier or any other user ID to these requests, and we do not deliberately include your email address or name, although text you write yourself may contain them.

What Anthropic does with it. Under Anthropic's commercial terms, API data is not used to train Anthropic's models. Anthropic deletes it within 30 days of receipt, except where content is flagged for a violation of Anthropic's usage policies (then it may be kept up to two years) or where longer retention is required by law. We do not claim that Anthropic keeps nothing.

What Solin keeps. We do not store the prompts we send, or the AI's raw output. A reply Solin may reuse (for example, today's draft or the day's Insights line) is kept for up to 7 days, or 2 days if it may mention your calendar events. After that, only a record that the feature ran remains (which feature, the model, the size, the cost, the timing, and whether it worked), with no content. Disconnecting a calendar deletes, at once, the stored replies that may mention its events. Your Ask Solin conversations are kept in your account until you delete them or your account: you can delete any one of them in Ask Solin (Past conversations), and it is then deleted at once, on all your devices, and cannot be recovered. What else Solin wrote for you as part of your history stays in your account until you delete your account (Section 3.9): your weekly summaries, the morning observations Solin showed you, and each day draft's timing and whether you used it (the draft's wording is cleared after 7 days). These can repeat words from your tasks, habits, and calendar. Like all deleted data, deleted replies remain in our database provider's backups until they age out, within 30 days (Section 3.9). Our logs and error reports do not contain AI prompts or replies, only which feature ran, its timing, and an error code. We do not use your data to train AI models.

Ask Solin. When you type a question in Ask Solin, the question is converted to a numeric representation by Voyage AI to find the most relevant help entries, and then answered with Anthropic. Voyage AI receives the question text only, with no account identifier, and handles it under its own terms and privacy commitments (linked in Section 6.1).

If you dictate on the web with the microphone button in the add bar, the speech is processed by your browser's own speech service (run by the browser vendor), not by Solin. If you dictate on the iPhone, the phone turns your speech into text on the phone when it can, and otherwise uses Apple's speech servers, under Apple's terms. Solin does not receive the audio, only the text returned to the field.

You must not input into AI features: (a) sensitive personal information of third parties; (b) confidential business information you are not authorized to disclose; (c) government-classified information; or (d) any information whose disclosure would violate applicable law.

3.4 Third-Party Authentication Data

If you sign in using Google or Apple, we receive only the information necessary to create and authenticate your account (typically your email address and a unique identifier). We do not receive your passwords or payment credentials from those providers.

3.5 Granular Data Retention Schedule

Backups follow one rule everywhere in this Policy: they roll off within 30 days (Section 3.9).

Data Category	Retention Period	Legal Basis
Account information (email, name)	Duration of account; deleted when you delete your account (Section 3.9)	Contract performance
User-generated content (tasks, notes, habits, routines, reflections)	Duration of account; deleted when you delete your account	Contract performance
Calendar integration data (Solin's copy)	Until you disconnect the calendar or delete your account. Disconnecting deletes Solin's copies immediately and never changes or deletes anything in your own calendar. Solin changes an event in your own calendar only when you edit that event in Solin (Section 10.4)	Consent
AI replies Solin may reuse	Up to 7 days; 2 days if they may mention calendar events; immediately when you disconnect that calendar. Prompts and raw AI output are not stored. A record that the feature ran, with no content, stays for the duration of the account	Contract performance
What Solin wrote for you as part of your history (weekly summaries, morning observations, each day draft's timing and whether you used it; the draft's wording is cleared after 7 days)	Duration of account; deleted with it (Section 3.9)	Contract performance
AI inputs held by Anthropic	Up to 30 days, or up to two years if flagged for a policy violation (Anthropic's terms)	Legitimate interest (safety)
Ask Solin conversations while signed in	Until you delete them (each one, in Ask Solin) or your account. Deleting one is immediate and permanent (Section 3.3)	Contract performance
Support chats with Ask Solin while signed out	90 days, then deleted	Legitimate interest
Usage analytics (PostHog), only if you opt in	12 months	Consent
Error reports (Sentry)	30 days	Legitimate interest
Server and hosting logs (Railway, Vercel)	Set by each platform; about 30 days	Legitimate interest (security)
Billing and transaction records	7 years, held by Stripe (card payments) and Apple/RevenueCat (App Store purchases). Solin deletes its own copy of your billing rows when you delete your account	Legal obligation (Canadian tax law)
Deletion record	3 years. Holds only a keyed hash of your account ID, the date, your plan, and a few yes/no results. No email, no name, no content (Section 3.9)	Legitimate interest (proof we honored the deletion; safe restores)
Backups (Neon point-in-time history)	Rolls off within 30 days. Deleted data stays in backups until then	Operational necessity
Communications with support (email)	3 years, or earlier if you ask	Legitimate interest (dispute resolution)
Behavioral event log (behavioral_events)	12 months, then deleted; deleted with account	Contract performance (personalization)
Derived behavioral patterns (behavioral_patterns)	Duration of account; deleted with it	Contract performance (personalization)
Your working picture (energy profile, scheduling preferences, consistency scores, cycles, observations, and the notes drawn from your reflections: Section 3.6)	Duration of account; deleted with it	Contract performance (personalization)
Onboarding questionnaire responses	Duration of account; deleted with it	Consent
Notification preferences	Duration of account; deleted with it	Contract performance
Push notification tokens / web push subscriptions	Until the device unregisters, the OS reports the token invalid, or you delete your account (whichever is sooner)	Consent
Short-lived cache (Upstash)	Minutes to about 36 hours; deleted when you delete your account	Contract performance
Confidentiality Incident Register	5 years minimum	Legal obligation (Quebec Law 25)

3.6 Behavioral Telemetry and Performance Data

To plan for you, Solin learns how you work from how you use the planner. This is stored on our servers and used solely to tailor the Services to you. The first layer is two database tables (behavioral_events and behavioral_patterns); the second, your working picture, follows below.

What we store: timestamps, durations, hour-of-day integers, day-of-week, anonymous category slugs (such as "deep-work" or "admin"), the UUIDs of the records each event refers to, and your user ID. Schema-level validation prevents task titles, note content, calendar event titles, habit names, intention text, or any other free-text content from entering these payloads.
Derived patterns: on a weekly schedule, we compute aggregate snapshots (peak focus window, capacity trend, day-of-week completion factor, category avoidance, habit timing) from the raw event log and store them in behavioral_patterns. Snapshots hold one row per user per pattern. Raw events older than 12 months are deleted.
Your working picture: from those patterns and from the reflections you write, Solin keeps a private profile of how you work: when your energy is highest, how you like to schedule, how consistently you finish things, the cycles it notices, how its past suggestions turned out, and the morning observations it shows you (user_models, behavioral_cycles, drift_observations). Once you have written five or more reflections, a daily background job sends your recent reflections (up to 30) and your habit names to Anthropic, which returns three kinds of notes: what tends to get in the way of a habit, areas where you are growing, and short statements about who you are becoming. Solin stores them in your account and uses them to plan and to write its lines for you.
How it is used: solely to personalize plans for you within the Services — feeding the DraftMyDay AI prompt, the daily lines Solin writes, the weekly review email, and proactive notifications. We do not use behavioral data for advertising, do not sell it to data brokers, and do not share it with third parties for any purpose other than the AI provider processing the request that used it. It is separate from the optional analytics in Section 9.
Deletion, export and control: all of it is deleted when you delete your account, and it is included in the data export described in Section 8. To have it deleted without closing your account, write to us (Section 8.2). There is not yet a setting to turn it off, and Solin may build it again as you keep using the planner.

3.7 Onboarding Personalization Questionnaire

During onboarding, we may offer a short five-question questionnaire about your typical peak energy window, daily capacity, planning tendency, hard days of the week, and biggest planning challenge. Answering is optional; the questionnaire can be skipped, and you may decline any individual question.

What we store: if you complete or skip the questionnaire, your answers are persisted in a single JSON column on your user record (users.onboarding_intelligence) as enum slugs only. No free-text input is collected in the questionnaire.
How it is used: to seed your personalized scheduling model with reasonable defaults during the first three weeks of use. The seeded values are progressively replaced by your observed behavior as data accumulates.
Deletion and export: the column is included in your data export and is deleted along with your account.

3.8 Information We Do Not Collect

We do not collect:

Government-issued identification numbers (SIN, passport, driver's license)
Financial account numbers or credit card data (handled entirely by Stripe and Apple)
Biometric data
Health or medical information that we ask you for
Precise geolocation data
Information about minors under 13 years of age

You decide what you write in tasks, notes and reflections. If you write something sensitive, it is stored and, for the AI features you use, sent as described in Section 3.3.

3.9 Deleting Your Account

How. Open Settings → Account → Delete account in the web app or the iPhone app. You confirm by typing a confirmation and signing in again (within the last ten minutes; Sign in with Apple accounts re-authenticate with Apple). Deleting is immediate and cannot be undone. Settings also offers a copy of your data to download first.

What happens, in this order.

If you signed in with Apple, we revoke Solin's Sign in with Apple authorization.
If you have a card subscription (Stripe), we cancel it. If we cannot cancel it, we stop and tell you, so you are never billed after deleting. You can try again or write to support@solinapp.com.
If you connected Google Calendar, we stop its change notifications and revoke Solin's Google access.
In one step, we delete everything tied to your account from our database: your tasks, subtasks, notes, habits, routines, reflections, intentions, calendar data and stored calendar credentials, behavioral data, AI replies and what Solin wrote for you, Ask Solin conversations, feedback, push tokens, and your subscription records, and finally the account itself. In the same step we also delete the AI summaries our background jobs made, since you joined, from feedback and support questions (they are not linked to one person, so all of them from that period go). It either all succeeds or none of it changes. In that same step we write the deletion record described below.
Right after, we delete your cached data, close your open sessions, and ask Stripe to delete your customer record. A Google revoke or Stripe deletion that did not work the first time is retried automatically until it succeeds, and we are alerted if one keeps failing. We are adding the deletion of your RevenueCat subscriber record to this step; until that is switched on, RevenueCat keeps its record of your App Store purchases under its own rules. We then email you a confirmation (Section 5.1; it is not marketing).
The app clears the data stored on your device (cached tasks, widget, scheduled reminders, push registration) and resets the analytics device ID if you had agreed to analytics.

What is kept, and why.

A minimal deletion record, kept for 3 years. It exists so we can show that a deletion was done and so that, if a database backup is ever restored, we can delete the accounts that had already been deleted. It holds only: a keyed hash of your account ID (a scrambled value that can only be matched to an ID someone already has, using a secret key we hold; it cannot be turned back into your ID, email or name), the date and time of deletion, your plan (free, trial or paid), and yes/no results of the deletion steps (whether an Apple link existed, whether Apple's revoke worked, whether a subscription was still active, whether cancelling a card subscription failed). It holds no email address, no name, no tasks or other content, and no account ID or payment-provider ID once clean-up has finished. While clean-up at Stripe is still being retried, normally minutes, the record temporarily holds your account ID and Stripe customer ID; both are erased when clean-up finishes or is abandoned. After 3 years the record is deleted.
Stripe keeps invoices and payment records for 7 years because Canadian tax rules require it. Deleting your Stripe customer record removes your saved payment methods; it does not remove those records. Apple and RevenueCat keep App Store purchase records under their own rules.
Backups. Our database provider keeps a point-in-time history so we can recover from an incident. Your deleted data remains in that history until it ages out, which happens within 30 days. We do not use backups for anything else, and if one is ever restored we re-delete the accounts that were already deleted, using the deletion record.
Support emails you sent us (3 years, or earlier on request) and Ask Solin questions asked while signed out (they cannot be matched to an account).
Items that are not tied to your identity cannot be deleted by account: analytics and error reports are not keyed to you (Section 9), and expire on their own schedule in Section 3.5.

What we cannot do for you.

We cannot cancel an App Store subscription. Apple only lets you do that: on your iPhone, open Settings → your name → Subscriptions → Solin → Cancel Subscription. Deleting your account does not stop Apple billing you (Terms, Section 4.4).
We cannot remove an Apple Calendar app-specific password. We delete our stored copy, but the password stays valid at Apple until you remove it: go to appleid.apple.com → Sign-In and Security → App-Specific Passwords and delete it.
We cannot delete your Apple or Google account, or things stored on your device by the operating system.
We cannot delete data inside backups before they roll off (see above).

Timing. In the app: immediate. Clean-up at other companies: normally within minutes; retried until done. Backups: within 30 days. Deletion record: 3 years.

If deleting in the app fails (for example you no longer have access to the sign-in method, or the app tells you it could not cancel your subscription), write to support@solinapp.com with the subject "Privacy Rights Request" from the email address on the account. We will delete the account within 30 days (usually much sooner).

4. Purposes and Legal Bases for Processing

Purpose	Description	Legal Basis
Service delivery	Account creation, feature access, data sync, fulfilling requests	Contract performance
Behavioral personalization	Recording usage signals (durations, completion times, anonymous category slugs), and keeping a private working picture drawn from them and from your reflections (Section 3.6), to tailor scheduling suggestions, daily lines, weekly insights, and proactive notifications	Contract performance
Push notifications	Sending proactive in-app, mobile push, and browser push notifications you have opted in to receive	Consent
Calendar integration	Accessing and displaying your calendar data to provide scheduling features, and changing an event's title, start or end in your calendar when you edit that event in Solin (Section 10.4)	Consent
AI features	Processing your inputs and planning context to generate scheduling and productivity suggestions, including background features such as the nightly draft	Contract performance
Transactional communications	Sending magic links, account notifications, receipts, deletion confirmation	Contract performance; CASL s.6(6) implied consent
Analytics and improvement	Understanding feature usage and improving the Services (optional, only if you opt in)	Consent
Error monitoring	Detecting and fixing faults in the Services	Legitimate interest
Security and fraud prevention	Detecting, preventing, and responding to unauthorized access and abuse	Legitimate interest
Legal compliance	Complying with applicable laws, regulations, and governmental orders	Legal obligation
Business operations	Managing subscriptions, processing payments, enforcing Terms of Service	Contract performance; Legitimate interest

5. Electronic Communications and CASL Compliance

5.1 Types of Electronic Messages We Send

We send the following categories of electronic messages:

Transactional messages: Magic link sign-in emails, account verification, billing receipts, reminders you have turned on, the account-deletion confirmation, and service-critical notifications. These are sent pursuant to CASL Section 6(6) (implied consent for existing business relationship) and do not require express opt-in consent.
Service update messages: Notices of material changes to the Terms, the Privacy Policy, or the Services. These are sent on the basis of legal obligation and are not commercial in nature.
Product updates (optional): Feature announcements and newsletters. We will only send these if you have provided express consent. You may withdraw consent at any time.

5.2 Unsubscribe Mechanism

Every commercial electronic message we send includes a clear and functional unsubscribe mechanism. You may opt out at any time by:

clicking the "Unsubscribe" link in any email we send; or
contacting us at support@solinapp.com.

We will process unsubscribe requests within 10 business days, as required by CASL. Withdrawal of consent does not affect the lawfulness of prior communications.

5.3 No Harvesting or Purchased Lists

We do not harvest email addresses from third-party sources, purchase email lists, or send electronic messages to addresses obtained without appropriate consent.

6. Disclosure of Personal Information

We do not sell, rent, or trade your Personal Information. We disclose Personal Information only as follows:

6.1 Service Providers and Sub-Processors

"Only if you opt in" means nothing is sent until you choose to. "On request" means only when you use that feature. Each provider processes data under its own terms and privacy commitments, linked in the last column. We do not claim a separately negotiated agreement with any provider.

Provider	Purpose	Data Shared	Location	Provider terms and privacy
Neon	Primary database hosting, including backups and point-in-time history	All account data and content you create in the Services	United States (AWS us-east-1, Virginia). Backups roll off within 30 days	Privacy notice
Railway	Application servers and scheduled jobs	All data processed while handling your requests	United States (US East, Virginia)	Privacy; Terms
Vercel	Website hosting and delivery	Web requests, IP address, device and browser data	United States (global edge network)	Privacy; Terms
Upstash	Short-lived cache and real-time sync between your devices	Short-lived copies of session and sync data	United States (AWS us-east-1, Virginia)	Privacy; Terms
Anthropic	AI language model processing	AI input text and the task, habit, schedule, and calendar-event context a feature needs, including a task's notes when a feature works on that task. For your working picture, your recent reflections and habit names. No user ID	United States	Terms; Privacy
Voyage AI	Finds the right help entry for Ask Solin	The text of your Ask Solin question. No account identifier. On request only	Provider based in the United States	Privacy
Resend	Transactional email delivery, and our replies to support messages	Email address, email content. We do not turn on open or click tracking, so the emails contain no tracking pixels or tracked links. Mail is sent with opportunistic TLS (encrypted when the receiving mail server supports it)	United States (AWS us-east-1, North Virginia)	Privacy; Terms
Stripe	Card payments and subscription management (web)	Email address, billing metadata, payment details you enter with Stripe	United States	Privacy; Terms
RevenueCat	iPhone subscription management	Your Solin account ID, subscription and purchase status	United States	Privacy; Terms
Apple	Sign in with Apple; App Store purchases; push delivery (APNs); Apple Calendar if you connect it; speech recognition for dictation on the iPhone, when the phone cannot do it itself; Apple Weather if you turn on “Weather on Today”	Email or relay address, purchase data held by Apple; with Apple Calendar connected, the title and time changes you make to an event in Solin (Section 10.4); for dictation, the speech (Solin does not keep it); for Weather, your approximate location, sent by the iPhone to Apple Weather only while Weather is on	United States and worldwide	Privacy
Google (sign-in, Calendar)	Sign in with Google; optional Calendar integration	Email address; with Calendar connected, the title and time changes you make to an event in Solin (Section 10.4)	United States	Privacy; Terms
Expo	Mobile push notification delivery	Push token, notification content	United States	Privacy; Terms
Sentry	Error monitoring (website, servers, and iPhone app)	Error type and stack trace, page or screen route (ids removed), browser or phone model and OS, release. No user identity, cookies, request bodies, or AI content. IP address not stored; no session replay	United States (US data region). Error reports kept 30 days	Privacy; Terms
PostHog	Product analytics, only if you opt in	Named product events and pages visited; from the iPhone, a daily summary of app speed and hangs from Apple's MetricKit (counts and timings, no content); random per-device ID; IP address is discarded; no session replay and no automatic event capture	United States (US cloud). Events kept 12 months	Privacy; Terms
Cloudflare; Google (Gmail)	Receiving support email (Cloudflare email routing) and reading and answering it (Gmail)	The email you send to support, with your address, name and message	United States and worldwide	Privacy; Google privacy

Messages sent to support@solinapp.com are received by Cloudflare's email routing and forwarded to a Gmail mailbox that our team reads. We answer from that mailbox, through Resend. Messages you send from the app's Contact screen reach the same mailbox, through Resend.

6.2 Where Your Data Is Stored and Transfers Outside Quebec

Where your data is stored. Your account and everything you create in the Services — tasks, notes, habits, routines, calendar data you choose to sync, and the behavioral signals described in Section 3.6 — are stored in a PostgreSQL database hosted by Neon on Amazon Web Services in the United States (us-east-1, Virginia), including its backups. Our application servers run on Railway in the United States (US East, Virginia), and our website is served by Vercel. We do not currently store your data in Canada, the European Union, or the United Kingdom.

All service providers listed above are located outside Quebec. Section 17 of the Act respecting the protection of personal information in the private sector (as amended by Quebec Law 25) allows personal information to leave Quebec only if it would receive adequate protection, judged by its sensitivity, the purposes it is used for, the protections that apply (including those in contracts) and the law of the destination.

Solin sends Personal Information only to the providers listed in Section 6.1, and only as far as the features you use require.

By using the Services, you acknowledge that your Personal Information will be transferred to and processed in the United States and potentially other jurisdictions.

6.3 Legal Requirements

We may disclose Personal Information if required by applicable law, regulation, court order, or governmental authority. Where legally permitted, we will notify you of any such compelled disclosure before complying.

6.4 Business Transfers

In the event of a merger, acquisition, reorganization, bankruptcy, or sale of all or substantially all of our assets, your Personal Information may be transferred to a successor entity. We will provide you with at least 30 days' prior notice by email, and the acquiring entity will be required to handle your Personal Information in accordance with this Policy or provide you with a new privacy notice and an opportunity to opt out.

6.5 Aggregated and De-identified Data

We may share aggregated, anonymized, or de-identified data that cannot reasonably be used to identify you, without restriction.

7. Security and Confidentiality Incident Response

7.1 Security Measures

We implement and maintain commercially reasonable technical, administrative, and organizational safeguards, including:

Encryption of data in transit using TLS 1.2 or higher
Encryption of calendar connection credentials at rest using AES-256-GCM
Least-privilege access controls limiting data access to authorized personnel on a strict need-to-know basis
Error monitoring via Sentry (Section 9.4)
Regular review of our security practices and service providers

No method of transmission over the Internet or electronic storage is 100% secure. We cannot guarantee absolute security of your Personal Information.

7.2 Confidentiality Incident Response — Quebec Law 25

In the event of a Confidentiality Incident that presents a risk of serious injury to any affected person, Solin will:

Step 1 — Regulatory Notification: Notify the Commission d'accès à l'information du Québec (CAI) as soon as reasonably possible, and no later than 72 hours after becoming aware of the incident, in accordance with the Regulation respecting confidentiality incidents (CQLR c A-2.1, r 3.1). The notification will include: (a) the nature of the incident; (b) the Personal Information affected; (c) the approximate number of persons affected; (d) the measures taken or planned to mitigate harm; and (e) our contact information.

Step 2 — Individual Notification: Notify affected individuals as soon as reasonably possible after notifying the CAI, providing: (a) a description of the incident and Personal Information affected; (b) steps taken to reduce the risk of injury; (c) steps affected individuals can take to reduce harm or protect themselves; and (d) our contact information.

Step 3 — Incident Register: Maintain a confidential Confidentiality Incident Register recording all incidents (including those below the notification threshold) for a minimum period of five (5) years, as required by Quebec Law 25.

Notification to affected individuals will be by email to the address on file, or by another method reasonably likely to reach you (e.g., in-app notification, postal mail). Note: after you delete your account we no longer hold your email address, so we cannot notify you of an incident by email.

8. Your Rights

8.1 Rights Under Quebec Law 25 and PIPEDA

Right	Description	Response Time
Access	Request a copy of the Personal Information we hold about you (Settings also offers a data export)	30 days
Rectification	Request correction of inaccurate or incomplete Personal Information	30 days
Erasure	Delete your account yourself in the app (Section 3.9), or ask us to, subject to legal retention obligations	Immediate in the app; 30 days by request
Withdraw Consent	Withdraw consent to processing based on consent (analytics, push, calendar), without affecting prior processing	Immediate in Settings (analytics, push, calendar); 30 days (other)
Data Portability	Receive your Personal Information in a structured, machine-readable format (JSON)	30 days
Object to Processing	Object to processing based on legitimate interests or for direct marketing	30 days
Complaint	Lodge a complaint with the CAI or OPC	N/A

8.2 How to Exercise Your Rights

Submit requests to: support@solinapp.com with the subject line "Privacy Rights Request." We will acknowledge receipt within 5 business days and reply in writing within 30 days. We may require verification of your identity before processing your request. We will not discriminate against you for exercising your privacy rights. General questions can use the same address; please put "Privacy Rights Request" in the subject for privacy requests so they are tracked. Section 17 says who answers your request and what happens if we refuse or do not reply.

8.3 Right to Lodge a Complaint

Commission d'accès à l'information du Québec (CAI): www.cai.quebec.ca | 1-888-528-7741
Office of the Privacy Commissioner of Canada (OPC): www.priv.gc.ca | 1-800-282-1376

We encourage you to contact us first so we may attempt to resolve your concern directly.

9. Cookies, Consent, and Tracking Technologies

9.1 Cookie Categories and Consent Requirements

Under Quebec Law 25, non-essential cookies and tracking require your prior, informed, and freely given consent.

Category	Purpose	Consent Required	How to Opt Out
Strictly necessary	Authentication, session management, security	No — essential to the Services	Cannot be disabled
Functional	Saving preferences, language, settings, a local copy of your lists so the app opens quickly	No — directly requested functionality	Sign out (clears the local copy)
Analytics (PostHog)	Collecting usage data to improve the Services	Yes — opt-in. Off until you choose to allow it	Settings (Your data on the web), or support@solinapp.com

9.2 Obtaining and Managing Consent

The first time you use the Services we show a notice asking whether you allow analytics. Until you say yes, analytics is off and nothing is sent to our analytics provider. The default is "off". Your consent is freely given, specific, informed, and unambiguous, and you may withdraw it at any time in Settings without penalty or loss of any core feature. If you allow analytics, events use a random ID on that device; we do not link it to your email, name, or account, and our analytics provider discards your IP address. Signing out, withdrawing consent, or deleting your account stops collection and resets that ID. Because the ID is random and not linked to you, we cannot look up and delete one person's analytics events; they expire after 12 months.

9.3 No Advertising or Cross-Site Tracking

We do not use advertising cookies, cross-site tracking pixels, social media pixels, or any technology designed to track you across third-party websites. We do not sell data to data brokers or advertising networks. We do not record or replay your screen.

9.4 Error Monitoring (Sentry)

The website, our servers, and our scheduled jobs send error reports to Sentry so we can fix faults. A report contains the error and where in the code it happened, the page route (with ids removed), your browser and operating system, and the app version, and a sample (about 1 in 10) of request timings. We configure it not to include your name, email, cookies, request contents, database values, or any AI prompts or replies. Sentry stores data in its United States region. IP address storage is turned off for our whole Sentry organization, and we scrub the user identifier as a sensitive field before reports are stored. Error reports are kept for 30 days. We do not record or replay sessions.

The iPhone app sends an error report to Sentry when it crashes or hits an unexpected error. A report contains the error and where in the code it happened, the screen name (with ids removed), your phone model and iOS version, and the app version. It never contains your name, email, tasks, notes, calendar events, or any AI prompts or replies. We keep reports for 30 days, and you can turn this off in Settings (Your data → Send crash reports).

10. Calendar Integration — Special Provisions

10.1 Scope of Access

When you connect Google Calendar or Apple Calendar, or let the iPhone app read the calendars on your iPhone, we request only the minimum permissions necessary:

We access event titles, dates and times, locations, attendee names and email addresses, whether you organise an event or were invited (and your reply), whether it shows you as busy or free, and whether it repeats, to display and sync your schedule within the Services.
Solin keeps an event's description (its notes), up to 2,000 characters, to show it with the event in Solin on the web and on the iPhone. Notes are never sent to our AI provider (Section 10.2), and never appear in our logs, error reports, analytics, or notifications. They are deleted with Solin's copy of the calendar when you disconnect it or delete your account, and are included in your data export (Section 8). Your calendar provider may also send an event's attachments; Solin does not store, show or use them. When you edit an Apple Calendar event in Solin, the event is written back with its notes and attachments unchanged.
We do not access your contacts list beyond attendee display.
If you allow it, Solin can also change an event's title, start time and end time in your calendar, and only when you make that change yourself in Solin (Section 10.4). For Google Calendar this is a separate permission ("View and edit events on all your calendars") that Google asks you for; you can decline it and Solin will only show your events. For Apple Calendar, the app-specific password you give Solin allows it.

10.2 Use Restrictions on Calendar Data

Calendar data is used exclusively to provide the scheduling and productivity features of the Services. We do not:

use calendar data to serve advertising;
share calendar data with any third party except our service providers listed in Section 6.1, and only to the extent strictly necessary to provide the Services;
use calendar data to build profiles about you for any purpose other than providing the Services.

Calendar data and our AI provider. Solin's AI features are run by our AI provider, Anthropic (Sections 3.3 and 6.1), which processes calendar data for us as follows:

Draft my day (including refining a draft, re-planning its blocks and finding a time for one task) and replanning send Anthropic the title and the start and end time of each event that takes up that day's time, and the title of each all-day event, so Solin can plan around them. Declined events and events marked as free are left out.
The morning email, which Solin writes in the background, may send Anthropic the title of your first event of the day and how many events you have that day.
Drafting, Ask Solin and Solin's capacity notes also use totals worked out from your events (busy and free time, how many events, how full the day is), not the events themselves.
If you turn an event into a task, that task's title and times are used like any other task's.

Anthropic never receives an event's location, its guests or attendee details, its description, or your account identifier, and events from calendars you switch off are never sent. Under Anthropic's commercial terms, this data is not used to train Anthropic's models (Section 3.3). Calendar data is not sent to any other AI or analytics provider. If you do not want this, do not connect a calendar.

These restrictions apply even if third parties offer us value in exchange for calendar data. We will never monetize your calendar data.

10.3 Revocation

You may revoke calendar access at any time through your account settings or through your Google or Apple account settings. When you disconnect a calendar in Solin, we delete Solin's copies of its events and the stored connection credentials immediately. Events in your own Google or Apple calendar are not touched. Disconnecting does not remove things Solin made from those events: tasks you created from an event stay in your account, and the stored AI replies that may mention its events are deleted at the same time; your weekly summaries stay in your history, and a day draft's wording is cleared after 7 days (Section 3.3). For Apple Calendar, remove the app-specific password at appleid.apple.com as well (Section 3.9). If you revoke only on the Google or Apple side, Solin's access stops at once, and we delete the synced data within 30 days. To stop Solin from changing events while still showing them, remove Solin's access in your Google Account and connect again without the edit permission. Disconnecting never changes or deletes events in your own calendar.

10.4 Changing Events in Your Calendar

Solin changes an event in your Google or Apple calendar only when you ask it to: by moving, resizing or editing that event in Solin. It never changes your calendar in the background, on a schedule, or through the AI assistant.

What can change: the event's title, its start time and its end time (its length). Apart from the revision stamp your calendar keeps on every edit, nothing else in the event changes: Solin never creates or deletes events in your calendar, and never changes guests, descriptions, locations, reminders, or how an event repeats.
Which events: only events you organise, on calendars you are allowed to edit. Invitations from other people, read-only calendars and all-day events are not changed. For a repeating event, only the one occurrence you changed is affected.
Undo: after each change, Solin offers Undo for 10 seconds. Undo writes the previous title and times back to your calendar, unless the event has been changed again somewhere else in the meantime.
Never over a newer change: if the event was changed somewhere else since Solin last saw it, Solin does not overwrite it and shows you the latest version instead.
Guests: when you change the time of an event that has guests, your calendar provider may tell them about the new time, as it would if you had changed it in your calendar app.
What Solin keeps: Solin's copy of the event as it is now (retention in Section 3.5). Solin does not keep a separate history of your edits. Our server logs record that an edit happened, or that it failed and the type of error (internal identifiers and the time, never the event's title, times or other details), and follow the platform log retention in Section 3.5.

10.5 Google API Services User Data Policy

Solin's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular, information Solin receives from your Google Calendar:

is used only to provide and improve the features you use in Solin: showing your schedule, planning your day around it, and changing an event when you edit it in Solin;
is not transferred to others except as necessary to provide those features (to the service providers in Section 6.1, including Anthropic when event titles and times are part of an AI request, Section 10.2), to comply with the law, or as part of a merger or acquisition with notice to you;
is never used for advertising, and never sold;
is not read by people at Solin unless you ask us to (for example, in a support request), it is needed for security or to comply with the law, or it has been aggregated and made anonymous;
is not used to develop, improve or train generalized AI or machine-learning models, by Solin or by Anthropic (Section 3.3).

11. Push Notifications

11.1 Channels and Consent

The Services may send proactive notifications via two channels, each requiring its own consent:

Mobile push (iOS / Android): sent through Apple Push Notification service or Firebase Cloud Messaging via the Expo Push API (Expo, United States). Requires you to grant notification permission to the Solin mobile app on your device. A push token issued by your operating system is stored in expo_push_tokens so we can address messages to your devices.
Browser push (web): sent through the W3C Push API and your browser's push service (e.g. Mozilla autopush, Apple Push Notification service, Google FCM). Requires you to grant notification permission to the Solin website in your browser. A subscription record (endpoint URL + cryptographic keys) is stored in web_push_subscriptions.

You may revoke either consent at any time through your device or browser settings. Tokens and subscription records are also cleared from our database whenever the upstream platform reports them invalid (for example, after you uninstall the mobile app or revoke browser permission), and when you delete your account.

11.2 What Notification Content May Include

Notifications are generated by the Services and are limited to what each one needs:

Reminders you set (a task or habit reminder) include the title of that task or habit.
Completion checks ask whether you finished a scheduled task shortly after it ends, and include that task's title.
Overloaded-day notices include one figure about your own day (for example, how far the day's plan exceeds what you usually complete) and no task content.

Notes, calendar event details, intentions, and other content you write are never included. Depending on your device settings, notification text — including a task title — may be visible on your lock screen; you can hide notification previews in your device or browser settings.

11.3 Frequency and Quiet Hours

Solin limits proactive notifications (completion checks and overloaded-day notices) to limit interruption:

No more than one proactive notification per hour;
No more than one overloaded-day notice per day, and none after 17:00 in your local time;
Quiet hours: no proactive notifications during the evening and night (21:00–05:00 in your local timezone).

Reminders you set yourself arrive at the time you chose, including during quiet hours, because you asked for them. You can turn reminders off per task or habit, or in Settings → Notifications.

11.4 Per-Type Opt-Out and Global Off Switch

You may toggle individual notification categories on or off, or silence all proactive notifications entirely, in Settings → Notifications. Your preferences are persisted in your account record (users.notification_prefs) and apply across every device on which you use the Services. Transactional messages (Section 5.1) are not affected by these toggles.

11.5 No Marketing or Third-Party Use

Push notifications are used exclusively for the productivity and planning purposes of the Services. We do not use push channels to deliver advertising, do not share push tokens or subscription records with third parties other than the push delivery services above, and do not enrich notifications with data obtained from outside the Services.

12. Privacy by Design

Consistent with Quebec Law 25, Solin incorporates privacy by design and by default into the development and operation of the Services, including:

minimizing collection of Personal Information to what is strictly necessary for identified purposes;
implementing privacy-protective default settings (for example, analytics is off until you turn it on);
assessing privacy before we add new features or service providers that involve Personal Information; and
reviewing and updating our privacy practices as technology and law evolve.

13. Automated Decision-Making and AI

We do not make decisions that produce legal or similarly significant effects on you solely by automated means without human review. AI suggestions in Solin are advisory. Nothing changes in your plan until you confirm it, including when Ask Solin proposes moving a task to a different time. You retain full control over your data and all decisions made through the Services.

14. Children's Privacy

The Services are not directed to individuals under 14 years of age. A person under 14 may not create an account, and we do not knowingly collect Personal Information from children under 14, because Quebec law requires the consent of the person with parental authority (Quebec Law 25, section 4.1). If you are a parent or guardian and believe your child has provided us with Personal Information without your consent, please contact support@solinapp.com and we will delete such information within 30 days.

15. Third-Party Links and Integrations

The Services may contain links to third-party websites or integrate with third-party services. This Policy does not apply to those services. We are not responsible for the privacy practices of third-party services. We encourage you to review their privacy policies before use.

16. Changes to This Policy

We reserve the right to update this Policy at any time. For material changes, we will: (a) post the updated Policy at solinapp.com/privacy with a new effective date; and (b) send email notice to the address associated with your account at least 14 days before the changes take effect. Your continued use of the Services after the effective date constitutes acceptance of the revised Policy. If you do not accept the changes, you must delete your account before the effective date.

17. Contact and Person Responsible for Privacy

The person responsible for the protection of personal information at Solin (Quebec Law 25, section 3.1) is the owner of the business.

Sydney Poshayi
Title: Person responsible for the protection of personal information
Business: Solin, operated by Sydney Poshayi, sole proprietor
Address: 235 Rue Sherbrooke Ouest, Montréal (Québec) H2X 1X8, Canada
Telephone: 514-686-2198
Email: support@solinapp.com (privacy requests, complaints, support and general questions)
Website: solinapp.com/privacy

To ask for access to your information, to ask for a correction, or to make a privacy complaint, write to this email address or this postal address. Put "Privacy Rights Request" in the subject so we can find it. We confirm receipt within 5 business days and answer in writing, promptly and no later than 30 days after we receive your request (Quebec Law 25, section 32). If we refuse, we tell you why, which provision of law we rely on, and what remedies you have and by when (section 34).

If we do not answer within 30 days, the law treats that as a refusal. You can then ask the Commission d'accès à l'information (CAI) to examine the disagreement, within 30 days of the refusal or of the end of the 30 days (sections 42 and 43). You can also complain to the CAI at any time (Section 8.3).

18. Governing Law

This Policy is governed by the laws of the Province of Quebec and the federal laws of Canada applicable therein.

This policy is available in French and English. For residents of Quebec, the French version prevails.

19. Where the Services Are Offered and Users Outside Quebec

The Solin iOS application is offered in Canada, the United States, Australia, and New Zealand. We do not currently offer the Services in the European Union, the European Economic Area, Switzerland, or the United Kingdom, and this Policy is not designed to meet the requirements of the laws of those places.

United States. We do not sell your Personal Information and do not share it for cross-context behavioral advertising. You may exercise the rights described in Section 8 wherever you live, and we will honor any additional rights your state's law gives you.

Australia. If you are not satisfied with our response to a privacy complaint, you may contact the Office of the Australian Information Commissioner (OAIC): www.oaic.gov.au.

New Zealand. If you are not satisfied with our response to a privacy complaint, you may contact the Office of the Privacy Commissioner: www.privacy.org.nz.

Wherever you live, your Personal Information is stored and processed as described in Section 6.2.

Further corrections to Version 2.5 (October 16, 2026). Section 17 now names the person responsible for the protection of personal information, with an address and a telephone number, and says how to ask for access or a correction, how to complain, how long we have to answer, and what happens if we do not (Sections 8.2 and 17); the minimum age is 14 years (Section 14); Section 1 names who operates Solin.

Corrections to Version 2.5 (October 16, 2026). They apply from the day they were published, to every version of this Policy. Some describe what Solin already does and take nothing away: task notes and reflections sent to Anthropic, dictation on the iPhone, Weather, app speed summaries and support email (Sections 3.3 and 6.1); the working picture Solin keeps of how you work, and how to ask for it to be deleted (Sections 3.6 and 4); sensitive information you choose to write (Section 3.8). Others correct statements that were not accurate: the data export is JSON, not JSON or CSV, and access requests have no extra 30 days (Section 8); we no longer say that a written privacy assessment is done for each provider or each new feature, or that AI suggestions fall outside Quebec's rules on automated decisions (Sections 6.2, 12 and 13).

This Privacy Policy was last updated on October 12, 2026. Version 2.5, in effect from October 26, 2026; Version 2.4 applies until then. Changes since Version 2.4: the iPhone app sends an error report to Sentry when it crashes or hits an unexpected error; what a report contains and never contains, and how to turn it off (Sections 3.2, 6.1 and 9.4); Solin keeps each calendar event's notes (its description, up to 2,000 characters) to show them with the event, never sends them to our AI provider, and includes them in your data export; the calendars on your iPhone are named as a calendar source (Sections 3.1 and 10.1).

Version 2.4 (October 3, 2026). Published October 3, 2026 and in effect from October 17, 2026, 14 days after we emailed you about it; Version 2.3 applies until then. Changes since Version 2.3: Solin can change an event's title, start or end in your Google or Apple calendar when you edit that event in Solin, with Undo, only for events you organise, and never in the background (Sections 10.1 and 10.4); how to stop it (Section 10.3); the Google API Services User Data Policy and Limited Use statement (Section 10.5); exactly which calendar details Solin reads (Section 10.1) and which our AI provider, Anthropic, receives and when (Section 10.2); the calendar rows of the retention, purposes and service-provider tables (Sections 3.5, 4 and 6.1).

Update to Version 2.4 (October 4, 2026): AI replies Solin may reuse are kept for 7 days at most, 2 days if they may mention calendar events, and are deleted when you disconnect that calendar; raw AI output is no longer stored; a day draft's wording is cleared after 7 days, keeping only its timing and whether you used it; logs and error reports carry no AI content; deleting your account also deletes the AI summaries our background jobs made from feedback and support questions since you joined (Sections 3.3, 3.5, 3.9, and 10.3). These changes only reduce what we keep and apply from the day they were published.

Version 2.3 (October 2, 2026). In effect from October 2, 2026, the day it was published. Changes since Version 2.2: one backup period for every statement (Sections 3.5 and 3.9); clearer AI wording: what is sent to Anthropic, that no user ID is attached, what Anthropic retains, and that Solin keeps AI replies for the life of your account (Section 3.3); Voyage AI named as a service provider, and each provider's own terms linked (Section 6.1); Google Gemini image generation removed; a full description of what deleting your account does, what is kept (including a minimal deletion record held for 3 years), and what you must do yourself for App Store subscriptions and Apple Calendar passwords (Section 3.9); analytics is off until you opt in, with no linking to your identity (Section 9); error monitoring described in full (Section 9.4); retention schedule updated, including 12-month behavioral events, 90-day signed-out chats and platform logs (Section 3.5); mobile crash reporting removed from the list until it exists; calendar disconnect and calendar content in AI requests described accurately (Sections 10.2 and 10.3). Added provider regions and email-tracking statement (2026-10-02).

Version 2.2 (September 30, 2026). Changes since Version 2.1: named where your data is stored (Section 6.2); updated the service provider list — Anthropic replaces OpenAI, and Neon, Railway, Vercel, Upstash, and Expo are added (Section 6.1); updated AI data retention and training terms (Section 3.3); corrected what push notifications may include and how often they are sent (Sections 11.2 and 11.3); added Section 19 on where the Services are offered (Canada, the United States, Australia, and New Zealand).

Version 2.1 (May 23, 2026). Changes since Version 2.0: added Section 3.6 (Behavioral Telemetry and Performance Data), Section 3.7 (Onboarding Personalization Questionnaire), and Section 11 (Push Notifications); extended retention table (Section 3.5) with behavioral, onboarding, notification preference, and push-token rows; extended purposes table (Section 4) with behavioral personalization and push notification rows.

Version 2.4 wording, in effect from October 17, 2026 until October 26, 2026

From October 17, 2026 until October 26, 2026, Version 2.4 applies. It is this Policy as written above, except for the passages below, which read as follows in Version 2.4. Under Version 2.4, the iPhone app sends no error reports, and Solin does not keep event notes.

Section 3.1, calendar integration data: When you connect Google Calendar or Apple Calendar, we access calendar event metadata (titles, dates, times, attendees) to provide scheduling features. We do not access the body or attachments of calendar events unless you explicitly share them through the Services. Calendar data is never sold, shared with advertisers, or used to build profiles for third-party purposes. See Section 10 for full calendar data provisions.
Section 10.1, opening sentence: When you connect Google Calendar or Apple Calendar, we request only the minimum permissions necessary:
Section 10.1, second item: Your calendar provider may send an event's description (notes) and attachments along with it. Solin does not store, show or use them. When you edit an Apple Calendar event in Solin, the event is written back with them unchanged.
Section 3.2, log data: Server logs and error reports from the website and our servers. These do not include the content of your tasks, notes, or messages. Crash reporting for the mobile app is not currently in use.
Section 6.1, Sentry row: Purpose: error monitoring (website and servers). Data shared: error type and stack trace, page route, browser and OS, release. No user identity, cookies, request bodies, or AI content. IP address not stored; no session replay.
Section 9.4: the same text without its last paragraph (the iPhone app's error reports), ending instead with: The mobile app does not yet send error reports; if we add that, this section will be updated before it ships.

Version 2.3 wording, in effect until October 17, 2026

Until October 17, 2026, Version 2.3 applies. It is this Policy as written above, except for the passages below, which read as follows in Version 2.3, and the passages listed under Version 2.4 wording, which read the same in Version 2.3 (Section 10.1 aside, which reads as given here). Sections 10.4 and 10.5 are not part of Version 2.3. Editing an Apple calendar event from Solin is already available and works exactly as Section 10.4 describes; editing Google Calendar events is not available before October 17, 2026.

Section 3.5, calendar row (retention): Calendar integration data (Solin's copy): until you disconnect the calendar or delete your account. Disconnecting deletes Solin's copies immediately. Events in your own calendar are not touched. Legal basis: consent.
Section 4, calendar row (purposes): Calendar integration: accessing and displaying your calendar data to provide scheduling features. Legal basis: consent.
Section 6.1, Apple row (data shared): Email or relay address, purchase data held by Apple. Google row (data shared): Email address, calendar metadata (if connected).
Section 10.1, first two items: We access event titles, dates, times, and attendee names to display and sync your schedule within the Services. We do not access the body text, notes, or attachments of calendar events unless you explicitly paste them into the Services. (Version 2.3 has no item about changing events.)
Section 10.2, the paragraph about AI requests: Calendar event titles and times may be included in AI requests (to Anthropic, Section 3.3) so Solin can plan around your commitments and tell busy time from free time, including in background features such as the nightly draft. They are not sent to any other AI or analytics provider. If you do not want this, do not connect a calendar.
Section 10.3: the same paragraph without its last two sentences (how to stop Solin changing events, and that disconnecting never changes or deletes events in your calendar).