Information we collect
We collect account details such as the account identifier associated with native Sign in with Apple, the name you provide, and settings. On first authorization, Apple may provide an email address, including a private-relay address, which Supabase may receive and store for authentication; Apple does not provide an email address on every authorization. Legacy users may also have a verified phone number used for legacy phone sign-in or account recovery. We also collect the content you choose to log, including workouts, exercises, sets, meals, foods, calorie and macro estimates, supplements, bodyweight, notes, goals, preferences, and the history, personal records, consistency signals, and insights derived from those entries.
When you pair Messages, Orph stores a service-owned identity for the actual sender—a phone number or Apple-account email—and the messaging space and verification state needed to route the conversation. Orph does not use your Apple sign-in email to infer the Messages sender or automatically merge accounts. Only Orph's receipt through Photon Spectrum's signed inbound webhook of a message containing the single-use connect <token> command establishes that link.
We receive subscription and purchase status from RevenueCat and Apple, but we do not receive your full payment-card number. If you contact support, we collect the information in your request.
If you use adaptive check-ins, we store whether your plan is active or paused, quiet hours, daily message limits, enabled categories, preferred times, delivery records, and bounded reply context needed to operate the feature.
After eligibility, PostHog may receive pseudonymous identifiers and bounded product events. Those events exclude names, email addresses, phone numbers, message content, workout content, nutrition content, supplement content, schedules, transaction details, error text, and free-form text. We configure PostHog to discard IP addresses.
We may retain aggregate, content-free scheduler counts and technical logs needed to secure, diagnose, and operate the service.
How we use information
We use information to create and secure your account; parse and organize the entries you send; maintain records and progress views; provide support; manage subscription access; prevent abuse; improve reliability; and meet legal obligations.
With your permission, Orph sends fitness or nutrition text and relevant context to OpenAI so the service can interpret and respond to your entry. Orph may use FatSecret to match food descriptions with nutrition information. Calories, macros, and similar outputs are estimates and are not medical or nutritional advice.
How we share information
We share only what is needed with service providers that help operate Orph: Supabase for Sign in with Apple and legacy phone authentication or recovery and primary application data; Apple for the Sign in with Apple service and subscription infrastructure; Photon Spectrum for messaging infrastructure; OpenAI for permitted language processing; FatSecret for food matching; RevenueCat for subscription and purchase status; PostHog for bounded product analytics; and Cloudflare for website delivery and security.
Messages also pass through your carrier and platform providers. We do not sell personal information, use behavioral advertising, access HealthKit or contacts, or use advertising tracking.
Retention, export, correction, and deletion
We generally retain account and logged content while your account is active. Orph's in-app export tools let you retrieve your information. You can ask us to correct inaccurate information and use available app and Messages controls to correct logged information and plan details.
Account deletion is available in your Orph profile under Help & about → Account settings → Delete account. Read the warning, then continue to the confirmation. Type DELETE in the app to confirm. Deletion removes your primary database record immediately and irreversibly; there is no recovery window. Analytics deletion may complete asynchronously, and limited security logs or backups may persist for a restricted period. Deleting your Orph account does not cancel an Apple subscription; manage that subscription through Apple.
Your choices and messaging controls
Orph uses two separate Messages actions. After Sign in with Apple, the first Open Messages action prepares a single-use connect <token> command. Orph pairs the actual sender's phone number or Apple-account email with the authenticated account only after receiving that command through the signed inbound service, which proves control of the sender. Opening or dismissing the composer alone does not complete pairing. This first connection does not provide consent for automated service messages, adaptive check-ins, or AI processing.
Later in onboarding, you can review the Messages & coaching and Your data & AI disclosures. Consent is recorded when you tap Agree & Open Messages, before the Messages composer opens. This authorizes automated service messages and the disclosed AI processing, and prepares the default adaptive coaching plan; your existing coaching pauses and declines stay in place. Sending the prepared starter continues setup by text; it is not the action that records consent. Dismissing that composer does not withdraw consent; use the controls below to change your permissions. Message frequency varies, and carrier message and data rates may apply.
An enabled adaptive check-in plan can send only after your Messages address is connected, setup is complete, current service and AI permissions are in place, and paid access is active. Before sending, Orph uses the current log to decide whether a check-in is still relevant. Its default local schedule is 7:30 a.m. for a morning check-in; conditional nutrition, training, and supplement prompts at 3:00 p.m., 6:00 p.m., and 7:30 p.m.; an 8:30 p.m. review; and a Sunday 5:00 p.m. weekly review. Quiet hours run from 9:00 p.m. to 7:00 a.m., proactive messages are capped at four per day, and Orph will not send a second rescue nudge when you did not respond to the first.
The in-app Privacy & messaging destination lets you pause or resume proactive delivery without erasing plan rules, withdraw AI permission through a confirmed action, and reach the Privacy Policy and Terms. You can manage plan times and categories in Messages. AI withdrawal expires queued proactive work but preserves plan intent; granting AI permission again removes only the AI-related block when the plan was enabled, while a paused plan stays paused.
Replying STOP stops every service text and disables logging by text. START resumes service messaging, and HELP returns support information. Your existing tracker and account controls remain available if you stop messaging or withdraw AI permission.
Age and health information
Orph is for adults age 18 or older. It is not an emergency service and does not provide medical diagnosis, treatment, or professional nutrition advice. Contact a qualified professional for decisions about your health.
Changes to this policy
We may update this policy as Orph changes. We will revise the date above and provide additional notice when required.
Contact
Questions or privacy requests can be sent to support@textorph.com.