SOONISH · UPDATED NOVEMBER 7, 2026

Privacy, with a clear view.

Soonish is a friend-group scheduling service operated by Dan Safdie. This policy explains what we access, why we use it, and how you control it. Contact daniel.safdie@gmail.com with questions or a data-deletion request.

Information you provide

We store your Google account email and name, display name, ZIP code, timezone, optional weekly availability, circle memberships, group settings, ideas, and responses to plans. ZIP codes help suggest a fair area to meet. We use a session cookie to keep you signed in.

What Google Calendar access allows

With your permission, Soonish reads availability from your primary Google Calendar to find shared free time. Matching uses free/busy blocks rather than the names or descriptions of your existing events.

Calendar event permission also allows us to show your upcoming primary-calendar events to you on Share plans; create, read, update, and cancel the Soonish hangouts on your calendar; send invitations to participants; and read their Calendar responses to keep Soonish RSVPs in sync. We request permission for events on calendars you own; Soonish currently uses your primary calendar. Accounts connected before this permission was narrowed may still have the earlier, broader event permission until you revoke it and reconnect.

What other people can see

Your existing calendar events are private by default. If you explicitly share an event, we save its Google event identifier, title, start and end times, and location. Only members of the Soonish circles you select can see that shared snapshot. You can remove sharing on Share plans. A title can also appear in that circle’s activity history.

Circle members can see member names, circle ideas, shared plans, and related activity. People invited to a Soonish hangout receive its details and participant information through Google Calendar. Sharing an invite link lets someone join that circle, so share links with people you intend to invite. Removing sharing cannot remove copies someone has already made.

Storage and service providers

Google refresh tokens are encrypted before being stored. Access tokens are used to make Google API requests. Account, circle, plan, sharing, and operational records are stored in the service’s database. OpenAI Sites and Cloudflare provide hosting and infrastructure; Google provides account authorization and Calendar services. These providers process data needed to operate the service. Requests may generate security and diagnostic logs, including request information and errors.

How we limit use

We use Google data to provide the scheduling and event-sharing features you choose. We do not sell Google user data, use it for advertising, or use it to train general-purpose AI models. Human access is limited to your requested support, necessary security or abuse investigations, and legal obligations.

Our use and transfer of Google API data follows the Google API Services User Data Policy, including its Limited Use requirements.

Your controls and deletion

You can change your profile and availability in Settings, leave circles, remove event sharing, and sign out. To stop future Google access, remove Soonish from your Google account connections. Revoking access does not automatically delete your Soonish account, stored shared-event snapshots, or events already created in Google Calendar.

To request deletion of your Soonish account and associated stored data, email daniel.safdie@gmail.com from the Google address you use with Soonish. We may verify the request before deleting records. Some records may need to be retained for security or legal obligations. You can manage existing calendar events directly in Google Calendar.

We retain information while needed to run the service and handle support, security, and legal obligations. Shared-event snapshots remain stored until sharing is removed or deletion is requested; activity records can remain after a plan ends. Signing out alone does not delete data.

Changes to this policy

We update this page when our practices change. If we introduce a new use of Google data, we will disclose it and obtain any required consent before using data that way.