Privacy Policy

1. Scope

This policy applies to Strata's planning app, cloud services, website, AI tools, and authenticated feedback board. It should be read together with the Terms of Service and Data Rights page.

2. Information Strata handles

• Account information: email address, Firebase account identifier, optional display name or profile image, authentication status, account-security records, email-delivery status, and the versioned record of a required OpenAI acknowledgement made during account creation.
• Planning content: tasks, events, schedules, habits, journal entries, categories, reminders, timers, completion history, statistics, and shared content you choose to create.
• Friends and safety data: the Friends identity assigned after verification, including a safe, usable first word from the Firebase Authentication display name when available or neutral random defaults, profile edits, connections, pending requests, sharing choices, preset nudges, private profile reports, and block records used to enforce your safety choices.
• AI inputs and outputs: prompts, planning answers, selected photos, voice recordings or transcripts, schedule context, journal text, habits, and statistics summaries submitted when you use AI planning, transcription, or pattern-analysis features. When you invoke AI planning, your own calendar event titles and times can be included so Strata can plan around those commitments. Strata does not automatically load or include Friends profiles, connections, schedules, shared titles, habits, statistics, or current-focus information in your AI requests.
• Device permissions: notification tokens and calendar information you choose to grant. Device calendar events are used as read-only planning anchors.
• Diagnostics: device and app version, crash information, security signals, App Check information, and privacy-limited retention analytics where enabled. Short-lived AI Planner diagnostics can include the request context the planner used, structured routing and readiness decisions, model and version details, the structured response before and after schedule validation, timing, and safe error details.
• Feedback board activity: requests, comments, votes, reports, moderation records, and a stable random public alias. Your app name and email are not shown to other board members.

3. How information is used

Strata uses information to provide and synchronize the app; build and apply schedules you approve; run timers, reminders, notifications, statistics, and shared features; generate AI responses; secure accounts; prevent abuse; troubleshoot failures; understand performance; respond to support and feedback; and meet legal obligations.

4. Required OpenAI permission

Creating a new Strata account requires you to affirmatively select an initially unchecked acknowledgement: Allow Strata to send information needed for AI features to OpenAI. For a newly created account, Strata stores the OpenAI provider name, acknowledgement policy version, and server time of acceptance in the account's Firebase profile. This limited record confirms that the required account-creation acknowledgement occurred and does not contain your prompts or other AI content. Accounts created before this requirement must grant permission before their next AI request. Strata does not send an AI request until permission has been granted for the signed-in account. This permission is separate from privacy-limited retention analytics, which remains optional and off by default. You may revoke OpenAI processing permission in Settings. Revocation stops future information from being sent to OpenAI and makes AI features unavailable until you grant permission again; it does not delete your account or disable non-AI features. The historical account-creation acknowledgement record remains with the account until the account is deleted.

5. Calendar and AI processing

If Calendar Sync is enabled, Strata reads timed events available through the iOS calendar database and shows them as read-only planning anchors. When you deliberately use an AI feature, Strata sends only the information relevant to that request through its Firebase backend to OpenAI. Depending on the feature, that information can include your prompts and planning answers; relevant calendar event titles and times; schedules, tasks, habits, journal text, timers, completion history, and statistics summaries; saved planner preferences and relevant recent chat context; and selected photos, voice audio, or transcripts that you deliberately provide. Information about another person that you enter or attach remains part of your request. Strata does not automatically add Friends-feature profiles, sharing settings, or activity. Strata does not train a Strata model on your schedule. When persistent AI memory is enabled, Strata may save concise planner preferences and learned planning patterns in your Firebase account and retrieve relevant recent chat context. You can disable and clear that memory from Settings. Planner and analysis requests use OpenAI's store:false setting. OpenAI states that API data is not used to train its models by default unless the API account opts in, but limited request and response data may be retained for abuse monitoring for up to 30 days unless different approved controls apply. See OpenAI's API data controls. Do not submit sensitive information you do not want processed by an AI provider.

6. AI Planner reports

If you choose Report Chat, you can add a short description and send the visible chat plus its recent structured planner diagnostics to Strata Support. The report may include prompts, planning answers, schedule and journal context used for that request, saved planner preferences that were used, model and version details, structured plan stages, validation results, and safe error information. It may also include bounded, client-observed request metadata such as a random request ID, app/build version, selected date, plan-or-feedback mode, request size and context counts, start/finish timing, outcome, response phase, HTTP status, and safe error class or code. Strata can match that metadata only to the signed-in account's own short-lived planner request records and briefly enrich the report with a server-derived diagnosis before delivering it to Support. This reporting does not make another AI request or change the planner's prompt or reasoning. The confirmation explains this transfer before you submit it.

Reports do not collect IP addresses, Wi-Fi names or identifiers, carrier identifiers, full HTTP headers, authentication tokens, image or voice file contents, or private hidden AI reasoning. Strata keeps the fuller diagnostic bundle in private short-lived storage and sends Support a smaller, deeply sanitized evidence snapshot through Google Cloud's monitoring notification service. Late enrichment does not extend the original expiration of about 72 hours. The submitted support copy and resulting correspondence can be retained longer so Strata can investigate, respond, prevent duplicate reports, and keep an appropriate support record.

7. Service providers and sharing

Strata uses Firebase and Google Cloud for authentication, databases, backend functions, app verification, crash reporting, notifications, short-lived AI Planner diagnostics, and delivery of user-submitted planner reports to Strata Support; Sentry for app error and crash monitoring using stack traces and limited app, device, and runtime diagnostics, with default personal-data collection, screenshots, view hierarchies, session replay, and performance tracing disabled; OpenAI for AI processing after you grant permission; Loops for authentication and lifecycle email delivery and audience synchronization using your email address and Firebase UID as its contact identifier; Cloudflare for website hosting, request routing, security, and D1 storage for the authenticated feedback board, where it processes feedback content, your Firebase UID, and standard network request metadata; Apple and Google for sign-in, calendar, and platform services where you choose to use them; Expo for app builds and push-notification delivery; and PostHog only after you independently enable privacy-limited retention analytics during account creation or in Settings.

PostHog receives a separate random analytics identifier, one retention-started event for each new opt-in identity, at most one app-active event per UTC day, and standard network request metadata. Strata uses your Firebase UID only on the device to bind the preference to the consenting account and reset the random identifier when accounts do not match. PostHog does not receive your Firebase UID, email, screen views, feature usage, or event content from Strata, and GeoIP enrichment and person profiles are disabled. Strata requires service providers that receive personal information to provide the same or equivalent protection described in this policy and to process it only for the services Strata uses. Strata does not sell personal information.

8. Friends privacy and safety

After a verified sign-in, Strata automatically creates a Friends identity. When the Firebase Authentication display name has a safe, usable first word, Strata uses that word as the initial Friends display name and username base; a short uniqueness suffix is added only if needed. Otherwise, Strata uses neutral random defaults. These defaults are never derived from an email address, the friend code remains random, the avatar is a colored initial, and the bio starts empty. Existing customized Friends profiles are preserved rather than overwritten by later sign-ins. There is no browsable profile directory: another user must enter the exact username or friend code to send a request, and full profile data is returned only to the owner, pending-request participants, and accepted friends. Provider-derived defaults and profile edits are checked for high-confidence targeted slurs; unsafe defaults fall back to neutral values, unsafe edits are rejected, and general profanity is not automatically blocked. User-authored event, schedule, to-do, habit, and category titles are checked again when shared with a friend and replaced with a neutral label when the targeted-slur filter matches; the owner's private original is not rewritten. Productivity details remain private until a request is accepted and per-friend sharing is enabled. You can privately report a profile to Strata or block another user. Blocking removes the connection and pending requests in both directions and prevents discovery, profile and shared-data access, requests, accepts, and nudges between the two accounts until you unblock. Reports are not shown to the reported user, and unblocking does not restore the friendship.

9. Feedback-board privacy

The board is pseudonymous to other members, not anonymous to Strata. Authentication privately links activity to a Firebase account for one-person-one-vote controls, safety, moderation, and deletion. Other members see only a permanent random alias and cannot use it to locate your Strata profile. The developer may access account-linked moderation records when reasonably necessary to prevent abuse or comply with law.

10. Retention and deletion

Account content is generally retained while your account remains active. Local AI chat threads and retrieved prior-chat context are limited to the most recent 14 days, and schedule-specific learned slots are pruned under Strata's recent-memory controls. Other concise planner preferences and learned patterns can remain while your account is active until they are updated, you clear saved AI memory in Settings, or you delete the account. AI Planner diagnostic and private report records are assigned an expiration about 72 hours after they are created. Firestore deletion is asynchronous, so an expired record may remain for a limited additional period while automatic deletion completes. A smaller, deeply sanitized copy deliberately submitted to Support and resulting correspondence can remain longer under Google Cloud's operational and support-retention periods. Other short-lived AI analysis caches, security records, operational logs, provider logs, and backups follow their own operational retention periods and may take additional time to expire.

Full account deletion can be initiated in Strata's Settings and automatically includes the linked feedback-board identity, requests, comments, votes, and reports. Most requests finish immediately. If a temporary provider failure prevents immediate completion, Strata records a durable deletion job, reports whether sign-in was disabled, and retries with bounded backoff for up to 30 days. The app retains an opaque confirmation reference on that device so its signed-out screen can report completion or tell you when support review is required. The separate board self-delete remains available if you want to erase only board activity and is not required before full account deletion. Limited records may be retained where required for security, fraud prevention, legal compliance, or completion of the deletion request.

11. Your choices

You can change notification, microphone, photo, and calendar permissions in iOS Settings; revoke OpenAI processing permission in Strata Settings; disable or clear persistent AI memory; independently enable or disable privacy-limited retention analytics; edit your Friends identity and per-friend sharing; report or block a Friends profile; correct content in the app; separately delete feedback-board activity; and initiate full Strata account deletion. Revoking OpenAI processing stops future AI transfers and disables AI features until you grant permission again, without deleting your account or disabling non-AI features. Retention analytics is separate, optional, and off by default for every account. See Data Rights and Delete Account.

12. Security

Strata uses authenticated requests, Firebase security rules, App Check, encrypted transport, server-side secrets, access controls, and abuse limits. No online service can guarantee absolute security.

13. Children

Strata is not intended for children who are below the minimum age required to consent to online services in their region. A parent or guardian should supervise use where required by law.

14. Changes and contact

Material changes will be reflected by a new update date and, when appropriate, an in-app notice. Privacy questions and requests can be started through the Support page.