How Unicornia handles trust, data and privacy.

Unicornia is a startup community operating system for founders, builders, students, freelancers and startup teams. The product includes founder dashboards, startup discovery, funding flows, marketplace workflows, team collaboration, GitHub-backed workspace features, feedback, mail, wallet/UNIC experiences and admin tooling.

This Privacy Policy explains how Unicornia may collect, use, store, protect and share information when users visit unicornia.club, create an account, connect OAuth providers, register a startup, participate in marketplace work, use funding flows, submit proofs, join teams or use wallet and collaboration features.

Account information includes name, email address, password credentials where applicable, role selection, startup name, referral identifiers and profile fields entered during signup or profile updates.

Startup information may include startup name, founder information, team membership, valuation inputs, workspace metadata, tasks, salary requests, marketplace requirements, pitch submissions, Serve Unicornia quest submissions, internal messages and settings.

User-generated content may include proposals, bids, feedback, reviews, proof links, GitHub file drafts, comments, mailbox messages, room messages, meeting details and any content submitted through forms or APIs.

Unicornia supports OAuth-based authentication through providers such as GitHub and Google. When a user chooses one provider, Unicornia receives profile data made available by that provider, such as email, name, username, avatar/profile metadata and provider identifiers.

Only one trusted provider is required for authentication. Users do not need to connect both Google and GitHub to create an account. GitHub may still be requested later for workspace-specific repository features where repo permissions are needed.

OAuth data is used to authenticate the user, prefill profile details, reduce duplicate identity checks, connect proof-of-work signals and keep the registration flow consistent across founders, builders and students.

Unicornia funding features may involve Reserve Bank requests, Razorpay-backed top-ups, provider order identifiers, payment identifiers, webhook event records, verification status, funding request details, valuation-related fields and treasury movement history.

Unicornia does not need to store full card numbers or sensitive payment credentials. Payment providers process payment details under their own terms. Unicornia stores the transaction references required to verify, reconcile, approve and audit the funding workflow.

Funding data is used for treasury crediting, UNIC top-up verification, valuation calculations, release approvals, fraud prevention, accounting review, support and compliance-oriented audit trails.

UNIC is Unicornia’s internal operating unit for startup treasury credits, rewards, reserved budgets and approved payouts. Wallet-related information may include balances, reserved balances, transaction history, UPI-style handles, transfer references, payout descriptions and scope of transfer.

Wallet and ledger data is used to show balances, reserve budgets, release approved payouts, prevent duplicate transfers, debug transaction issues and maintain a trustworthy record of treasury movement.

Some wallet events are intentionally retained for auditability because deleting or altering ledger history could make funding, payout and reward activity unreliable.

Workspace data may include repository connection metadata, branch names, file paths, workspace files, permissions, commit records, draft content, team member access and founder/member review status.

When GitHub workspace features are used, repository-related data is processed to browse branches/files, grant file-level permissions, save drafts, review changes and support founder-controlled commits. Access is limited to the scopes and permissions granted by the user or founder.

Collaboration data such as team rooms, meetings, mail, messages and task updates is used to coordinate work, preserve decision context, support accountability and help founders understand who contributed what.

Marketplace data may include services, applications, proposals, bids, accepted work, submitted proofs, review status, payout decisions and founder feedback.

Student track data may include internship-oriented tasks, completion proof, certificate metadata, portfolio evidence, GitHub links, role history and founder-approved outcomes.

This data helps Unicornia provide talent discovery, proof-of-work histories, certificate experiences, marketplace matching, trust signals, offer flows and payout approvals.

Unicornia may collect technical information such as device type, browser, approximate region, IP-derived security signals, pages visited, timestamps, referring URLs, session events, API response status and error logs.

Cookies and local/session storage may be used for authentication sessions, security, preferences, referral flows, OAuth redirects and product analytics. Users can control cookies through browser settings, but disabling them may break login or workspace behavior.

Operational logs are used to diagnose broken APIs, improve reliability, secure accounts, detect abuse, understand performance and support product decisions.

We use information to create accounts, authenticate users, route founders and individuals to the correct dashboard, create startup profiles, support referrals, initialize wallets, power marketplace applications and run workspace/collaboration features.

We also use data to verify top-ups, approve submissions, release payouts, generate certificate-like proof, personalize product UI, respond to support requests, send service messages, improve security and keep the platform reliable.

We do not sell personal information. If advertising or third-party analytics are introduced later, this policy should be updated with the relevant providers and controls.

Unicornia may share limited data with infrastructure, authentication, database, hosting, payment, email, analytics, support and security providers only as needed to operate the product.

Examples of processors may include Supabase for authentication/database services, Razorpay for payment processing, GitHub or Google for OAuth/workspace-related features and hosting or deployment providers for serving the application.

Data may also be shared when required by law, to protect users or the platform, to investigate abuse, to enforce terms or during a business transfer such as merger, acquisition or restructuring.

Account and profile data is generally kept while an account is active. Users may request deletion or correction, subject to legal, security, accounting and audit limitations.

Wallet, funding, ledger, payout, top-up, webhook and marketplace approval records may be retained longer because they are needed for auditability, dispute resolution, fraud prevention and financial reconciliation.

Operational logs may be retained for a limited period based on security, debugging and compliance needs. Backup copies may persist for a reasonable period before being deleted or overwritten.

Unicornia uses technical and organizational safeguards such as authentication sessions, authorization checks, role-based flows, database security policies, server-side validation and limited service-role access for sensitive operations.

No online system is perfectly secure. Users should protect account credentials, use trusted OAuth accounts, avoid sharing sensitive secrets in messages or workspace files and report suspicious activity promptly.

Sensitive payment details are processed by payment providers rather than stored directly by Unicornia whenever possible.

Depending on location, users may have rights to access, correct, export, restrict or delete personal information. Some requests may require identity verification before processing.

Users can manage OAuth access from the connected provider account settings, update profile information inside Unicornia where available and request help for account or data issues.

Some records cannot be fully removed immediately if they are required for security, audit, payment reconciliation, legal compliance or dispute resolution.

Unicornia is intended for users who can lawfully use startup, marketplace, payment and collaboration features. If minors use student-oriented features, they should do so only where permitted by applicable law and with required consent or supervision.

Student certificates and proof-of-work features should not include unnecessary sensitive personal data. Users should avoid uploading government IDs, private financial details or unrelated sensitive documents unless explicitly requested by an official workflow.

Unicornia may update this Privacy Policy as the product evolves. Material changes should be reflected by updating the effective date and, where appropriate, notifying users inside the product or through email.

Continued use of Unicornia after updates means users accept the revised policy to the extent permitted by applicable law.

For privacy questions, account requests, data access requests or deletion requests, users can contact Unicornia through the official support channel listed on the website or product dashboard.

Recommended contact email for production: privacy@unicornia.club. Replace this with the final monitored privacy inbox before public launch if a different address is preferred.