Stepi Privacy Policy
Effective June 15, 2026. Last updated September 30, 2026.
- No Stepi sign-in is required. An email address is optional and only needed if you voluntarily contact support.
- No ads or tracking. Stepi includes no advertising, analytics, or cross-app tracking SDKs.
- Local-first storage. Goals, tasks, plans, calendar items, completion history, and learned preferences are stored on your device.
- Smart Planning is optional. This Pro feature uses the OpenAI API only after you give permission.
Who we are
Stepi is a goal, todo, and calendar app made by an individual developer. In this policy, “Stepi,” “we,” and “us” refer to the developer of the app. Privacy questions can be sent to alexqin411@gmail.com.
Information stored on your device
Stepi stores your goals, tasks, plans, calendar items, completion history, Smart Planning permission, and a small set of learned planning preferences locally on your device. Sensitive preferences are deliberately reduced before local storage. For example, an income value is stored as a range and an injury as a short phrase.
Stepi does not sync this content to an application database. Device backups, including iCloud device backups, are controlled by you and Apple.
Your choice and permission
Before the first Smart Planning request, Stepi identifies OpenAI as its third-party AI provider and explains which planning information may be shared. You can allow Smart Planning or continue with on-device planning.
You can revoke Smart Planning permission from Account at any time. Revoking permission switches planning to the on-device mode and prevents new planning content from being sent to Stepi's server or OpenAI.
Smart Planning
After permission, Smart Planning may send the current goal text, follow-up questions and answers, a relevant plan step and date, relevant constraints, coarse learned preferences, recent action titles, or feedback needed to create or update the plan. Depending on the goal, this content may include health, fitness, financial, or other information the user chooses to provide.
The request travels over HTTPS to a Stepi Supabase Edge Function and then to the OpenAI API. The OpenAI request contains planning instructions and the permitted planning input. It does not contain the Apple transaction, Stepi subscription hash, the user's network IP address, name, email, full task list, completion history, calendar, or a Stepi user identifier.
OpenAI does not use API inputs or outputs to train its models by default. Stepi disables API response storage. OpenAI may retain prompts and responses in abuse-monitoring logs for up to 30 days. Read OpenAI's API data controls.
On-device planning does not send planning content to Stepi, Supabase, or OpenAI.
Subscription verification and service limits
A Smart Planning request also sends an Apple-signed subscription transaction to Stepi's Edge Function. The server verifies current Pro access with Apple before contacting OpenAI. Raw transaction data is used for verification and is not written to Stepi's application database or current function logs. The Apple transaction and subscription hash are never sent to OpenAI.
The server derives a one-way keyed hash from the original transaction identifier. It stores request counts and time windows against that hash to enforce service limits. These pseudonymous usage-limit records contain no goal content or raw transaction identifier. An hourly cleanup removes each record after it has been inactive for 24 hours, normally within 25 hours of its last update. A service outage may delay cleanup.
Network and diagnostic logs
Supabase and its network provider process and log request metadata used to route requests, limit abuse, verify availability, measure performance, and diagnose errors. This metadata can include the request IP address, approximate region derived from that address, request time, function path, response status, execution duration, request identifiers, deployment identifiers, and error categories.
The current Stepi function logs do not contain the Smart Planning request body or Apple-signed transaction. Network and function logs are retained according to the active Supabase project plan. Stepi does not use this information for advertising, marketing, analytics, or cross-app tracking.
App Store privacy categories
Stepi declares health, fitness, financial information, and other user content for app functionality and product personalization. These planning-content categories are not linked to a Stepi user identity. Stepi also declares approximate location, subscription and purchase status, pseudonymous user and device identifiers, Smart Planning feature interaction, performance data, and diagnostic data for app functionality. These technical and subscription categories may be linked through network or subscription records. None of these categories are used for tracking.
Payments
Stepi Pro purchases are handled by Apple through the App Store. Stepi does not receive payment card details, billing addresses, or Apple Account credentials.
Deletion
You can delete goals and tasks inside Stepi at any time. Uninstalling the app removes its locally stored data. The retention periods for usage-limit records, Supabase logs, and OpenAI abuse-monitoring logs are described above.
Children
Stepi is not directed at children under 13, and we do not knowingly collect personal information from children.
Changes and contact
If Stepi's data practices change, this page will be updated before meaningful changes take effect. Contact alexqin411@gmail.com with privacy questions.