Dexta

Legal

Privacy policy

This policy explains what Dexta collects, why we collect it, and which processors see it. Dexta stores your logo files privately and uses OpenRouter for AI steps. Logo paths are not diffused into new artwork. Paddle is merchant of record for Pro payments.

Last updated August 27, 2026

1. Who we are

Dexta is the logo-motion studio at dexta.art and www.dexta.art. We have not published a separate company legal name on this site, so this policy refers to the service as Dexta.

Questions: noreply@dexta.art.

2. Information we collect

We collect only what we need to run accounts, generate motion, store files, and bill Pro.

Account and authentication

  • Email address and password (hashed) when you register with email.
  • Google account identifiers if you choose Continue with Google (name, email, and Google subject ID supplied by Google OAuth).
  • Phone number if you choose phone sign-in. The number is normalized and stored as a hashed synthetic login identifier. Phone sign-in is not SMS-verified.
  • Guest (anonymous) session identifiers until you link a full account. Eligible projects, credits, and exports can move with that link.
  • Email verification status. Transactional verification messages are sent from noreply@dexta.art when Resend is configured.
  • Session tokens managed by Better Auth, including HttpOnly cookies used to keep you signed in.
  • Hashed MCP personal tokens (the secret is shown once and is not stored in plaintext). Tokens can be revoked in workspace settings.

Studio content

  • Uploaded logos (SVG, PNG, JPEG, up to 10 MB) and derived SVG after sanitization or vectorization.
  • Parsed structure: layer IDs and names, viewBox, palette, and related metadata. This stays with the project. Listed Library clips also show the prompt and video.
  • Written motion prompts, taste dials, MotionSpec JSON, QA reports, Lottie JSON, and export files (Lottie, SVG, GIF, MP4).
  • If a clip is listed on the Library: the video, first-frame poster, written prompt, and your first name. Project names, emails, and files that are not listed stay private. Free finished clips are listed; Pro can keep them off the Library.
  • Credit ledger entries, generation and export job status, and billing plan (Free or Pro).

Billing

  • Dexta does not store full card numbers. Paddle processes Pro checkout and stores payment instruments as merchant of record.
  • We store Paddle customer, subscription, checkout, and invoice identifiers, plan status, renewal or end dates, and amounts from signed webhooks so we can grant credits and show receipts in the app.

Technical data

  • IP address, user agent, and coarse request metadata used for security, rate limits, and logs. Logs are configured to avoid persisting cookie headers.
  • Hashed device signals (screen size, timezone, CPU cores, platform, and GPU renderer when the browser exposes it) used only to limit one free starter allotment per device. Browser chrome such as available window size is not used for that match.
  • Theme preference in localStorage (dexta-theme) so the canvas stays light or dark on your device.

3. How we use information

  • Provide the studio: ingest logos, generate motion, preview, export, and restore workspaces.
  • Authenticate you, prevent abuse, and enforce credit and export limits, including one free starter allotment per device.
  • Grant Pro after Paddle confirms payment, and downgrade after cancellation, expiry, or refund.
  • Send essential account mail such as email verification. We do not sell your data or use your logos to train a public generative video model.
  • Show Free-plan clips on the public Library when they finish generating. Pro can keep new work private and share a clip only when you choose. Guest workspaces stay unlisted.
  • Improve reliability (failed-job recovery, QA) using job metadata and structured specs.

4. AI processing (OpenRouter)

All AI features go through OpenRouter. That is the only AI gateway Dexta uses.

OpenRouter and the models behind a given call are independent processors. Their retention and training practices are governed by their own policies. Do not upload a mark you cannot allow those processors to see for the purpose of producing your motion files.

  • Raster plates: PNG/JPEG bytes are stored privately and rendered as image layers. They are not sent to a tracing or diffusion model.
  • Brand analysis, MotionSpec generation, and QA critique: language models receive a structure summary and/or the MotionSpec JSON, plus your prompt. System instructions forbid outputting SVG paths, replacement geometry, or recolored marks.
  • Locked vector paths used for rendering stay in Dexta’s pipeline and renderer. They are not passed through a diffusion model to synthesize logo video.

5. Storage

Logo originals, derived SVG, and export artifacts are stored in private S3-compatible object storage (production S3 or R2; local MinIO in development). Objects are not meant to be publicly listed.

Published Library clips are streamed through a public media route that only serves generations marked public. Unpublishing or a founder removal from the Library stops new public access; cached copies may remain briefly. Removed clips stay in the maker’s studio.

Account, project, generation, credit, device-grant, and billing records are stored in PostgreSQL.

When you delete your account, Dexta deletes stored logo and export objects it still holds for that workspace, along with the authentication user—after any active subscription has been cancelled.

6. Cookies, sessions, and similar technologies

Dexta uses cookies that are required to run the product, not a third-party advertising pixel wall. Blocking all cookies will prevent sign-in.

  • Better Auth session cookies (via the Next.js cookie helper) to keep you signed in and to support guest upgrade.
  • dexta_did, an HttpOnly first-party cookie (about 400 days) that identifies this browser for free-tier abuse prevention. It is not an advertising tracker.
  • CSRF and OAuth state cookies during Google sign-in when Google OAuth is enabled.
  • localStorage key dexta-theme for appearance only.

7. Who else receives data

  • Anyone who visits the public Library can watch listed clips, copy their prompts, and see your first name. Free-plan finished clips are listed. Pro can keep clips off the Library.
  • OpenRouter (and the routed language models) for brand analysis, MotionSpec generation, and QA critique.
  • Paddle for Pro checkout, tax, invoices, customer portal, and refunds. Paddle is merchant of record for those payments.
  • The S3-compatible storage provider that hosts private objects.
  • Resend, when email delivery is live, to send verification messages from noreply@dexta.art.
  • Hosting and database providers that run the application and PostgreSQL.
  • We share data if required by law, to prevent fraud or abuse, or as part of a transfer of the service, with this policy still applying to the transferred records.

8. Retention

We keep account and project data while the workspace exists. Credit ledger and billing webhook history are kept as needed to reconcile entitlements, prevent double-grants, and handle refunds.

You can delete the workspace from billing settings after cancelling Pro. Stale in-progress jobs may be cleaned up automatically so reserved credits can be returned.

9. Your choices and rights

Depending on where you live, you may have rights to access, correct, delete, or export personal data, or to object to certain processing. Email noreply@dexta.art from the address on the account and describe the request.

You can disconnect Google access in your Google account settings. You can cancel Pro in the Paddle portal. Pro can unpublish a Library clip from the studio. You can delete the Dexta workspace in-product once no active subscription remains.

10. Children and international use

Dexta is built for professional design work. It is not directed at children under 16, and we do not knowingly collect their data.

Servers, OpenRouter, Paddle, and object storage may process data in the United States or other countries where those providers operate. If you use Dexta from elsewhere, you understand that transfer is required to provide the studio.

11. Changes and contact

We will post updates here with a new effective date. The current version is dated August 23, 2026.

Dexta — www.dexta.art — noreply@dexta.art.

Related: Terms of service · Refund policy.

Privacy policy — Dexta — Dexta