About this draft
This draft describes Regenerator by GreenPill TO’s current implementation. The operator’s legal entity, privacy contact and jurisdiction remain pending. Retention schedules, rights-request procedures and transfer details must be finalized before production.
Information we handle
We store Cubid app-scoped identity identifiers and a hash of the verified email supplied for identity resolution. We store a preferred name, private Telegram/email/phone contact details, project details, site URLs, project stage, audience estimate, categories, private onboarding progress, site verification evidence, founder-score observations, terms/privacy acceptance versions and timestamps, an optional newsletters and application-reminders choice with its consent timestamp, membership/billing references, and audit events.
Why we use it
We use identity and private application data to secure account access, confirm authority, review project readiness, apply founder eligibility, administer membership, manage sandbox billing and maintain an accountable record. Score checks and eligibility are performed on the server; another manager’s score does not replace the applying founder’s eligibility.
What becomes public
The directory publishes approved project names, descriptions, URLs, category information and membership labels. Optional applicant listings require separate consent and verification. Your preferred name, contact details, monthly audience estimate, onboarding answers, acceptance records and identity identifiers are not part of the public directory. During an outage, clearly labelled static inaugural cards may appear; they are not evidence of approved membership.
Service providers
Cubid manages passkeys, identity disclosure and recovery. Stripe manages hosted sandbox checkout and subscription management; Regenerator stores billing references and verified events rather than card details. PostgreSQL/Supabase stores application data. Vercel hosts this deployment and may process request and operational logs. SnapVote hosts member ballots; this release stores links, not voting results. External project links lead to websites with their own privacy practices.
Browser storage and security
Real sessions use a secure server-managed cookie on HTTPS and expire after eight hours. Private operations enforce ownership and administrator permissions. Local and preview fictional demos use browser storage only; restarting clears the demo state. Demo storage never grants real server authority. Fonts may load from Google Fonts, which receives requests when those resources load.
Retention and your choices
You can choose whether an eligible applicant profile is published. Existing workspace controls allow changing that preference. Approved member directory inclusion follows the membership terms. You can also separately choose whether to receive newsletters and application reminders; the choice defaults off and this release does not send them. You may contact a project maintainer through an existing GreenPill channel while a dedicated privacy contact is pending. We have not yet finalized retention periods or automated access/deletion/export procedures; no specific deadline or completed privacy certification is claimed.