Privacy policy

Effective September 6, 2026

Redux is operated by Alex Rowan. Contact alex@tryredux.app about privacy or your data. This policy describes the current beta app and this website.

Information we process

• Your artist profile, selected archetypes, reference artists, social handles, platform preferences, posting capacity, and release dates.
• Calendars, captions you enter, production notes, asset links, post links, completion status, and results you record.
• Collected public social posts and available metrics used for account snapshots and reference analysis.
• If you connect an account: the platform account identifier, handle, display name, and authorization tokens returned by that platform. Redux does not ask for your social account password.
• An account identifier and sign-in session used to access your Redux data, plus operational job information. Supabase Auth processes your email address, password authentication, and identifiers returned by your chosen sign-in provider. Passwords are sent directly to Supabase and are not stored in the Redux application database. Our hosting provider may process network and request information to deliver the service. If you email us, we receive the contents and contact information in your message.

How we use information

We use this information to provide account connections, analyze posting patterns, create and edit plans, display results, troubleshoot failures, and answer support requests. AI-generated recommendations may be inaccurate. Public-account data can be incomplete or out of date.

Service providers and social platforms

Supabase provides account authentication. Render hosts the backend and its application database. When live analysis is enabled and requested, Apify processes public handles and public-post collection requests; Anthropic processes relevant profile inputs, post text, metrics, and planning context to produce analysis and plans. Redux does not include OAuth tokens in those AI planning requests. These features are not all enabled in every beta environment.

Optional account authorization sends connection requests to the social platform you select, such as TikTok or Instagram. These providers process information under their own policies. We do not sell your information or use it for targeted advertising. This website has no advertising trackers or analytics scripts.

Storage and retention

Redux stores profiles, plans, snapshots, and related records in its backend database. Connected-account tokens are encrypted in that database; legacy device-session credentials are hashed there. Sign-in and refresh tokens are stored in the device Keychain, while Supabase manages authentication records. Records currently remain until removed during beta administration or in response to a verified deletion request; the beta does not yet have automatic inactivity expiry. Development or test environments may be reset, so keep your own copies of important work.

Disconnecting an account removes its saved Redux authorization credentials and attempts to revoke the platform authorization. It does not by itself delete previously saved plans or snapshots. You can also revoke access in the social platform's settings.

Your choices and requests

Account connection is optional. You can use public handles where data is available, or plan and record results manually. To request access, correction, or deletion, email us using the data-deletion instructions. We may ask for information needed to verify your request. Do not email passwords, access tokens, or verification codes.

Age and changes

The beta is intended for adults and is not directed to children. Contact us if you believe a child has provided personal information. We will update this page when our practices change, with the effective date shown above.