Privacy policy
This policy describes how Ritrat Studio operates FORGE — Build Yourself (Android package app.forge.forge). Contact: eliyacohen1223@gmail.com.
What we collect and why
- Account: a Firebase account identifier and email address, plus your Google name if you choose Google sign-in, to authenticate you, keep your progress and associate purchases. Sign in with email and password or Google before onboarding. Email/password authentication is handled by Firebase Authentication; passwords are not stored in FORGE profile records.
- Your answers: name, age, occupation or daily routine, goal, motivation, starting point, available time, obstacles and preferred practice time. We use these to personalize your plan. Earlier versions may retain previously supplied fitness information until you delete your account.
- Activity: your plan, tasks, completion records, XP, progress, AI messages, review results, selected language and time zone.
- Photos: photos you choose to send for plan personalization, photo feedback or task verification. They may contain personal or health-related information. Do not include other people, documents, addresses or information you do not want processed.
- Purchases: Google Play purchase tokens, product identifiers, status and expiry to verify subscription access. Google handles payment details; FORGE does not receive your full card number.
- Security and support: bounded usage counters, image hashes to prevent repeated rewards, app-integrity checks, diagnostic codes and reports you submit. Infrastructure providers also process technical connection data such as IP addresses for service delivery and security.
Usage analytics
Firebase Analytics records app visits, screens, selected language, onboarding steps, purchase-button interactions, checkout outcomes and task completion to understand how the app is used. It may process app-instance identifiers and approximate location derived from masked IP addresses and device information. We do not send your name, age, goal text, answers, photos, email or coaching messages as analytics event parameters. You can turn usage analytics off in Profile using Help improve FORGE. First-open events measure launches after installation, not store download totals. Analytics information follows Google Analytics retention settings and may remain in aggregate reports after account deletion.
AI processing
When you request an AI plan, coaching or photo review, relevant answers, task context, messages and any selected photo are sent through our server to OpenAI's API. No ChatGPT account is required. API response storage is disabled by our requests, but this does not guarantee zero provider retention. OpenAI may retain abuse-monitoring data for up to 30 days, with exceptions for legal or safety needs. API data is not used to train OpenAI models by default. See OpenAI's data controls.
AI outputs can be inaccurate. FORGE offers general personal-development guidance, not medical diagnosis or treatment. A photo cannot establish your body-fat percentage, nutritional deficiencies, health or actual emotional state. You can report an AI response in the app.
Photo storage and permissions
The current version does not request a starting selfie. Earlier versions may have saved a starting photo locally; clearing app data removes that local copy. Previously generated insights may remain with your account until deletion. Android app backup is disabled.
Task evidence is uploaded to private Firebase storage and deletion is attempted after the review finishes, including failed reviews. Abandoned uploads may persist until cleanup or account deletion. Review results and image hashes remain with your account; photos are not published. We request access only when you select a photo or use the camera. We do not request contacts or location permission.
Providers and sharing
Google Firebase / Google Cloud provide authentication, app-integrity checks, hosting, database and private storage. Google Play handles billing. OpenAI processes AI requests. Providers receive the data necessary for these services and may process it outside your country, including in the United States. Authorized operators can access data where necessary for support, security or legal obligations. We do not sell personal data or use it for advertising. There are no third-party advertisements in FORGE.
Retention and deletion
Profile, intake, plan, progress, messages and reports remain while your account is active. You can request deletion in Profile → Your data → Delete account, or follow our web deletion instructions without installing the app. Deletion removes your authentication account, profile, associated user records and uploaded evidence. The local starting photo is removed when deletion completes on that device; copies on another device can be removed there or by clearing app data.
Minimal account-deletion markers and purchase-ownership records may be retained separately to prevent abuse, duplicate entitlement claims and reopening a deleted account during an in-flight request. These exclude your photos, intake and coaching text and are retained while needed for fraud prevention or legal obligations. Provider security logs and legally required payment records follow the providers' retention rules. Deleting the account does not cancel a Google Play subscription.
Your choices
You may decline optional photos and answers, remove the local starting photo, change language, copy your progress export, cancel subscriptions in Google Play, and request access, correction or deletion by contacting eliyacohen1223@gmail.com. We may verify account ownership before acting. Depending on where you live, additional privacy rights and the right to contact your local data-protection authority may apply.
Adults only and security
FORGE is intended for adults aged 18 or over. We do not knowingly offer accounts to children. Contact us if a child has provided information. Data is encrypted in transit; server access, app attestation and rate limits protect the service. No system can guarantee absolute security.
Updates
We will update this page when the service's data practices change. The date above identifies the current policy.