Privacy Policy
This policy explains how ForgeOS at forgeyourlife.ai processes personal data, including when you use TestForge to link a Google Play app, join a private testing campaign, submit QA feedback or buy a TestForge plan or credit pack.
Service operator and contact
ForgeOS / forgeyourlife.ai operates the service. Questions, data-rights requests and complaints can be sent to [email protected].
TestForge account data
When you register, TestForge stores your name, account email, role, a salted password hash, consent time, session and security records. If you register as a tester, it also stores the Google Play account email you provide, country, device model and Android version.
AI and provider data
Other ForgeOS modules can process projects, prompts, generated drafts, saved routines, creator assets, usage, credits, support requests and optional route information when you choose those features. Provider access keys stay server-side. Features that are not connected or release-approved remain gated.
Apps, campaigns and testing data
For developers, TestForge stores app name, Android package ID, Google Play opt-in and optional Google Group links, testing instructions and campaign settings. For testers, it stores campaign applications, test-session dates and durations, structured bug or usability feedback, private scores and verdicts. It also stores credit activity, referrals, service notifications, platform feedback and audit events.
Google Play email sharing
A tester's Google Play email is not shown in public campaign listings. If the tester gives the separate sharing consent, the email is revealed only to the owner of a campaign after that tester is approved, so the owner can add the tester in Google Play Console. The campaign owner becomes responsible for using that email only for the stated closed-test purpose and for removing it when it is no longer needed.
Payments and Stripe
Stripe processes checkout, payment-method and billing details. TestForge does not store full card details. TestForge stores limited billing records such as product, amount, payment status, Stripe session, customer, subscription and invoice identifiers, and signed webhook event identifiers so it can grant credits, activate campaigns, prevent duplicate charges and manage subscriptions.
Public and private visibility
Public TestForge pages may show app and campaign details plus aggregate participation and QA counts. Account data, tester identity, payment history and private testing records require authentication. An approved campaign owner may receive the approved tester's consented Play email and campaign-associated testing information where the service makes it available. Private TestForge ratings are not posted to Google Play.
Why data is used
Data is used to create and secure accounts, provide testing and billing features, prevent abuse and duplicate payments, keep an audit trail, respond to support or deletion requests, and comply with legal obligations. Processing relies on performance of the service contract, consent for sharing a tester Play email, legitimate interests in security and service improvement, and legal obligations for required financial records. Consent can be withdrawn for future sharing by contacting support.
Processors and external services
Cloudflare provides hosting, network security and database infrastructure. Stripe provides payment and billing services. Google Play and Google Groups are external services reached through links supplied by app owners. Those providers process data under their own terms and privacy notices. ForgeOS does not sell TestForge personal data or use positive public reviews as a condition for credits.
Retention
Account, app, campaign and testing records are kept while needed to provide TestForge. Authentication sessions expire after 30 days unless revoked sooner. TestForge currently has no automatic fixed deletion schedule for all campaign, QA, credit, security or billing records; those records may remain after account anonymisation when needed for campaign integrity, fraud prevention, accounting, disputes or legal obligations. Stripe retains its own records under Stripe's policy.
Deletion and other rights
A signed-in user can request account deletion in TestForge after cancelling any active Stripe membership. Deletion revokes sessions and anonymises the account email, name, tester Play email and device profile; linked campaign, QA, credit, billing and audit records may remain without those direct identifiers for the purposes described above. Depending on applicable law, you may also request access, correction, portability, restriction or objection, or complain to a data-protection authority.
Security and international processing
TestForge uses HTTPS, hashed session tokens, salted password hashes, access controls, rate limits and signed Stripe webhooks. No internet service can guarantee absolute security. Cloudflare, Stripe or Google may process data outside your country using the safeguards described in their own privacy documentation.
Children and changes
TestForge is intended for people who can enter a binding service agreement and is not designed for children. Material policy changes will be posted on this page with an updated effective date.