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, and email-delivery status.
• 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.
• 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. AI processing, storage, and permission

Before the first outbound AI request for a signed-in account on a device, Strata identifies OpenAI, describes the categories of information that may be sent, and asks you to tap Allow AI processing. Nothing is sent to OpenAI until you allow it. You can revoke this permission from Settings at any time; future AI requests remain blocked until you allow processing again, and declining does not affect non-AI planning and tracking features.

When you deliberately use an AI feature after allowing processing, Strata sends the content needed for that request to server-side AI services, including OpenAI-powered planning, transcription, and analysis services. Depending on the feature, this can include your text, selected images, audio or transcripts, calendar event titles and times, journal text, schedules, or statistics. Friends information is not automatically included. Strata does not send this material merely because it exists in your account and does not train a Strata model on your schedule. When persistent AI memory is enabled, Strata can save limited planning summaries and preferences to your account to improve later requests; you can disable and clear that memory from Settings. Planner and analysis requests ask OpenAI not to store API responses as application state. OpenAI states that API data is not used to train its models by default unless the API account explicitly opts in, though limited request and response data may be retained for abuse monitoring for up to 30 days and may be retained longer where required by law or for security or safety reasons under its policies. See OpenAI's API data controls. Do not submit sensitive information you do not want processed by an AI provider.

5. Service providers and sharing

Strata uses Firebase and Google Cloud for authentication, databases, backend functions, app verification, security, storage, notifications, and hosting; OpenAI for AI processing after you grant permission; Loops for transactional, welcome, and account-lifecycle email delivery and contact management; 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; PostHog only after you independently enable privacy-limited retention analytics during account creation or in Settings; and Firebase Crashlytics for crash reports and diagnostics. 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. The consent choice is bound locally to the consenting Firebase account so another account on the device cannot inherit it; that Firebase UID is not sent to PostHog. Strata does not send PostHog your email, screen views, feature usage, or event content, and GeoIP enrichment and person profiles are disabled. For Loops delivery and contact lifecycle, Strata provides the email address and uses the Firebase UID as the contact identifier. 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.

6. 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.

7. 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.

8. Retention and deletion

Account content is generally retained while your account remains active. Short-lived AI caches, security records, diagnostic logs, and backups may follow different operational retention periods. 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.

9. Your choices

You can change notification, microphone, photo, and calendar permissions in iOS Settings; allow or revoke OpenAI processing 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. See Data Rights and Delete Account.

10. 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.

11. 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.

12. 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.