Larply

Privacy Policy

Last updated: October 15, 2026

SEA & SEA LLC (“Larply,” “we,” “us,” or “our”) operates the Larply app. This policy describes information processed through Larply and the choices available to you. Larply is for people who are at least 18 years old, or the age of majority where they live if higher.

Information we process

  • Account information: the Sign in with Apple and Clerk identifiers, the Larply account identifier, and account details Apple makes available through your sign-in choice.
  • Creation materials: the video and reference images you choose, your written prompt, rights and AI-processing confirmations, and the generated video.
  • Purchase and credit records: Apple and Superwall transaction or subscription evidence, your Larply credit balance and credit activity. Larply does not receive your full payment-card number from Apple.
  • Service records: quote and job state, media format and duration, selected delivery setting, error and support details, and records needed to prevent duplicate credits or provider requests.

How Larply uses information

Larply uses this information to authenticate you, protect your private media, calculate a server-authoritative quote, process the larp you request, deliver the result, handle purchases and restores, prevent abuse and duplicate charges, provide support, and operate and secure the service. Larply itself does not use your video, references, prompt, or result for advertising or cross-service tracking.

When information leaves your device

Browsing and composing an edit while signed out stay local. When you authenticate and choose to generate, the selected media, prompt, and any references are uploaded to Larply’s private backend and storage. Larply sends the materials needed for the requested edit to Higgsfield, including any AI-model or compute providers Higgsfield uses. You must give affirmative permission at the app’s processing-consent step before that upload.

Higgsfield processing, moderation, and training

Higgsfield is Larply’s downstream video-generation provider. Under Higgsfield’s standard Terms of Use and Privacy Policy, submitted Inputs and generated Outputs may be processed to provide the service, for safety and moderation, and to train, develop, enhance, evolve, and improve Higgsfield’s and its affiliates’ AI models, algorithms, products, and services. Higgsfield states that deleting content stops future training, but material already incorporated into trained models cannot feasibly be removed from those models. Private content is not used by Higgsfield for marketing without consent or the user making it public. Larply has no documented Enterprise or no-training addendum in this release package.

Higgsfield’s Trust policy says moderation is applied at the model level: models scan prompts, reference images, and outputs using model-specific filtering, so policies can vary. Its Help Center describes filters during prompt processing and image upload or reference input, plus separate safety systems operated by external model providers. Either system can produce false positives. These public materials do not confirm the exact filter coverage for every API route Larply may use; filtering does not replace Larply’s consent, rights, age, or prohibited-use rules.

Service providers

Larply uses Apple for sign-in and App Store purchases; Clerk for authentication; Convex for backend data and job processing; Cloudflare R2 for private media storage; Higgsfield for video generation; OpenAI for text-only edit classification and instruction refinement in supported versions; Expo and Apple Push Notification service for requested notifications; Mixpanel for optional usage analytics; and Superwall for purchase presentation and transaction events. Each provider receives information needed for its role and may process it under its own terms and in locations outside your region.

Superwall’s SDK also receives app and paywall interaction events, including purchase events, for paywall analytics and reporting. Its device and audience attributes may include a vendor device identifier, device model and locale, an approximate city or region derived from the network address, and usage measures such as time since install and paywall views. Larply does not request precise location permission for this. After sign-in, Larply identifies the account to Superwall with its server-generated appAccountToken UUID, so later events and attributes can be linked to your Larply account. Larply does not use these data for targeted advertising or advertising measurement and does not share them with data brokers.

Text processing and optional training

In supported app versions, OpenAI receives text-only edit context: your prompt, the reference count, and the permitted editing approaches. Larply excludes videos, photos, audio, media URLs, and attachments from this text route. Text may contain personal information. Declining optional text training uses a separate OpenAI project with training sharing disabled. Only an explicit training opt-in, when that route is approved, selects the sharing-enabled project. You can withdraw future AI-processing permission in Settings → AI processing permissions; withdrawal does not recall material already processed. See OpenAI’s API data policies.

Analytics and first-party measurement

Optional usage analytics in Mixpanel is off unless you opt in. It measures app interactions and pseudonymous account or installation identifiers, never your videos, photos, audio, or prompts. Change your choice in Settings → Help & privacy → Share usage analytics. Declining does not affect access, purchases, or rewards.

Separately, Larply keeps minimal first-party paywall exposure records in Convex, including for people who decline Mixpanel. These record a pseudonymous checkout/account identifier, offer assignment, and exposure time to calculate subscription retention and realized service economics. Purchase, credit-settlement, and provider-cost records support that accounting. These records contain no prompts or media and are not sent as individual usage tracking to Mixpanel for people who decline. Superwall’s purchase and paywall reporting is separate from this optional Mixpanel choice.

Notifications

If you allow notifications, Larply stores an installation identifier, push token, and project identifier to deliver generation-status updates and earned referral rewards through Expo and Apple. Lock-screen messages exclude your media and prompts. Promotional Premium Preview reminders require a separate opt-in, off by default, in Settings → Help & privacy → Premium Preview reminders. Turn that off at any time to stop future reminders; the in-app Preview offer remains available if eligible. iPhone notification settings control all system alerts.

Storage and deletion

Larply keeps account, billing, and creation records while needed to operate the service, deliver creations, prevent duplicate fulfillment, resolve support issues, or meet legal obligations. Delete Account is available in Settings. If a generation is still active or requires reconciliation, Larply asks you to wait or contact support; once accepted, the request locks new work, deletes account-linked data and private media, and signs you out. Limited owner-free hashes of transaction and redemption identifiers may remain to prevent duplicate credits or satisfy applicable obligations. Provider retention follows the applicable provider terms. Deleting a Larply account does not cancel an Apple subscription; manage that separately in Apple’s subscription settings.

Your choices

You choose which media to select and whether to generate. You can stop before upload, deny photo-library access, withdraw before sending materials, sign out, and request deletion in Settings. After deletion, iOS provides the separate option to remove Larply from Sign in with Apple under your Apple Account settings. Contact us for access, correction, privacy, safety, rights, or deletion questions.

Contact and updates

Operator: SEA & SEA LLC

Contact: info@sea-and-sea.com

We will update this policy when our practices or providers change and will show the effective date on the current version.