Privacy

Alpha Applications And Surveys

When someone begins an InkVein Alpha application, InkVein may collect their email before they choose whether to complete the optional follow-up survey. Submitting an application creates an applicant record but does not itself create an Alpha account or make the applicant an Alpha participant.

Applicant information may include email address, confirmation that the applicant is 18 or older, confirmation that the applicant is located in California, optional survey answers, creative discipline, intended platform, intended InkVein uses or goals, discovery source, willingness to provide Alpha feedback, survey completion state, marketing preference, and Alpha application or lifecycle status.

Lifecycle states may include applied, reviewing, waitlisted, accepted, invited, redeemed, declined, or similar operational states needed to administer Alpha. Survey completion is optional, applicants may still be considered without completing it, and Discord is optional.

The Alpha survey does not ask for date of birth or precise GPS location.

How We Use Information

• To receive and review Alpha applications.
• To confirm Alpha eligibility requirements, including age 18+ and California-only participation.
• To understand the early creative community and improve the Alpha.
• To send operational Alpha messages such as signup confirmation, status, invitations, access information, and testing instructions.
• To send optional community or marketing messages only when separately consented to.
• To respond to support, privacy, security, abuse, or legal requests.

Applicant System And Email Processing

InkVein Core and Supabase-backed applicant records are the authoritative system for Alpha applicant information and lifecycle state. Loops may be used as an email-delivery and Alpha lifecycle communications service provider acting on InkVein's behalf. InkVein may provide Loops with bounded applicant or contact information needed for application-related operational email, Alpha lifecycle communication, and optional marketing communication where separately consented. This may include email address, applicant or contact identifier, Alpha/application status, survey-completed state, marketing opt-in state, platform, craft, and source metadata required for the integration. Detailed survey answers such as intended InkVein uses or goals, discovery source, and willingness to provide Alpha feedback remain Core/Supabase-only and are not routinely shared with Loops. Loops is not InkVein's authoritative applicant database.

Operational And Optional Email

Operational Alpha email is separate from optional marketing consent. Operational or administrative messages may include signup or application confirmation, review or waitlist status, invitations, access information, security notices, policy notices, and support responses.

Marketing messages may include product news, announcements, launch information, and promotional updates. Marketing consent is optional. Withdrawing marketing consent does not itself cancel an Alpha application, prevent necessary application communications, or cancel an existing Alpha account.

Service Providers

• Supabase and InkVein Core may support authentication, database, storage, and applicant records where applicable.
• Loops may support email delivery and Alpha lifecycle communications, but is not the authoritative applicant database.
• Discord may support optional connection or authentication where the user chooses it.
• PostHog may support product analytics where enabled.
• Sentry may support diagnostics and error monitoring where enabled.
• Railway may support hosted backend or API infrastructure where used.

Tracking And Browser Signals

Traditional browser Do Not Track signals do not have a single universally adopted technical standard, and InkVein does not currently change behavior solely in response to traditional DNT. InkVein does not currently sell personal information or share it for cross-context behavioral advertising. Third-party providers may process technical or usage information as necessary to provide their services. Where applicable law requires recognition of a legally operative privacy preference signal, InkVein will comply as required.

Retention And Requests

Alpha application records may be retained for as long as reasonably necessary to administer the Alpha, maintain application history, prevent duplicate or abusive applications, handle invitations and access, resolve disputes, and satisfy security or legal obligations. Information that is no longer reasonably needed may be deleted or de-identified.

InkVein account holders can permanently delete their account in the app. The deletion flow provides a one-time receipt before sign-out. InkVein stores only its digest, along with keyed verification values rather than plaintext former username or email. People who cannot sign in can use the public account deletion resource or contact support@inkvein.app. InkVein may verify the requester.

Deletion removes the live account and eligible personal data from normal product surfaces. Limited restricted information may remain where reasonably necessary or permitted for security, fraud prevention, legal obligations, moderation or audit history, disputes, attribution, provenance, unsubscribe state, suppression state, or backup integrity. Backups and provider systems may age out on their normal restricted schedules rather than instantly. A separately selected marketing subscription may remain after account deletion; it is not part of the deleted account and remains subject to normal unsubscribe or removal controls.

At the end of Alpha, keeping an account for Beta requires an explicit, timestamped choice. Non-response is not treated as affirmative Beta retention consent.

Creative Content

Creators retain ownership of their underlying creative work. InkVein receives only the operational license needed to host, display, and provide the service. Alpha creative content is not used for generative-AI training without separate affirmative permission.

After Group disband, detached content, attribution, contributor provenance, moderation evidence, and platform-integrity records may be preserved where reasonably necessary under the existing operational license and retention rules. Disband does not make private Group records public. Privacy and removal requests remain available through Support.

Assets, Shared Work, And Deleted Creators

Personal, unshared Assets are normally deleted with the creator's account when no legitimate restricted retention applies. A Group-shared or collaborative Asset may remain where an active collaboration, issued Artifact, or historical record legitimately depends on it. The live creator profile is removed, restricted provenance may reference a deleted-subject identifier, and ordinary product surfaces use neutral attribution such as “Deleted creator.”

Shared retention does not transfer copyright or other creator rights to InkVein or a Group, expand InkVein's operational license, or authorize generative-AI training. A former creator or other rightsholder may contact Support about removal. Independent rights claims do not require an active account or deletion receipt, and disputed collaborative claims may require human review.