AURETHNETWORK

Creative intelligence.
One coordinated engine.

AURETH / YOUR INFORMATION & CHOICES

Privacy Policy

How AURETH handles information when you browse our websites or use an available Studio account.

Updated November 3, 2026 · Public commercial services have not launched.

Account access

Sign-in cookies keep requested account and security features working.

Optional analytics

Site activity is recorded only after you allow it. You can decline or change your choice.

Advertising tracking

Google Ads and Meta tracking tags are not currently active on this website.

Information you provide

When you create an available Studio account, we receive your name, email address and a password that is stored as a protected hash rather than readable text. Your saved projects may include titles, descriptions, creative requirements, storyboard text, revisions and approval history. If you use an available Google sign-in option, the information needed to verify and link that account is also processed.

We use this information to provide account access, save and retrieve your work, handle your requested actions and protect accounts. Please avoid including sensitive personal information in creative briefs unless it is necessary for your project.

Account help and confirmed actions

When you sign in, support can read your own project status, quote availability and downloadable-file information. Your account information is not sent to an external answer provider by this feature. Account actions require your explicit confirmation. Confirmations expire after ten minutes, and action records are kept privately to prevent duplicate actions and record your request. Uncommitted draft projects may be moved to Trash after confirmation and restored for 30 days; expired recovery windows require AURETH review and do not automatically purge files. Ordered, running or delivered projects require review. Refund requests are sent to the owner for approval and do not issue money automatically. Subscription cancellation and plan-change requests are recorded for review while billing is disconnected; they do not change a subscription or create a charge.

Support conversations and requests

The support center uses a necessary browser cookie to keep your conversation and requests available. Conversation records expire after 30 days. You can choose to send your name, email address, a message and an optional conversation transcript to AURETH for personal follow-up. Replies posted by AURETH appear in your support requests. Email delivery is not currently connected.

When a configured answer service is available, the question and relevant conversation may be processed by that service to prepare a reply using AURETH’s published information. Do not share passwords, API keys or payment-card details. Obvious credentials and email addresses in chat text are removed before processing, but automated filtering cannot identify every kind of sensitive information.

Open support requests remain available for review. Closed requests and their reply history are removed 90 days after the last update during routine support access. Support content is separate from optional website analytics and is not included in its event records.

Information from website use

AURETH’s optional website analytics uses a random browser-tab identifier to group recorded visits. This identifier is not your name or customer account identity. With your permission, it records page views, link visibility and clicks, broad screen-size categories, referring domains and observation times.

The analytics dataset does not contain IP addresses, email addresses, form entries, URL queries, passwords or private dashboard activity. This describes the analytics feature, not a claim that ordinary network requests never contain technical connection information.

Authentication and security features also process information needed to verify requests and protect account access. Our Cookie Policy explains browser storage and your options.

Connected services and external websites

Following an external link takes you to another service with its own policies. If you choose an available Google sign-in or another connected service, the permissions and information involved are presented through that service’s authorization process.

Creative production may involve configured service providers when the requested feature is available. Public production services and their provider disclosures must be confirmed before commercial launch. An owner connecting a reporting or advertising account does not, by itself, authorize tracking every website visitor.

Google Analytics reports, when configured for the owner, remain separate from AURETH’s own recorded website observations. Google Ads and Meta website tracking tags are not currently active here.

How long information is kept

Optional website analytics observations are removed after 90 days during routine collection or report access. Cookie and browser-storage durations are listed in the Cookie Policy.

Studio account and project records currently remain in the local development service until removed through an authorized account or support process. Automated subscription expiry and account purging are not active public services.

For future subscriptions, the approved access policy provides 90 days to retrieve work after a subscription ends and 365 days of total content retention before scheduled account closure and deletion. One-time projects have a 30-day download period after delivery. These commercial services have not launched. Read the subscription retention policy and one-time project policy for their intended terms.

Your choices and requests

You can browse without optional analytics, change that choice at any time, clear browser storage, and sign out of an available account. Before public launch, AURETH will provide its confirmed business identity and a working privacy contact for access, correction, deletion and other applicable privacy requests.

The Contact page reflects the current availability of contact details. A complete public privacy-request channel is a launch prerequisite; this development notice does not replace one.

Security and updates

Account permissions, protected password hashes and server-side access checks help safeguard information. No website can promise absolute security. Current development services operate locally; public hosting, international processing, service-provider details and applicable privacy rights must be confirmed for the intended launch markets before deployment.

We will update this notice when the website’s data practices change. New optional tracking purposes will be presented separately before they are enabled.