Privacy Policy

1. Information We Collect

• Account & Authentication Information: When you sign up or log in (via email magic links, GitHub, or Google OAuth), we collect your name, email address, username, and authentication identifiers.
• Company Billing & Support: Company billing records include the company name, supplied tax identifier, and billing address. Checkout receipts retain a billing snapshot. Support requests include the account identifier, role, selected category, message, application route, and browser/OS user-agent context to investigate your request.
• Public Launch Circle: Developer updates explicitly marked public, their author usernames, and visible comments are accessible without signing in. Older members-only updates remain restricted unless made public through an explicit publishing choice. Do not include confidential builds, credentials, or personal data in public discussions.
• Profiles, Connections & Messages: Developer and tester profiles show your chosen handle, avatar, biography, links, join date, follow counts, aggregate platform statistics and visible Launch Circle activity. They do not show your email, wallet, private proof files or direct messages. We store follow relationships, per-developer email choices, message requests, conversation messages and blocks to provide member connections. Direct messages are accessible to their participants; reporting a conversation shares a disclosed recent excerpt with authorized SeedEnv support reviewers. Messages are not end-to-end encrypted. Members-only Launch Circle activity remains restricted to signed-in members.
• Developers: Organization details, project URLs, test build files/links, campaign specifications, and payout/funding preferences.
• Testers: Device specifications, operating system versions, testing hardware profiles, and feedback submissions.
• Test Submissions & Proof Files: Files uploaded to verify completed tasks, including bug reports, crash logs, system diagnostics, feedback notes, screenshots, and screen recordings.
• Clippers & Connected Social Accounts: Creator biographies, portfolio and social profile URLs, campaign room messages, private video versions, publication evidence, agreement terms, and payment references. With your authorization, TikTok provides your account identifier, display name, and selected public-video metadata. Access and refresh tokens are encrypted at rest using a dedicated application key and are never shared with other members.
• Payment & Transaction Details: Payment processing, campaign escrow, and tester reward payouts are handled by third-party payment processors (such as Stripe). We do not store complete credit card numbers or banking account credentials directly on our servers; we retain only reference transaction tokens, payout status, and invoice histories.
• Automated Technical Data: IP addresses, browser type, device identifiers, session timestamps, and interaction events recorded via server logs and privacy-preserving analytics.
• Cohort Brief Clicks: When you click a public cohort brief, we store its cohort identifier, timestamp and a daily hashed visitor key, not your raw account ID or IP address. A cohort's developer sees only the aggregate count, deduplicated per visitor per UTC day. Signed-in owners, bots, local previews and analytics opt-outs are excluded. No tracking is triggered by prefetching or simply refreshing a brief.

2. How We Use Your Information

• Creating and managing your user account and role settings (Developer vs. Tester).
• Facilitating beta campaigns, distributing test instructions, and delivering tester proof files to developers for review.
• Managing campaign rewards, bounties, and escrow disbursement via our payment partners.
• Detecting, preventing, and mitigating fraudulent behavior, bot registrations, duplicate accounts, and invalid submission proofs.
• Sending essential service communications, such as authentication links, campaign updates, submission approvals, and security alerts.
• Sending opt-in email updates about developers you follow when they launch a cohort or publish in Launch Circle. Tester follows do not send emails. You can disable emails per developer or unfollow in Account Connections, and disable new message requests or block members in Message privacy.

3. How We Share Your Information

• Between Developers and Testers: When a tester submits proof of completion for a campaign, the associated developer receives access to the submitted feedback, uploaded proof files, screenshots/recordings, and tester platform username to verify campaign completion.
• Clippers Rooms & Reviews: Creator applicants share their background and linked samples with the campaign developer. Invited creators and the developer share campaign-room messages and developer reference assets. Each creator's drafts and publication evidence are accessible only to that creator, the developer, and authorized administrators, through short-lived private asset links. Administrators can review agreement disputes.
• Cloud Storage: Secure hosting for uploaded tester proof files, screenshots, and campaign assets.
• Authentication & Email: Providers delivering transactional emails and secure magic-link sign-ins.
• Payment & Escrow Processors: Stripe for processing developer campaign deposits and tester reward payouts.
• AI Support Assistant: When you use "Ask AI" in the help panel, your messages, the page you are on and, if you are signed in, the account details the assistant looks up to answer (such as balance, cohort or payout status) are sent to Google's Gemini API to generate a reply. We use Google's paid service, under which Google does not use this content to train its models. Chats are not stored by SeedEnv unless you send them to our team as a support ticket.
• AI Submission Review: When a tester submits proof, the written report, device details, crash-log excerpt, screenshot and (up to 18 MB) screen recording are sent to Google's Gemini API to score completeness, spot duplicates and check that the media matches the report. Developers use the AI drafting tool by sending their app description and release notes. We use Google's paid service, under which Google does not use this content to train its models. The result is advisory: a person makes every approval or rejection decision. The assistant may ask a tester once for missing details, and a flagged proof waits for human review instead of being approved automatically.
• Hosting & Analytics: Cloud infrastructure hosts and monitoring services.
• Legal Requirements: We may disclose information if required by law, regulation, subpoena, or legal process, or to protect the vital interests, safety, and integrity of SeedEnv and its users.

4. Data Security & Storage

5. Your Rights & Choices

• Access & Portability: Requesting a copy of the personal data we hold about you.
• Correction: Updating or amending inaccurate personal details through your account settings.
• Deletion: Requesting the deletion of your account and personal data, subject to legal or transactional retention obligations (e.g., historical tax or payment records).
• Communication Preferences: Opting out of non-essential campaign notifications.
• Connected Social Access: Disconnect TikTok in the Clippers workspace to revoke authorization and remove locally stored encrypted tokens. You may also revoke access in TikTok's account settings. Disconnecting does not delete existing contracts, paid-content obligations, or financial records required for disputes and legal compliance.

6. Cookies & Local Storage

• Authentication (strictly necessary): next-auth.session-token, next-auth.csrf-token, and next-auth.callback-url (prefixed with __Secure- or __Host- over HTTPS) keep you signed in, protect forms against cross-site request forgery, and return you to the right page after sign-in. They expire when you sign out or when your session ends.
• Analytics opt-out (functional): seedenv_analytics_optout remembers that a browser has opted out of, or is excluded from, our self-hosted, privacy-preserving visit counts. It lasts up to two years.
• Connected social sign-in (strictly necessary): clip-tiktok-state is a short-lived security value used only while you connect a TikTok account in Clippers. It expires after 10 minutes.
• Browser storage: Session storage holds a random, non-identifying visit identifier used to de-duplicate page-view counts for the current tab. Local storage may hold workspace preferences you set in the developer console. Neither is shared with third parties.
• Your choices: You can block or delete cookies in your browser settings. Blocking strictly necessary cookies will prevent you from signing in.

7. Third-Party Links & External Software

8. Children's Privacy

9. Contact Us

If you have questions, concerns, or requests regarding this Privacy Policy or your personal information, please contact us:

Email: terimus@seedenv.com