Privacy Policy

Information you provide

We collect information you provide when you join the website waitlist, create or use an account, or contact us. This may include your email address, verified phone number, date of birth, name, username, profile photo, timezone, default location, support messages, safety reports, and any screenshots you choose to attach to a report. We use date of birth and, where available, an operating-system age declaration to enforce Cache's adults-only service.

We also store the content and actions needed to provide Cache: events and proposals; titles, descriptions, dates, locations, coordinates, timezones, privacy choices, and attendance; calendar shares; invitations and invite-recipient contact information; comments, reactions, notes, photos, videos, stickers, and covers; blocks and reports; notification preferences; and records of changes to collaborative content.

Information about other people

You may provide another person's name, phone number, or other invite information when you sync contacts, invite someone, share a calendar, or forward a message to Computa. Only provide information you are allowed to use for that purpose. Cache uses this information to match registered users, suggest people you may know, create or claim invitations, prevent duplicate or abusive outreach, and deliver the requested collaboration features.

Cache does not send Twilio SMS invitations to people who are not registered Cache users. Links for non-users are shared by the inviter through the device's share tools.

Contacts

If you enable contact sync from the invite experience, Cache uploads the contact names, normalized phone numbers, phone labels, and a device-specific source identifier available within the access you granted. Cache does not upload contact email addresses or contact photos for matching. Contact information is used to find existing Cache users, suggest people to invite or share with, and notify you when a synced contact joins where that feature applies.

You can revoke Contacts permission in device settings and delete server-side synced contacts in Cache settings. Revoking permission pauses access; the in-app delete control removes the synced contact data from active use.

Photos and videos

If you grant full photo-library access, Cache may sync metadata for non-hidden photos while the app is in the foreground. Synced metadata can include capture and modification times, precise latitude and longitude already embedded in the photo, pixel dimensions, favorite status, media subtype labels, and hashed device-local or iCloud asset identifiers. Cache uses this metadata and derived activity, time, and location signals to suggest photos for events. Cache does not request background Location Services for this feature, and photo-library sync does not upload filenames, albums, thumbnails, file paths, full EXIF data, or photo and video bytes.

Photo or video files are uploaded only when you choose to share them, use them as an avatar, cover, sticker, or report attachment, or otherwise submit them. Cache creates display and thumbnail versions for delivery and processing. You can delete synced photo metadata in Cache settings; this also deletes derived photo-analysis data and model artifacts associated with that metadata.

Location information

Cache stores location text and, when selected or available, coordinates and timezone information for profiles and events. If you choose Current Location in the event location picker, the app requests foreground location permission and sends the selected coordinates to Cache so it can resolve a timezone and save the event location. Search text, place identifiers, and location bias may be processed through Google Places and Google Time Zone services.

Cache may also use your network address with an IP-geolocation provider to suggest and store an approximate default city and coordinates. Precise coordinates embedded in photo metadata are handled as described in the Photos and videos section.

Calendar integrations

If you connect Apple Calendar, the app creates and normally reads and updates only a dedicated Cache calendar on your device. Event fields needed for synchronization, such as title, description, location, timing, privacy, and provider identifiers, are exchanged with Cache servers. Apple calendar credentials and native calendar identifiers remain on the device.

If you connect Google Calendar, Cache receives your Google account identifier and email address, granted scopes, an encrypted refresh credential, and event data for the calendar Cache creates in your Google account. Cache requests access to calendars created by Cache and does not request permission to list or import your other Google calendars. Cache may create, read, update, or delete events in the Cache-created Google calendar based on your actions and synchronization settings.

Cache's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use Google Calendar data only to provide or improve the calendar features you request, and we do not use it to train generalized artificial-intelligence models.

Computa and AI-assisted features

When you intentionally send or forward content to Computa, Cache stores the forwarded message, sender information, processing status, and resulting proposal. To interpret the request, Cache may send the message and relevant context to OpenAI, including user and sender identifiers or phone numbers, timezone, default location, candidate Cache event details, and relevant photo-suggestion metadata such as hashed asset identifiers and capture times. This context may include an event that was synchronized from a connected calendar. Cache requests that OpenAI not store the response for later retrieval, and OpenAI states that API data is not used to train its general models by default.

Computa creates a proposal for review before it changes your Cache calendar. Photo suggestions are also reviewed on your device before any photo file is uploaded. Place names may be sent to Google Places to improve a proposed event location.

Device, usage, and diagnostic information

Cache processes network address, request time, browser or app headers, referrer, device platform, operating-system version, app/build/runtime version, installation and authentication-session identifiers, push token, and delivery status. Website waitlist submissions are recorded with the submitted email and related request log information.

Our first-party product analytics records account-linked app session starts, openings of Updates, and notification openings, along with timestamps and app/build information. We do not measure advertising activity, dwell time, scrolling, or cross-company behavior. Sentry may receive sanitized error, crash, performance-failure, and diagnostic context linked to a Cache user ID and username; Cache disables Sentry's default personal-data collection, screenshots, replay, profiling, and automatic performance tracing.

How we use information

We use information to operate, secure, maintain, and improve Cache; verify phone ownership and adult eligibility; create and synchronize calendars and events; deliver invitations, media, suggestions, notifications, and support; personalize time and location behavior; provide AI-assisted proposals; measure core product use; prevent fraud, abuse, and unauthorized access; enforce our Terms and Community Rules; investigate reports; and comply with legal obligations.

Cache does not sell personal information, show targeted advertising, or perform cross-company tracking. We do not use contact, photo-library, Google Calendar, or SMS-consent data for advertising.

How information is disclosed

We disclose profile and content information to other Cache users according to the event, participation, calendar-sharing, blocking, and privacy controls you use. People with a reusable invite link may see the inviter's display name, event title and time, and an invite preview image. Anyone who receives a bearer link may be able to forward it, and link-preview services may request its preview. Private event details are not included in generic event handoff pages.

We use vendors to provide infrastructure and product functions. Depending on the feature, these include hosting, databases, object storage, content delivery, error diagnostics, phone verification and SMS, push delivery, calendar synchronization, place and timezone lookup, IP geolocation, and AI processing. Current integrations include Twilio, Expo and platform push providers, Sentry, Google, OpenAI, and hosting or S3-compatible storage providers. They may process information only to provide contracted services to Cache, protect the service, or comply with law, and not for their own advertising.

We may also disclose information when reasonably necessary to comply with law or valid legal process, protect a person from harm, investigate fraud or abuse, enforce our agreements, or protect Cache's users, rights, and service. If Cache is involved in a merger, financing, acquisition, reorganization, or sale of assets, information may be transferred as part of that transaction subject to applicable law and appropriate confidentiality protections.

SMS and phone data

Cache uses phone numbers for account verification, user matching, invitations, and optional non-marketing SMS fallback notifications. Registered users who separately opt in may receive event invitation notices, calendar-sharing invitation notices, and event-proposal review links. Consent is optional, message frequency varies, and message and data rates may apply. Reply STOP to opt out or HELP for help.

We do not sell, rent, transfer, or use mobile numbers or SMS opt-in information for third-party marketing or promotional purposes. The above excludes text messaging originator opt-in data and consent; this information will not be shared with any third parties.

Retention and deletion

We keep account and collaborative data while needed to provide Cache and maintain the history, integrity, safety, and security of shared calendars and events. Deleting a content item normally removes it from active product views while retaining a limited historical record. Unsubmitted support-report drafts and their images expire after 24 hours. First-party usage telemetry is deleted after 400 days. Photo-sync receipts are retained for up to 90 days and detailed sync mutations for up to 30 days. Some shorter-lived authentication, delivery, cache, and synchronization records expire according to their operational schedules.

Deleting your account deactivates it immediately, revokes active sessions and device delivery, and submits a request for final reviewed erasure. Final erasure deletes personal authentication, contact-sync, photo-metadata, product-analytics, support, SMS-consent, and owned storage data; removes your content from active reads; and replaces your identity in retained collaborative history with an anonymized deleted-user identity. We may retain minimized safety, fraud, security, transaction, or legal records where reasonably necessary or required by law.

Disconnecting Google Calendar removes the active integration and lets you choose whether Cache should attempt to keep or delete the Cache-created Google calendar. Disconnecting does not delete the corresponding Cache events. Revoking a device permission stops future device access but may not delete information already synced; use the relevant in-app delete or account-deletion control for server-side deletion.

Your choices and requests

You can edit profile and event information, manage event privacy and calendar shares, block users, control notification preferences, revoke device permissions, disconnect calendar integrations, delete synced contacts or photo metadata, opt out of SMS, and delete your account through the app's settings where those controls are available.

To request a copy of your Cache data or other privacy assistance, email support@caaache.com. We will ask you to verify control of the account phone number before providing account data. Depending on where you live, you may have additional legal rights to access, correct, delete, or restrict certain uses of personal information.

Security

Cache uses administrative, technical, and organizational safeguards designed to protect information, including access controls, encrypted calendar credentials, private media storage, temporary delivery URLs, and data-minimizing diagnostic filters. No storage or transmission method is completely secure, so we cannot guarantee absolute security.

Adults only

Cache is intended only for people age 18 or older. We do not knowingly provide the service to children. If you believe a person under 18 has created an account, contact support@caaache.com.

Changes to this policy

We may update this policy as Cache changes. We will update the date above and provide additional notice when a change materially affects how we use information or when consent is required.

Contact

For privacy questions or requests, email support@caaache.com.