Privacy policy

Smitty supports optional Google Calendar, Gmail, and Google Docs features. Calendar and Gmail use separate credentials, and Gmail uses a separate OAuth client from Calendar. Enabling one does not enable the other. Google Docs access works differently: you provide a specific public Doc link or share a specific Doc with Smitty's service account as a Viewer. Smitty does not request a Google Drive authorization grant from you for that feature. Signing in with Google does not itself enable these features.

If you choose to connect Google Calendar, Smitty uses Google OAuth to request access to certain Google Account and Google Calendar information. The default connection is read-only. If you later turn on automatic calendar updates, Smitty also requests permission to create, update, and delete events that Smitty itself adds. Depending on the permissions you grant, Smitty may access:

• Your Google Account identifier and email address;
• Information about the calendars available through your Google Account, such as calendar identifiers, names, descriptions, time zones, colors, access roles, and selection status;
• Information contained in calendars that you select for synchronization, including event identifiers, titles, descriptions, dates and times, locations, recurrence information, status, organizers, attendees, availability, conferencing information, attachments or links referenced by an event, and other information included in the Google Calendar event record; and
• Technical information necessary to maintain synchronization, including the permissions granted, synchronization tokens, OAuth refresh tokens, connection status, and synchronization timestamps and error information.

Smitty requests Google Calendar permissions to read calendars you choose to sync. If you turn on automatic calendar updates, Smitty also requests permission to create, update, and delete events that Smitty added to a calendar you select. Smitty does not edit, invite guests to, or delete events it did not create.

References in this section to "Google user data" include both information received directly from Google APIs and information Smitty derives from that information.

When you choose to connect Gmail, Google asks you to authorize Smitty to identify your account and read email. You then choose the senders Smitty may read by entering email addresses or domains. Until you provide an approved sender list, Smitty does not retrieve message contents. There is no read-all-mail option.

Smitty limits retrieval to messages matching that list within a rolling 30-day window. The first check, and the first check for each newly approved sender, includes that sender's messages from the preceding 30 days, including messages received before you connected Gmail. Later checks remain within the approved sender list and rolling 30-day window. Smitty does not read the rest of your mailbox or messages older than 30 days.

For matching messages, Smitty processes the message body and HTML, sender and recipient details, subject, dates, identifiers, and supported attachments. Attachments are subject to a 15 MB cap. An oversized attachment is skipped and recorded as unread. Smitty reads each matching message individually; it does not retrieve other messages in the thread just because one message matched. We also store your sender settings, account identifier and email address, and the technical connection information needed to operate the feature.

Google's Gmail permission applies more broadly than your sender list. The sender list is a limit enforced by Smitty, not a sender-specific authorization enforced by Google. A domain entry can match multiple senders and unrelated mail from those senders. Choose entries carefully.

This Gmail feature does not send email from your account, modify or delete your mail, or manage forwarding settings. You may change or clear your approved sender list or disconnect Gmail. Removing a sender stops future retrieval from that sender; clearing the list stops message retrieval. Previously imported content and extracted items follow the retention rules below.

You may give Smitty a public Google Doc link or share a specific Google Doc with Smitty's service account as a Viewer. Smitty uses the service account's read-only Drive access to export that specific file and process its text. This does not involve an OAuth grant to your Google Drive from your account.

Smitty does not browse your Drive, read folders, or use this feature to discover other files. It does not edit, delete, publish, or change sharing permissions for your documents. A Doc you have provided may be read again when Smitty checks that known source, so changes can be reflected in household information.

To end access to a private shared Doc, remove Smitty's service account from that Doc's sharing permissions. To stop Smitty checking a public Doc, contact privacy@smittyhq.com. A publicly accessible link remains accessible to others under its Google sharing settings; stopping Smitty does not make the original Doc private. Ending source access does not automatically delete content already imported or items extracted from it.

Smitty uses Google user data only to provide or improve user-facing features that you request. Specifically, we may use it to:

• Display the Google Account and calendars available for connection;
• Synchronize events from calendars you select;
• Display selected Google Calendar events alongside other household plans;
• Convert synchronized events into corresponding household calendar items;
• Keep imported calendar items current when an event is added, changed, canceled, or removed in Google Calendar;
• If you turn on automatic calendar updates, add missing household events to a Google calendar you choose, and update or remove only events Smitty created;
• Identify scheduling conflicts and relevant household activities;
• Generate reminders, digests, planning information, and responses from Smitty's assistant;
• Associate calendar events with the appropriate members of your household;
• Maintain and troubleshoot your Google Calendar connection;
• Retrieve approved Gmail messages and export specific Google Docs you provide;
• Extract dates, events, tasks, and relevant family logistics;
• Check authorized sources again and incorporate relevant changes into household plans, reminders, digests, and assistant responses;
• Maintain approved-sender lists, known source references, and connection information needed for these features; and
• Protect the security, integrity, and reliability of the service.

Smitty does not use Google user data for advertising, personalized or interest-based advertising, retargeting, credit or lending decisions, data brokerage, or sale to information resellers. Smitty does not sell Google user data.

Smitty does not use Google user data to train general-purpose or shared artificial-intelligence models. Our service providers are not permitted to use Google user data to train their models.

Smitty may create household calendar items and other structured information derived from Google Calendar events in order to provide the features described above. Derived information may include normalized event dates and times, reminders, household-member assignments, scheduling information, and calendar summaries. We treat this derived information as Google user data for purposes of this section.

The Google data protections in this section also apply to information derived from Gmail and Google Docs, including extracted dates, events, tasks, summaries, and related household logistics. Turning source information into a structured item or summary does not remove these protections.

Smitty does not create, sell, transfer, or use aggregated or anonymized datasets derived from Google user data for advertising, profiling, data brokerage, model training, or other independent commercial purposes.

We may use limited aggregated operational measurements, such as the number of successful or failed synchronization operations, to maintain the reliability and security of the service. These measurements are designed not to contain calendar-event contents, Google Account identifiers, OAuth credentials, or information that identifies a particular user or household.

Smitty does not sell Google user data. We disclose Google user data only as necessary to provide the user-facing features described in this policy, protect the service, or comply with applicable law.

Google user data may be processed by the following categories of service providers acting on our behalf:

• Database, authentication, and storage providers that host account information, OAuth connection records, synchronized calendar information, authorized Gmail and Google Doc content, and derived household items;
• Cloud and application-hosting providers that operate Smitty's backend and web application;
• Anthropic, which receives Gmail and Google Doc text to extract household information, under the no-model-training restrictions described in Section 6. OpenAI's role described in this policy is voice transcription; Gmail and Google Doc text are not sent to OpenAI for extraction;
• Cloudflare R2, which stores Gmail attachment bytes until the 30-day raw-content purge;
• Security, monitoring, and technical-support providers where access is necessary to protect, troubleshoot, or operate the service.

Our service providers are contractually restricted to processing the information on our behalf and may not use it for their own advertising, profiling, data brokerage, or model training.

We may also disclose Google user data:

• When required to comply with applicable law, regulation, legal process, or a valid governmental request;
• When reasonably necessary to detect, investigate, prevent, or address fraud, abuse, security incidents, or technical problems; or
• Where Google user data is transferred as part of a merger, acquisition, or sale of assets, we obtain your explicit prior consent as required by Google's applicable policies.

Smitty does not transfer Google user data to advertising platforms, data brokers, information resellers, credit-reporting organizations, or lending providers.

Google handles the OAuth authorization and serves Google API requests. Relevant extracted information may pass through our delivery providers when included in enabled household plans and messages. Raw Gmail messages and attachments are not delivered to the other adult.

Google user data, including data received through Google APIs and information derived from it, is not sent to Google Analytics, Google Ads, or Meta, regardless of optional tracking consent. We do not use this data for advertising, audience matching, campaign measurement, data brokerage, credit decisions, or model training. Optional tracking consent does not change these restrictions.

Extracted family logistics are shared with the household, including logistics about children. Raw Gmail messages and their attachments are visible within Smitty only to the adult who connected that Gmail account. The other adult does not receive the raw message body, raw payload, or attachment bytes. Connecting Gmail does not share your Google credentials with other household members. Disconnecting one adult's Gmail does not disconnect the other adult's Gmail.

These Gmail source restrictions are specific to mail retrieved through the Gmail connection. Mail you forward to Smitty continues through the existing household source-sharing path. Forwarding a message should not be treated as equivalent to connecting a private Gmail source.

Smitty personnel, contractors, and service providers may not read Google user data or identifiable information derived from it except when:

• We first obtain and document your affirmative agreement to view specific messages, files, or other data for support;
• Access is necessary for security purposes, such as investigating abuse or a security-related bug;
• Access is necessary to comply with applicable law; or
• The information has been aggregated and anonymized and is used for lawful internal operations permitted by Google's applicable policies.

Permitted access is restricted to authorized people with a legitimate need and is subject to confidentiality and security controls. Routine troubleshooting or general product improvement does not by itself authorize reading private content.

Smitty uses administrative, technical, and organizational safeguards designed to protect Google user data against unauthorized access, disclosure, alteration, loss, or destruction. These safeguards include:

• Encryption of information in transit using industry-standard transport encryption;
• Encryption of stored Google OAuth refresh tokens;
• Encryption at rest provided through our database, storage, and hosting infrastructure;
• Household-level access controls intended to prevent one household from accessing another household's information;
• Restricted access to production systems and personal information;
• Secure OAuth practices, including state validation, PKCE, nonce validation, and validation of Google identity tokens;
• Revocation and removal of stored OAuth credentials when a Google Account connection is disconnected;
• Logging controls designed not to record OAuth credentials, Gmail message contents, Google Doc text, or Google Calendar event contents; and
• Monitoring, testing, and incident-response procedures intended to detect and address unauthorized access.

Gmail refresh tokens are encrypted while stored. Disconnecting a Gmail account revokes that account's token and deletes its stored credential. Calendar and Gmail use their own credentials, and Google Docs reads use Smitty's service account rather than a parent Drive grant. Disconnecting one adult's Gmail does not disconnect another adult's Gmail or Smitty's separate Calendar connection.

No method of electronic transmission or storage is completely secure, and we cannot guarantee absolute security.

We retain Google OAuth credentials only while they are needed to maintain a Google Calendar connection. When the last active Google Calendar connection associated with a Google Account is disconnected, Smitty attempts to revoke the authorization with Google and deletes the stored OAuth refresh token. After disconnection, Smitty can no longer retrieve new or updated information from that Google Account unless you reconnect it.

Disconnecting Google Calendar does not automatically delete information that Smitty previously imported or derived from your calendar. Previously synchronized event records, calendar metadata, and derived household items may remain associated with your household so that existing plans, reminders, historical context, and household records are not unexpectedly removed.

Previously imported Google Calendar items and stored copies of Google Calendar data are retained until you remove the applicable imported data, request its deletion, or delete your household. Certain derived items may be retained until the corresponding item or household is deleted.

Short-lived OAuth authorization-state records used to secure the connection process expire after approximately 15 minutes and are subsequently purged from our systems.

Limited security, audit, and operational records that do not contain calendar-event contents, Gmail message contents, Google Doc text, or OAuth credentials may be retained for up to 90 days, unless a longer period is required by law or reasonably necessary to investigate a security incident.

Raw Gmail and forwarded-email bodies, HTML, and attachments are retained for 30 days and then purged from active systems. Stored Google Doc text follows the same 30-day raw-content purge. This retention period is not user-configurable. The rolling 30-day Gmail retrieval window is a separate limit on which messages Smitty reads; it is not a statement that an imported source is retained only until its original message date is 30 days old.

Dates, events, and tasks extracted from these sources remain until someone deletes the item or the household is deleted. Deleting an item removes it from plans and lists; it does not selectively erase the original source email, attachment, or stored document text.

Removing a sender stops future mail retrieval from that sender. Disconnecting Gmail revokes that account's token, deletes its stored credential, and stops retrieval through that connection. Stopping forwarding stops new forwarded content from arriving. Ending Doc access stops future checks for the affected source. These actions do not automatically remove already saved items or purge raw content before its retention period ends.

Confirmed household deletion removes household information from active systems, including stored raw content, attachments, imported Google records, extracted items, sender settings, and connection credentials, subject to any limited retention already described in this policy for legal or security purposes. Deleting a Smitty household does not delete original messages or documents in your Google account. We do not promise erasure from every provider backup. Provider backup retention remains unverified, and this deletion promise is limited to active systems.

You may stop Smitty's future access to Google Calendar at any time by:

• Disconnecting the applicable calendar or Google Account through Smitty's settings;
• Revoking Smitty's access through your Google Account permissions; or
• Contacting us at privacy@smittyhq.com.

Revoking access through Google stops future API access but does not, by itself, send Smitty a request to delete data previously obtained from Google.

You may remove imported calendar items using the controls available in Smitty. You may also request deletion by contacting privacy@smittyhq.com.

To delete all Google user data associated with your household, along with your other household information, you may use the household-deletion control in the web application or follow the account-deletion instructions described in the "Retention and deletion" section of this Privacy Policy. Confirmed household deletion permanently removes the household's Google OAuth connection records, stored calendar metadata and event records, imported and derived calendar items, and associated account information from Smitty's active systems, subject to any limited retention required by applicable law or necessary for security, fraud prevention, or dispute resolution.

Smitty's access to, use of, and transfer of information received through Google APIs comply with the Google API Services User Data Policy and, where applicable, the Google Workspace user data and developer policy, including their Limited Use requirements. These commitments apply to source information and information derived from it.

If you connect an external AI assistant, information Smitty has already extracted or stored from Google Calendar, approved Gmail messages, or an authorized Google Doc may be disclosed to that assistant, as described in "External AI assistants."

You authorize that disclosure when you connect the assistant and choose its permissions.

The disclosure does not include raw Gmail messages, attachments, or Google Doc contents.

The assistant receives information Smitty has already stored for your account. Depending on your permissions, that may include:

• Household schedules, events, and availability;
• Responsibilities and coordination messages;
• Information Smitty has extracted or derived from connected Google Calendars;
• Information extracted from approved Gmail messages;
• Information extracted from Google Docs you have authorized;
• Information from other sources you have provided.

Smitty does not send external AI assistants raw Gmail messages, attachments, or Google Doc contents.

The assistant can access only information available to your signed-in Smitty account.

Connecting an assistant does not give you or the assistant access to another household member's restricted information.

If another adult has a private calendar event that you are permitted to see only as busy time, the assistant receives the time, not the event title, location, or child labels.

Shared household logistics, including information about children's activities, may be included when your account is authorized to access them.

A connected assistant may request supported actions through Smitty, subject to the permissions you grant and Smitty's safeguards.

Currently supported actions include:

• Creating a shared event in Smitty;
• Responding to a shared event on your behalf;
• Requesting a pickup;
• Recording pickup coverage you are taking on;
• Sending a household coordination message.

A pickup request is not complete until the other adult accepts it.

Coordination messages are sent only when the recipient's messaging consent and applicable plan limits allow them.

The MCP does not currently allow an external assistant to update or cancel an event or directly assign a responsibility.

Creating an event in Smitty does not automatically modify Google Calendar. If you have separately enabled calendar export and authorized Smitty to write to Google Calendar, an event created in Smitty may subsequently be copied to Google.

An external AI assistant is an independent service selected by you. It is not a service provider hired by Smitty.

Information disclosed to your chosen assistant may be processed, stored, or used according to that provider's privacy policy, terms, and account settings.

You can disconnect an assistant through Smitty Settings.

Disconnecting stops further access through that authorization. It does not delete information the assistant previously received or undo events or messages Smitty already created or sent.

Connections last up to 90 days unless disconnected sooner or terminated because of changes to your account or household membership.