Your information, clearly explained.
Privacy notice
Last updated: October 31, 2026
What Cursuum uses today, what stays on your Mac, and how to ask for help.
charles@predictive.companyAbout this notice
This notice describes the current Cursuum website and native Mac app. Cursuum is a social calendar in development. Questions and privacy requests are handled by Charles Jackson at charles@predictive.company. Features described as planned on the website are not automatically active in the app.
Your account and Google sign-in
Email and password sign-in uses Supabase. When you choose Google sign-in, Google and Supabase process the identity information needed to authenticate you: your email address, account identifier, name and profile image when supplied by Google. Cursuum uses account identity to sign you in and keep your local account workspace separate. Availability of Google sign-in depends on the configured release.
Signing in with Google requests identity access, not access to your Google Calendar, contacts, Gmail or Drive. Your Google password is entered with Google, not in Cursuum. Email/password credentials are sent to Supabase for authentication; the native app stores encrypted session data on your Mac.
Local calendars and selected events
Your manual availability, local relationship records, preferences and selected busy intervals are saved in encrypted files on your Mac. Authenticated accounts use separate local calendar files; the signed-out workspace is separate. This local isolation is not cloud synchronization or a promise of end-to-end encryption for hosted services.
An .ics import is read locally. Event titles are shown temporarily while you choose events. Only selected start/end times, local identifiers and inclusion choices are retained as busy intervals; event titles, guests, locations, notes and the original file are not saved by the import or uploaded. Your original export file remains wherever you saved it. Importing creates a snapshot, not a live calendar connection.
The import screen explains its date range and time zone. Within that imported range, unblocked times in your chosen daily hours are treated as available. Dates without manual or imported coverage remain unknown.
Calendar permissions and sharing
Calendar access is separate from account sign-in and is not granted automatically. The optional Google Calendar connection, when offered in the native app, requests access to read your calendar list and events, plus permission to manage events on calendars you own. Google bundles viewing, creation, editing and deletion in this permission. Cursuum currently implements creation and editing only, after you review the calendar, title and time; it has no event-deletion action. You choose calendars and which events affect availability. Events with guests and all-day events remain viewable but cannot currently be edited in Cursuum. No attendee invitations are sent by the editor.
After separate Google permission, the calendar service reads event titles and times for the selected calendars and returns them to an owner-only event picker. Titles and calendar names are temporary in the service response and app memory; they are not retained in calendar storage. The service also checks event status, transparency, recurrence, organizer flags, your own attendance response and whether attendees are present to calculate availability and prevent unsupported edits. It does not request attendee names or email addresses. Guests, locations and notes are not included in the picker response.
The connected-calendar service stores encrypted Google access and refresh credentials in Supabase Vault. Selected calendar identifiers and excluded-event hashes are private service settings. The stored availability contains opaque identifiers and start/end times, not event titles. This hosted processing uses the Cursuum Supabase project described below, unlike the entirely local .ics import.
The connection covers a rolling 30-day window. The native app can refresh while open, on returning to the app and periodically; this is not a promise of continuous background synchronization. Disconnect requests Google token revocation and deletes stored connection credentials, selection settings and associated busy intervals. If Google revocation cannot be confirmed, the app reports that separately; you can also revoke access in your Google Account.
Local sharing preferences do not publish your calendar. Creating an availability code deliberately shares free windows for your chosen hours and a 7-, 14- or 30-day range with signed-in Cursuum users who possess the code. They can combine these windows with other shared schedules. You may separately opt in to share selected activity preferences (activity, days, hours and minimum duration) with holders of that code. These preferences are stored with the revocable code and are never inferred from your events. New codes share no activity preferences unless you choose them. Event titles, guests and notes are not shared. The code can be copied onward; revoke it to stop future access. Expired codes and stale calendar imports return unknown availability. Optional private conversations store the conversation title, chosen participant aliases, membership, plain-text messages and delivery timestamps in Supabase. Joining requires explicitly accepting a single-use invitation code. Members see messages sent since they joined; leaving or removal blocks further reading. The owner can revoke invitations and remove members. Messages are not end-to-end encrypted. Conversation messages remain stored while the associated accounts exist; account deletion removes that account’s sent messages, and deleting the owner account removes its conversations. Contact support for deletion requests. No calendar events or availability are copied into chat automatically. Optional local relationship reminders use encrypted account-specific settings and display a generic notification without contact names, at most once a day between 9 am and 8 pm while the app is running. With background activity enabled in the installed Mac app, a short-lived macOS launch job checks the currently signed-in account at login and about every 15 minutes while the Mac is awake. It refreshes only your saved calendar selections and exclusions and can send your separately enabled relationship reminder after the main app quits. Internet access, an unlocked session and system permissions are required; it does not wake the Mac. You can remove the scheduled job in Settings. No event details are written to background status files, only check times and generic status. Sample preview never sends reminders; macOS controls notification permission. The website demonstration uses sample availability. No invitation or event is sent just by exploring that demonstration.
Private interests and suggested times
When you save an interest in Up for it?, the service receives the activity, duration, expiry and a reference to the other person’s availability code. The service can read this data to check for a reciprocal interest and overlapping availability. An unmatched interest is hidden from the other person. You can withdraw it or let it expire. Both people can see a time you explicitly suggest. If availability changes, the original stays visible until you confirm a replacement.
Email invitations to Cursuum
Only the configured Cursuum administrator can issue access invitations, one recipient at a time. Each single-use code is bound to the invited email address, expires after 30 days if unused, and grants Free access or a Plus/Pro trial lasting the number of days selected by the administrator. The trial starts upon redemption; Free access remains afterward, with no automatic charge. Existing accounts also require a redeemed access grant before onboarding. Supabase processes the administrator account, recipient address, selected language, grant tier, trial duration and request identifier. It stores a hash of the access code, the invited email address for administrator management and recipient verification, plus grant, expiration, revocation and redemption records. The plain code exists in the private delivery payload only during the retry window and in the email sent through Resend. Resend processes the recipient address and invitation content, including the sender’s display name. Sending or opening an invitation does not create an account, subscribe anyone to marketing, share calendar data or join a conversation.
Sending limits and request records prevent repeated invitations. Recipient addresses, sender-name snapshots and rendered content are cleared within 25 hours by scheduled cleanup. Minimal request hashes, status and provider identifiers remain until the sender account is deleted. Access-code hashes and grant records remain to enforce access, expiration and revocation; account deletion removes associated records according to their ownership. Provider retention follows Resend’s policies. A successful response means the provider accepted the message, not that it reached an inbox. Ignore unwanted invitations or contact support.
Service providers and processing locations
Supabase provides account authentication and hosted account data. The current Cursuum Supabase project is configured in the United States, East US / North Virginia (us-east-1). Account and authentication data can therefore be processed outside Canada. Local calendar files described above remain on your device in the current native implementation.
Vercel hosts the public website. Website delivery and security can produce operational request logs, including IP addresses, request URLs, browser information and timestamps. Google processes Google sign-in under its own privacy policy. Service providers may process operational data in other locations according to their own service arrangements.
Resend delivers Cursuum transactional account emails, including confirmation messages sent through Supabase. Delivery requires the recipient email address and message content, including the account-action link. Cursuum does not enable open or click tracking for these account emails. Delivery and security logs may still be processed by the providers.
The website stores your appearance preference in browser storage. This notice does not promise that hosting or authentication providers never use cookies or operational logs.
Google API data and Limited Use
Cursuum handles Google API data, including availability derived from it, in accordance with the Google API Services User Data Policy, including its Limited Use requirements. This data supports only the account, calendar and availability features described in this notice. We do not sell it or use it for advertising, credit decisions or AI model training.
Transfers and human access are limited to the purposes and exceptions allowed by that policy. This includes your consent for the relevant visible feature, necessary security work or legal obligations. Availability codes share only the authorized free windows; they do not authorize broader uses of calendar data.
Optional AI and purchase information
Optional free profile analysis is separate from paid planning. After reviewing, editing or removing up to 40 calendar titles, you can explicitly consent to send those titles to OpenAI for tentative activity and atmosphere suggestions. Notes, guest lists, location fields and account identifiers are not included. Titles themselves may contain private details; remove these before consenting. No sensitive traits are inferred, and each suggestion requires your confirmation. Raw titles are not stored in the analysis ledger; allowlisted suggestion identifiers and evidence indices are retained for safe retries for up to 24 hours and cleared on the next request after expiry. OpenAI requests use store:false; provider security and legal retention are separate, so this is not a zero-retention guarantee. Free analysis has account and service-wide limits and does not spend paid planning credits.
Local matching and search do not send your calendar to an AI provider. When cloud planning is enabled and you explicitly agree, Cursuum sends your typed request and selected derived availability windows to OpenAI. Participant references replace automatic names and share codes, but anything you type in the request may still identify you or someone else. Do not include private event notes or other information you do not want processed. Raw calendar events, titles, guests and stored messages are not automatically sent. AI results require review; arbitrary preferences in prose are not guaranteed to be understood.
Cloud requests use the provider’s no-storage request setting. Cursuum keeps the generated result for up to seven days to support safe retries; generated text can repeat parts of your request. Credit, cost, request-fingerprint and operational records are separate from that result. Provider security and legal retention may differ. A server checks that shared windows remain authorized before returning the result. Cursuum does not use this data to train models.
If you choose a paid purchase, Stripe processes payment and billing details. Cursuum receives the account/customer identifiers, subscription and invoice status, plan, currency, amounts, taxes, billing period and buyer contact/address details needed to administer your purchase and provide its agreement. Full payment-card credentials are entered with Stripe, not stored by Cursuum. A website visit or billing return page alone does not authorize a charge.
Cursuum stores a private immutable copy of your purchase agreement and terms-acceptance version/time in Supabase. It includes the buyer name, email, billing address and transaction details. You can access only your own live agreement. Resend processes that information to send a bilingual confirmation with full contract attachments; delivery status and a provider identifier are recorded for retries. No calendar events or chat content are included in the purchase agreement. Financial and contract records may be retained where legally required; deleting the app or requesting account deletion does not automatically erase Stripe’s legally retained records.
Cursuum does not use Google identity or imported calendar content for advertising, data brokerage or model training. Google identity is used for the sign-in and account purposes described here, without requesting other Google services.
Retention, access and deletion
Hosted account information is kept while your account exists, until a deletion request is processed. Local calendar information remains on your Mac until removed; signing out does not delete the account’s local calendar. Removing an app alone may leave its application data behind.
To request access, correction, an export, account deletion or help removing local copies, email charles@predictive.company from the account address where possible. These requests are handled manually, not by an automated deletion button. We verify account ownership and explain the removal steps and any records that need to be retained for operational, security or legal reasons. Provider backup and log retention may differ from active-account deletion.
You can also revoke Google access through your Google Account connections settings. Revoking Google access does not itself delete your Cursuum account or local calendar files.
Contact and changes
Contact charles@predictive.company with questions about this notice or your information. Do not email your password, sign-in codes or a complete private calendar. If data access or use changes, this notice will be updated and any additional permissions will be requested in context.