Privacy · Trinity Sim

Who is responsible and how to contact us

Aventide LLC, registered in Florida, United States, operates TrinitySim. For privacy questions or requests about your data, email support@trinitysim.com.

Data we process

Account and sign-in: if you register by email, we process your address, username, a password hash, and records needed to verify your email or reset your password. If you choose Discord, we receive your Discord ID and profile data the provider returns, such as username or avatar; email depends on what Discord provides. We never receive your Discord password.
Sessions and security: we process IP address, browser (user-agent), activity times and session data to sign you in, protect accounts and limit abuse.
Simulations: we process the character profile and settings you paste, import or look up, including character name, realm, region, class, specialization, talents and gear. We also process the simulation job, status, result and history. This data is processed on our Cloudflare and netcup services to run and show the simulation.
Guest use: a random guest identifier is created and a token hash is stored to apply usage limits. The token stops working after 72 hours. The simulation is still processed under a pseudonymous identifier and may create operational records; it is not linked to a registered account.
Feedback, errors and support: we may process your rating, category, comment and technical context, such as product, specialization, game version or references to a job. If you open a ticket through our Discord bot, we store the ticket's content, your Discord ID and the linked TrinitySim account, if one exists. Do not include passwords, payment data or unnecessary personal information.
AI assistant: if you use the AI features (result explanations, settings by text, comparison with combat logs and the support chat), we send our AI providers only what is needed to answer you: game data from the result, the text you type and, for support, the status of your latest jobs. We do not send your email, account name, character name, realm or payment data, and before sending we remove the personal data we detect from the text. Simulations do not use AI. We keep the support conversation and, if a ticket is opened, its summary, so we can help you, and we record usage to apply each plan's limits.
Paid memberships: when Vanguard or Ascendant are offered for purchase on the membership page, Stripe processes the payment on its own pages. You enter your card details directly with Stripe and they never reach TrinitySim. From Stripe we receive and keep only the subscription and invoice data needed to apply and manage your plan and email you its receipt.
Technical data: our services and providers may record request, operation, security and error information. The details available depend on the service and its configuration.

How we use data

To create and protect accounts and sessions; verify email addresses and send password-reset links.
To receive and run the simulations you request, and show results and history.
To apply usage limits and membership states assigned by TrinitySim and, when paid memberships are on sale, to manage your subscription and send its receipts.
To respond to feedback and support requests, fix errors, and maintain service security and availability.
To validate the engine with inputs from testers who accept the applicable notice. The engine's own outputs are never used to calibrate it.

Cookies and browser storage

We use cookies needed to maintain a sign-in session, lasting up to 14 days and renewable while you use the site, and a guest cookie valid for 72 hours. Your browser may also store preferences and temporary form or simulation data in localStorage or sessionStorage. You can clear these using your browser controls. The current website does not use advertising or analytics cookies.

Retention and deletion

Account sessions expire no later than 14 days after their last renewal. A guest token stops working after 72 hours, and its record is removed afterwards.
Feedback and error records have a 90-day retention period. Deletion may happen somewhat after that period has elapsed.
Simulations in your history, with their results, are deleted automatically 7 days after you send them on the Explorer plan and 15 days after on Vanguard or Ascendant. Simulations run without signing in are not saved to any history and are deleted when the guest session ends, 72 hours after it starts, unless you sign in first: they then move to your account and are kept for your plan's period, counted from when you created them. Automatic deletion starts on November 3, 2026; older history is kept until then. The summary copies the website keeps are deleted after 15 days at most, and a technical record of each job, with no profile or results, after 30 days.
Account data and character profiles do not currently have a set automatic expiry. You can request deletion by email, and we handle it by hand in each of our systems.
Billing records (subscription, payments, refunds and receipts) are kept as long as needed to manage the subscription, meet tax and accounting obligations or resolve disputes.
Support tickets, some security or audit records, and technical logs held by providers do not have one published deletion period. They may be kept as needed to handle a case, operate or protect the service, meet legal obligations or resolve disputes; provider-managed copies follow their own cycles.
We handle access, correction or deletion requests under applicable law. We may ask for reasonable information to verify that a request is yours and will explain any exception or data we cannot delete.

Services that help us operate TrinitySim

Cloudflare, Inc.: network, hosting and database for the website, identity system and service features.
netcup GmbH (Germany): servers and database for the service and the simulation engine.
Discord Inc.: sign-in, account linking, bot and tickets you choose to submit through Discord. Discord also processes data under its own terms.
Anthropic, PBC and OpenAI (United States): AI providers that process, on behalf of TrinitySim and only to generate the answer, the data described under “AI assistant”. Under their terms, they do not use it to train their models and keep it only for a limited time.
Warcraft Logs: lookups of the public reports you link for the real-fight comparison.
Resend, Inc.: delivery of email verification and password-reset messages when those email features are configured.
Blizzard Entertainment: Battle.net API lookups for character portraits; when you use that feature, we send the name, realm and region needed for the lookup.
GoDaddy / DomainControl: authoritative DNS for the domain's root zone.
Microsoft 365 / Exchange Online: the domain's email service and, if configured there, delivery or forwarding of messages to the privacy address.
These providers may process data in the United States, Germany or other places where they operate. Each provider may process the data it receives under its own terms and policies.
Stripe, Inc.: payment and subscription processing for paid memberships when they are offered for purchase. Stripe handles payment data under its own terms and privacy policy.
TrinitySim never receives or stores your card numbers: when there are payments, only Stripe handles card details. While the membership page says paid plans cannot be purchased, nothing is charged.

Privacy requests and rights

Email support@trinitysim.com from your account email address or include your username. You may request access, correction or deletion and exercise other rights where applicable law gives them to you. The response may depend on identity verification, legal deadlines and applicable exceptions.

You may also contact the competent public authority where you live if you have a complaint.

Children

TrinitySim is not directed to children under 13. If you believe a child under 13 sent us personal data, email support@trinitysim.com so we can review it and take appropriate steps.

Changes to this policy

We will update this page and its date when our practices change. We will announce significant changes in the service when appropriate.