1. Who We Are

  • Controller: 3i7 LLC (United States)
  • Contact (privacy): gpts-privacy@proton.me
  • Scope: This policy covers the website, the blog, and the apps (Tuning System and Editor) under the same domain.

2. What We Collect

  • Account and profile: Google account ID (UID), display name, email, photo URL.
  • Public profile: A profile page is created automatically on first login (e.g., /users/<id>/).
  • User content and activity: Paddle setups, comments, likes/reactions, and other explicit actions you publish. Public content is visible to others and may be indexed.
  • Technical data: Basic device/browser info, IP-derived region, and service logs for security and reliability.
  • Analytics: Google Analytics 4 (GA4) for aggregate usage metrics. See Cookies & Analytics.

3. How We Use Data

  • Provide and maintain the service: authentication, profiles, content posting, community features.
  • Improve and secure the service: troubleshooting, preventing abuse, aggregate analytics.
  • Communication: service notices (e.g., critical changes, policy updates).
  • Legal: comply with law, enforce terms, protect users and the service.
  • Contract: operating your account, profiles, and user content.
  • Legitimate interests: service operation, security, and basic service logs.
  • Consent: analytics cookies/identifiers where required (e.g., EU/UK).

5. Cookies & Analytics

  • Necessary cookies/local storage: used for authentication and UI preferences.
  • Analytics: GA4 (property ID G-RY054MZKZ2).
    • EU/UK users: we use Consent Mode. Analytics is disabled until consent is provided.
    • You can change or withdraw consent anytime via your browser or by clearing site data.
  • No third‑party ad/retargeting pixels. Some posts embed YouTube videos via YouTube’s privacy-enhanced player (youtube-nocookie.com). Paddle review thumbnails load from YouTube before playback, sharing connection information such as your IP address with Google. On paddle pages, the player loads only when you choose Load video, and playback never starts automatically. Privacy-enhanced mode limits personalization; it does not prevent all third-party processing. See Google’s Privacy Policy and YouTube’s Terms of Service .

6. Data Sharing

  • Service providers: Google (Firebase Auth, Firestore, Storage; Google Cloud; GA4).
  • No sale of personal data. We share data only with providers necessary to operate the service or where required by law.

7. Data Storage and Transfers

  • Primary storage: us-central1 (USA). Data may be processed in other regions by Google’s infrastructure.
  • We rely on appropriate safeguards for international transfers as provided by our processors.

8. Moderation

  • We may use automated tools to assist moderation, with human review where needed.
  • Moderation action logs are retained only while a moderation workflow is in progress, then discarded.

9. Retention and Deletion

  • Account deletion: on verified request, we delete account data within 30 days.
  • Public content (UGC): by default anonymized (e.g., remove profile linkage) so threads and community context remain intact. You may delete your own posts where the UI allows.
  • Backups/logs: retained for a limited period for security and integrity, then purged.

10. Your Rights

  • Depending on your location (including EU/UK and California), you may have rights to access, correct, delete, port, restrict/opt out of certain processing, and to withdraw analytics consent.
  • California: we do not “sell” or “share” personal information as defined by the CPRA.
  • Requests: email gpts-privacy@proton.me from your account email. We may need to verify your identity.

11. Your Choices

  • Public profile/content: anything you publish may be visible to others. You can remove your posts where supported; otherwise request assistance.
  • Analytics cookies (EU/UK): use the cookie banner to accept/decline. If no banner is shown, analytics may be disabled by default in your region.

12. Children’s Privacy

  • The service is not intended for children under 13. If you believe a child under 13 has provided personal data, contact us and we will take appropriate action.

13. Security

  • We use industry‑standard measures including encryption in transit and at rest (via Firebase/Google Cloud), access controls, and monitoring to protect data. No method is 100% secure.

14. Changes to This Policy

  • We may update this policy from time to time. We’ll post the updated date here and, for material changes, provide a notice in the app or on the blog.

15. Contact