TRAVIDENCE — PRIVACY POLICY

This Privacy Policy describes how Travidence, LLC, a Delaware limited liability company with a mailing address at 800 N King Street, Suite 304-3527, Wilmington, Delaware 19801, United States (“Travidence,” “we,” “our,” or “us”), collects, uses, shares, and retains information in connection with the TRAVIDENCE websites, platform, and strategy-validation services (the “Service”). This Policy is incorporated into, and uses terms defined in, our Terms of Service.

The Service is available only to individuals 18 or older and is not offered to, or directed at, residents of the European Economic Area, the United Kingdom, or Switzerland.

1. Information We Collect

(a) Account information. Your email address, your name if you provide it, and the authentication identifiers used to sign you in (for example, Google sign-in identifiers or passkey credentials). We do not receive or store your Google account password. When you create an account after following a link from one of our pages or advertisements, we also record the page or campaign identifier carried in that link and keep it with your account information.

(b) Payment information. Payments are processed by our third-party payment processor, Stripe. We receive transaction metadata (such as amount, date, and payment status); we do not store full card numbers or security codes.

(c) Trading data you submit. The files you upload (trade histories and backtest exports) and the intake information you provide about each submission (for example, nominal capital and the number of variants tested).

(d) Broker credentials and retrieved records. If you connect a supported trading venue, the read-only API credentials you provide and the trade records retrieved with them.

(e) Technical and usage data. Standard technical logs (such as IP address, browser type, and timestamps) used for security, abuse prevention, and operations. The Service uses strictly necessary cookies and similar local-storage technologies for authentication, security, and core functionality. If you arrive from one of our pages or advertisements, your browser’s session storage may also hold, until you create an account, sign in, or close the tab, the page or campaign identifier carried in the link, so that we can count how many accounts each page or campaign produces. We do not use advertising cookies.

(f) Version Journal entries. If you use the Version Journal, we store what you enter in it: the name, instrument, timeframe, sample size and frequency you give each strategy; and, for each version you log, the date you tested it, the period the test covered, what changed, why, the result you looked at, the decision you recorded, whether you later marked the entry as not a test, your notes, and any figures you choose to enter (number of trades, net return, maximum drawdown, Sharpe ratio). We also record the date and time each entry was created or edited, and the date and content hash of each export you request. Separately, and without any entry content, we log when you create a strategy, add a version, or export, in order to count use of the journal.

2. How We Use Information

We use the information described above to: provide the Service, including running the analysis, generating your results and certificates, and maintaining your validation history; provide the Version Journal, that is, store the entries you make, show them back to you, compute the figures the journal displays from the values you enter, and produce the exports you request; measure our own pages and campaigns by counting the accounts, strategies, versions, exports and paid submissions they produce, reported in aggregate; operate the public certificate verifier, which displays only limited, non-personal fields; process payments and prevent fraud and abuse; send transactional notifications (for example, that a result is ready — result contents are never included in the email body); respond to support requests; and comply with legal obligations and enforce our Terms of Service. We may generate aggregated, de-identified operational statistics (for example, submission volumes and error rates) that do not identify you and do not reveal your submitted content.

3. Automated Analysis

The Robustness Score, verdict band, and certificate are produced by an automated, deterministic statistical engine applied to the data you submit. The outputs are informational decision-support about the submitted trading history; they do not produce legal effects concerning you, and we do not use your information for advertising or behavioral profiling. The figures the Version Journal displays — the number of versions you logged, a “noise bar”, and a probability derived from the Deflated Sharpe Ratio for the version you marked as kept — are arithmetic performed on the values you enter, using the published formulas identified in the journal; none of them is a forecast of trading results or a recommendation; we do not verify your entries or check them against any broker, platform or backtest record, and they do not enter the Robustness Score or any certificate unless you yourself type a figure from your journal into a submission’s intake. Counting which of our pages or advertisements an account came from is used to measure those pages and advertisements in aggregate; it is not used to show you advertising or to build a profile of you. If you have questions about a result, you can always reach a person at soporte@travidence.com.

4. How We Share Information

We do not sell personal information, and we do not share it for cross-context behavioral advertising. We share information only: (a) with service providers that process it on our behalf under contractual safeguards — currently including Stripe (payment processing), Supabase (authentication and database infrastructure), Render (application hosting), Cloudflare (content delivery and security), Google Workspace (business email), and Postmark (transactional email); (b) where required to comply with law, legal process, or enforceable governmental requests, or to protect rights, safety, and the integrity of the Service; (c) in connection with a merger, reorganization, or transfer of the Service, including to an affiliate, in which case this Policy will continue to apply to your information; and (d) at your direction.

5. Broker Credentials

Venue credentials are requested with read-only scope, are used solely to retrieve your trade history for analysis, and are stored encrypted at rest. We never ask for your venue login password. You may delete stored credentials at any time from your account, and they are deleted immediately when you delete your account. Retrieval of records from a venue occurs only when you initiate it.

6. Data Retention

We keep information only as long as needed for the purposes described in this Policy, with the following specific periods:

(a) Certificates and the verification registry. Retained for at least seven (7) years from issuance, in line with audit-documentation retention standards, and retained after account deletion in order to preserve the integrity of the public certificate record. The public verifier displays only limited, non-personal fields.

(b) Submitted trading data and results. Retained for the same seven (7)-year period as the evidentiary record supporting issued certificates and their reproducibility hashes.

(c) Broker credentials. Retained until you delete them or delete your account, whichever comes first. There is no retention tail for credentials.

(d) Account information. Retained while your account is active and deleted upon verified request, subject to the exceptions in this Section.

(e) Billing and transaction records. Retained for seven (7) years to meet tax and accounting obligations.

(f) Version Journal entries. Retained while your account is active. A version you delete is kept for thirty (30) days so that you can undo the deletion, and is then removed from our live systems; a strategy you delete, after confirming its name, is removed from our live systems with all its versions at once. Copies held in routine backups of the platform database are overwritten within seven (7) days; we do not restore individual entries from backups, and an entry cannot be recovered once it has been permanently removed. If the Version Journal is discontinued under Section 3(f) of the Terms of Service, entries are deleted after the notice period stated there. Export hash records and journal usage logs are kept while your account is active. None of this content forms part of the seven-year record in Section 6(b) unless you yourself enter a figure from it in a submission’s intake, in which case only that figure is retained with the submission. The Version Journal is deleted with your account under Section 7.

7. Account Deletion

You may request deletion of your account at any time from your account page or by writing to soporte@travidence.com. Upon a verified deletion request, we delete your personal information, except: the certificate registry and its supporting evidentiary record (Sections 6(a) and 6(b)); billing and transaction records (Section 6(e)); and limited records reasonably necessary to prevent fraud, resolve disputes, or comply with law. Your Version Journal — entries, entries pending undo, export hash records, journal usage logs and the page or campaign identifier recorded at account creation — is deleted with your account and is not among these exceptions; only aggregate counts that no longer identify you are kept. We state these exceptions here so that they are never a surprise.

8. Your Privacy Rights

Regardless of where you live, you may request access to, correction of, a portable copy of, or deletion of your personal information (subject to Section 6) by writing to soporte@travidence.com. We will verify your identity before acting on a request and will respond within a reasonable time. We will not discriminate against you for exercising these rights. Residents of certain U.S. states may have additional statutory rights under state privacy laws; we extend the rights described above to all users voluntarily. For the Version Journal, you can download a portable copy of your entries yourself at any time, in JSON and CSV, from the journal, within the usage limits shown in the journal’s settings (Terms of Service, Section 3(f)).

9. Security

We use industry-standard safeguards, including encryption in transit (TLS), encryption at rest, hardened access controls, and multi-factor authentication on our administrative systems. No method of transmission or storage is completely secure; we cannot guarantee absolute security, and we will respond to any incident in accordance with applicable law.

10. International Processing

We are a United States company. Your information is processed and stored in the United States and may be accessed from other countries where our personnel operate. By using the Service, you understand that your information will be processed in the United States.

11. Children

The Service is not directed to, and may not be used by, anyone under 18 years of age. We do not knowingly collect information from minors; if we learn that we have, we will delete it.

12. Changes to this Policy

We may update this Policy. If we make a material change, we will provide notice at least fifteen (15) days before it takes effect — by email to your account address and/or a prominent notice in the Service — and we will state the new version’s effective date. Changes apply prospectively only. Each published version carries a version number and effective date, and prior versions are available on request.

13. Contact

Travidence, LLC — 800 N King Street, Suite 304-3527, Wilmington, Delaware 19801, United States — soporte@travidence.com.