Privacy Notice

1. Information processed

Vorda analytics are designed to exclude raw credentials, balances, positions, symbols, quantities, order payloads, and arbitrary request bodies. Stripe, not Vorda, handles complete card details.

• Identity and account data handled with Clerk: identifiers, email, display name, security state, workspace membership, role, and timezone.
• Provider connection data: account identifiers, scopes, encrypted credentials or tokens, connection status, and credential versions.
• Operational account data: balances, equity, buying power, positions, orders, fills, fees, and Provider status needed for display, validation, routing, and reconciliation.
• Signal Sources, source messages, Trading Rules, Automations, mappings, instruments, quantities, readiness, commands, and execution intents.
• Execution and diagnostic data: actions, Provider responses, order identifiers, reconciliation, sanitised Proof, errors, logs, security events, and timestamps.
• Stripe billing metadata; Telegram link and notification data; support communications; and pseudonymous website and product analytics.

2. Sources

Information comes from users, Clerk, Stripe, connected Providers and Signal Sources, Telegram, browsers or devices, Vorda systems, and organisations that validly invite a user to a workspace.

3. Purposes

• Create, authenticate, secure, and administer accounts and workspaces.
• Provide routing, execution, Proof, reconciliation, notifications, and support.
• Enforce permissions, safety controls, entitlements, acceptable use, and law.
• Process subscriptions and billing records.
• Detect abuse, investigate incidents, debug, measure reliability, and communicate service or legal updates.

4. No undisclosed model training

Vorda does not silently use customer trading data, credentials, positions, orders, instructions, or execution Proof to train a general-purpose model. Future secondary training use requires a defined purpose, disclosure, lawful basis, controls, and approval.

5. Legal bases and Australian position

Where required, intended bases include performance of the service agreement, legitimate interests in operating and securing Vorda, compliance with law, protection of legal interests, and consent for optional analytics or communications.

[COUNSEL MUST CONFIRM AUSTRALIAN PRIVACY ACT AND APP COVERAGE, ANY SMALL-BUSINESS EXEMPTION OR OPT-IN, AND THE MODULES REQUIRED FOR EACH LAUNCH MARKET.]

6. Recipients

• Clerk for identity and security.
• AWS and Cloudflare for hosting, networking, storage, security, and delivery.
• Stripe for checkout, billing, tax configuration, fraud controls, and portal functions.
• Connected Providers and routing services for account state, permitted instructions, and reconciliation.
• Telegram when selected by the user.
• PostHog, Google Analytics, and Amplitude when configured and allowed by consent.
• Professional advisers, authorities, and workspace administrators where lawfully necessary.

7. International processing

An Australian Vorda entity is expected to use providers in multiple countries. [COUNSEL TO INSERT VERIFIED COUNTRIES, AUSTRALIAN APP 8 DISCLOSURE, AND ANY REQUIRED EEA OR UK TRANSFER MECHANISMS.]

8. Retention

• Sanitised source and Provider payload bodies: 30 days.
• Durable execution identity, state, explanations, references, and sanitised Proof: while the account exists during founding beta; final period TBD.
• Anonymous analytics visitors: 13 months; linked visitors: until account deletion subject to required records.
• Delivered analytics outbox: 7 days; analytics dead letters: 30 days.
• Billing, security, audit, support, backups, and legal records: [VERIFIED PERIOD REQUIRED].

9. Security

Vorda uses access controls, segregated roles, transport encryption, and AWS KMS encryption for stored Provider credentials. Credentials are intended to be decrypted only by the execution worker for a required operation. No security measure removes all risk.

10. Cookies and choices

The Cookie Notice describes browser technologies and analytics controls. Optional analytics should remain off until opt-in where required, and unknown regions are intended to fail closed. Essential identity and security technologies cannot be disabled through the analytics control.

11. Rights

Depending on applicable law, a person may have access, correction, deletion, restriction, objection, withdrawal, portability, complaint, or appeal rights, subject to exceptions. Requests should go to [PRIVACY EMAIL] and may require Clerk identity verification.

[COUNSEL TO ADD ONLY THE AUSTRALIAN, U.S. STATE, EEA/UK, AND OTHER MARKET RIGHTS THAT ACTUALLY APPLY.]

12. Children, changes, and contact

Vorda is not directed to anyone under 18. Material notice changes should receive reasonable notice and consent where required.

Privacy requests: [PRIVACY EMAIL]. General questions: [email protected]. Postal address and Australian complaint process remain unresolved.

Optional analytics controls

When enabled, pseudonymous analytics help us understand how people find Vorda, move from the website to the app, sign up, activate the product, and return.

We do not send credentials, balances, positions, email, phone, or arbitrary URL values to analytics. In the EEA, UK, Switzerland, and locations we cannot classify, analytics stay off until you allow them. Elsewhere they start automatically and can be rejected here.