TX-IN AI Campaign Studio · TX-IN Digital & Design

Privacy Policy

Last updated: September 7, 2026

This policy describes information handling for TX-IN AI Campaign Studio by TX-IN Digital & Design. Contact support@tx-indigitaldesign.com with privacy questions.

Information used by the studio

Account information includes your email, account identifier, confirmation status, and authentication state. Supabase Auth handles password authentication. Campaign information includes briefs, brand and audience details, other submitted content, saved campaigns, and generated text and images. Usage records include quotas, counters, and generation attempts. Billing records include Stripe customer, subscription and price identifiers, subscription status, period dates, and cancellation state.

Service and security records can include request times, routes, response status, request identifiers, and technical connection information processed by providers. Support email contains the contact details and information you choose to send.

Service providers

• Supabase: authentication, account and campaign database records, generated-image storage, usage accounting, and billing state.
• OpenAI: campaign briefs and instructions for text generation, and art-direction prompts for image generation. The app does not deliberately include account email or billing details in these requests, but information entered in a brief may be sent with that brief.
• Stripe: hosted checkout and subscription management, details entered directly with Stripe, and account references needed to associate subscriptions with studio users. Campaign briefs are not part of the billing integration. The studio does not store complete payment-card details.
• Vercel: hosting and server execution, including processing requests and responses and hosting service logs.
• Upstash Redis: rate-limit counters, time windows, and authenticated user identifiers. The limiter does not store briefs, passwords, or payment details.
• hCaptcha: bot-protection challenges and related browser, connection, and interaction signals. Supabase receives the challenge token to verify protected authentication requests. See hCaptcha privacy information.
• Resend: transactional authentication email through Supabase SMTP, including recipient addresses and authentication email content.

Browser storage and cookies

The studio uses local storage for local campaigns and Supabase authentication sessions. Signing in can import local campaigns into your cloud account. Signing out does not erase all local campaign data. Clearing browser storage may remove local drafts and sign-in state. hCaptcha and hosted provider pages may use their own cookies or storage for their services. The studio currently has no application analytics or advertising-tracking integration.

Retention, choices, and security

Saved campaigns remain available until removed through the app or other account handling. Deleting a campaign does not mean usage history, billing records, provider logs, or backups are immediately erased. Fixed retention and backup-deletion schedules are not specified here. Contact support about access, correction, or deletion requests; requests may require identity verification and consideration of applicable obligations and technical limits. We do not promise immediate or complete deletion from every system.

Account-scoped access controls protect cloud records, but no online service can promise absolute security. Submit only content you are authorized to share and avoid unnecessary sensitive information.

Policy updates

Updates will appear here with a revised date. This policy makes no claim of a particular certification, data-residency location, or jurisdiction-specific entitlement.