Privacy Policy

1. Information We Collect

We collect what you provide and what you generate while using ForGrit — the generator and the marketplace.

• Account data: name, email, authentication identifiers, and login/session metadata. If password login is supported, passwords are handled using secure hashing/authentication controls.
• Build inputs: your prompts, uploaded materials, and design choices.
• Marketplace activity: listings, purchases, offers, and messages.
• Payment, payout & verification data: payment processors, payout providers, and verification partners may process billing, payout, tax, KYC/AML, and fraud-prevention information where applicable. ForGrit does not store full card numbers.

2. How We Use Information

We use your information to operate the generator and marketplace, process transactions and payouts, prevent fraud, comply with legal obligations (including KYC/AML), and improve the service. We do not sell personal data for advertising. Where privacy laws define “sale” or “sharing” more broadly, we will provide applicable choices.

3. AI Processing, Prompts, and Generated Code

To generate plans, previews, code, quality checks, and launch guidance, ForGrit may process your prompts, project context, uploaded materials, and generated outputs through AI systems and infrastructure providers. Do not include passwords, API keys, or secrets unless ForGrit specifically asks for connection keys during deployment.

• No training on private content: We do not use private project prompts or private generated code to train or fine-tune AI models. If you publish, list, sell, or share an app, the information you choose to make public may be visible according to that workflow.
• Your project content: Your prompts and generated app code are treated as your project content. Generated app code belongs to you subject to ForGrit terms, third-party licenses, marketplace transfer rules, and applicable law.

4. GitLab Repositories and Project Content

Generated code may be stored in private GitLab repositories linked to your project. Repository access is scoped to the project owner or approved organization members based on role and permissions. Marketplace transfer workflows may update repository access only after the approved transfer step.

5. Marketplace, Ownership Transfer, and Seller Workflows

Marketplace workflows may share listing details, seller profile information, buyer information needed for the transaction, ownership-transfer status, repository-transfer status, support messages, dispute records, and payment/payout status as needed to complete the workflow. Private apps are not listed, sold, or transferred unless the owner starts and approves the relevant workflow and ForGrit review is completed where required.

6. Sharing with Service Providers

We use third-party service providers for payments, authentication, analytics, AI generation, repository hosting, cloud infrastructure, email/support, and compliance workflows. We require service providers to process data only as needed to provide their services. We do not sell personal data for advertising.

7. Data Retention

Generated code and repositories are retained according to your plan, project settings, and repository workflow. Temporary build artifacts may expire earlier. Transaction, marketplace, ownership-transfer, payout, fraud-prevention, tax, and compliance records may be retained longer where required by law or legitimate business needs.

When an eligible account-erasure request completes, ForGrit erases authentication credentials, profile and contact data, sessions, preferences, and user-owned project content. Sold or locked Design DNA inventory evidence remains permanently unavailable for resale, but direct user and job identifiers are replaced with a random, irreversible anonymous owner tombstone so that the evidence cannot identify or be linked back to the former account.

Billing, tax, payout, fraud-prevention, dispute, and compliance evidence required by law follows a separate statutory retention schedule with restricted access and is not treated as ordinary product data. The erasure receipt distinguishes erased data, anonymously preserved inventory evidence, and records governed by that separate schedule.

8. Cookies and Analytics

We use essential cookies for sign-in, security, and session management. We may use analytics cookies to understand product usage and improve ForGrit. We may use preference cookies to remember settings such as theme. We do not use ad-tracking cookies.

9. Security

We use technical and organizational measures designed to protect personal data, project data, repositories, and generated code. See the Security page for current controls and status.

10. Your Rights and Choices

Depending on your jurisdiction (e.g. GDPR/CCPA), you have the right to access, correct, delete, export your data, and object to certain processing. To exercise any of these rights, contact us at privacy@forgrit.com.

11. Children

ForGrit is not intended for children. If you believe a child has provided personal data, contact us so we can take appropriate action.

12. International Processing

Your information may be processed in countries other than where you live, depending on the service providers and infrastructure used to operate ForGrit.

13. Business Transfers

If ForGrit is involved in a merger, acquisition, financing, reorganization, or sale of assets, information may be transferred as part of that transaction, subject to applicable law and this policy.

14. Changes to This Policy

We may update this policy as ForGrit changes. We will update the “Last updated” date when changes are made.

15. Contact

If you have questions about this Privacy Policy, contact us at privacy@forgrit.com or support@forgrit.com.