UPDATED 18 NOVEMBER 2026

Privacy policy

How the relay shared account and subscriptions use the information needed to run the service.

Operator and scope

relay is operated by Gökhan Aşan in İstanbul, Türkiye. This policy covers relayCREATE’s shared account and subscription management and their connections to relayPM, relayDESIGN, relayART and relayENGINE. Product-specific information remains described in each product’s privacy notice. Contact support@relaycreate.ai for privacy questions or requests.

Information we process

Account information includes your email address, mobile number, verification status, linked Google identity, password hash if set, sessions and explicit product-account links. We process service and security metadata to operate sign-in, investigate failures and prevent abuse. Subscription records include your canonical account reference, Paddle customer, transaction and subscription references, plan terms, payment status, periods and usage receipts. AI usage records include reservations and settled cost used to enforce the shared allowance. Support correspondence includes what you send us.

Project information and AI providers

Projects, tasks, designs, assets, agent approvals and generated output remain in the corresponding product and are available only within its access controls. Shared sign-in or billing does not make a private project public. An authorized hosted AI operation sends the relevant task instructions and context to its selected model provider. Returned output and usage may be retained by the product. External agents process information available to their approved identity in the tools and providers you use. Do not include passwords, API keys or other secrets in project content.

Hosting, sign-in and messages

AWS hosts the service and recovery data on the existing relay infrastructure. Google sign-in, when selected, provides your Google account identity. Google Firebase Authentication and reCAPTCHA process your phone number and technical information for verification and abuse prevention. See Firebase privacy information and Google’s Privacy Policy. Existing Google Workspace email services handle transactional and support messages; carriers participate in SMS delivery. Providers may process information outside your country. relay does not sell your contact details or use verification messages for advertising.

Paddle payments

Paddle processes billing and payment information entered into its checkout and acts as merchant of record under its Privacy Policy. We send checkout and canonical account references, selected plan terms and the existing customer reference where applicable. We receive payment, subscription and adjustment state to supply purchased access, reconcile usage and handle support. We do not store full payment-card numbers or security codes, or send project prompts, passwords or agent tokens to Paddle as part of billing.

Cookies, verification and recovery

Essential cookies and browser storage maintain sign-in, preferences and safe retry state. Shared account sign-in can be remembered for up to 180 days unless ended earlier by sign-out, password reset, revocation or clearing cookies. Email and phone proof are required for paid checkout. Requested email-verification and recovery links are single use and expire; password reset revokes existing account sessions. Checkout retry identifiers remain scoped to the original account and may survive browser session restoration. relayCREATE does not add advertising trackers to its public pages. Google and Paddle have their own security and checkout processing.

Retention and your requests

Account, product, usage and billing records are durable service data with recovery backups. Expiring a session or link does not delete account history. Billing and security records may need retention for reconciliation, disputes, security and applicable obligations. Closing an account ends sign-in but does not automatically erase shared project history, billing records or backups. Email support for access, correction or deletion requests; we verify identity and authority, review shared records and retention requirements, and explain the outcome. Do not send passwords, verification codes or access tokens. A data request does not grant access to someone else’s project.