Privacy Policy
Last updated: October 2026
1. Who We Are
Hedge Layer is operated by Tuned Tensor Limited ("we," "us," or "our"), a company registered in England and Wales under company number 15007765, with its registered office at Suite 6049a, 60 Tottenham Court Road, London, England, W1T 2EW. We operate the website at hedgelayer.ai and act as the data controller for personal data collected through our platform. For privacy inquiries, contact us at privacy@hedgelayer.ai.
2. Data We Collect
Account data
When you sign in, we collect your email address. We use it to identify your account and deliver one-time authentication codes. Hedge Layer does not collect a wallet address for login.
Service data
We store your profile, hashed personal API tokens, token metadata, and per-user request limits. Hedge Layer Agent's cloud runtime stores context to support follow-up questions. We also save new agent questions, answers, visible proposals and chart data, tool names/status, model names and turn outcomes for your account history and export. This includes voice transcriptions, but excludes original audio, credentials, hidden model reasoning and raw tool arguments/results. If you connect WhatsApp, we store your connected number with your account, and the connector temporarily stores messages while processing replies. If you connect your own MCP server, we store its URL, its approved tool list, and its token encrypted; we send tool arguments to that server and pass its results to the client or agent that called the tool, without storing them.
Connected documents and email
If you connect Google Drive, OneDrive, Gmail or Outlook, we store the account identifier and encrypted access and refresh tokens. Email connections provide read-only access to your whole mailbox; Google Drive access is limited to files you select. Search results and requested document or message text are returned to the authenticated client or agent that requested them. Hedge Layer Agent processes those results through its cloud runtime and configured model providers, and relevant content may remain in conversation context or appear in saved answers. We do not send email or change mailbox contents. Disconnecting in Tools removes stored connection tokens and stops future reads; it does not remove excerpts already present in conversations.
Requests
Market queries are sent to the selected data provider. Evidence queries are sent to Perplexity. Current Hedge Layer Agent clients send prompts and tool results through Hedge Layer to the cloud agent in Amazon Bedrock AgentCore, which uses OpenRouter and the configured model provider for inference. Older clients use the hosted inference gateway. WhatsApp messages also pass through Meta and the hosted connector.
Technical data
Our hosting provider receives technical request information such as IP addresses and user-agent headers to operate the service. The application does not run optional analytics scripts.
3. How We Use Your Data
| Purpose | Legal basis (UK GDPR) |
|---|---|
| Account authentication & session management | Contract performance (Art. 6(1)(b)) |
| Managing profiles and API access | Contract performance (Art. 6(1)(b)) |
| Processing data queries | Contract performance (Art. 6(1)(b)) |
| Preventing fraud & enforcing terms | Legitimate interest (Art. 6(1)(f)) |
4. Cookies & Local Storage
We use the following browser storage mechanisms:
| Name / type | Purpose | Category |
|---|---|---|
| Supabase auth cookies | Session authentication | Strictly necessary |
Authentication cookies are essential for browser sign-in. API clients authenticate with personal tokens.
5. Third-Party Services
| Service | Data shared | Purpose |
|---|---|---|
| Supabase | Email, profile, token metadata, request limits; saved Hedge Layer Agent questions, answers and activity; connected WhatsApp number, pending WhatsApp messages and delivery checkpoints; your MCP server URLs, approved tool lists and encrypted tokens; connected document and mailbox identifiers and encrypted OAuth tokens | Authentication and database |
| Polymarket | Market queries | Market data |
| Hyperliquid | Market queries | Market data |
| Perplexity | Evidence queries | Web search |
| Amazon Web Services | Hedge Layer Agent conversations, tool results, and workspace files; access token used for authenticated tool calls | Cloud agent, session storage and sandbox |
| OpenRouter and the configured model provider | Prompts, tool definitions and tool results, including requested document and email content | Hedge Layer Agent inference |
| Meta / WhatsApp | WhatsApp number, messages, replies, and delivery information | WhatsApp messaging |
| Vercel | Technical request data, requests processed by the API and WhatsApp connector, and server-side connection configuration | Website, API, and connector hosting |
Where data is transferred outside the UK/EEA, we rely on Standard Contractual Clauses or equivalent safeguards.
6. Your Rights
Under the UK GDPR, you have the right to:
- Access your personal data — contact us for a copy of your account data.
- Rectification — contact privacy@hedgelayer.ai to correct your account information.
- Erasure — request full account deletion in Account.
- Data portability — contact us to request an export of your account data.
- Lodge a complaint — with the UK Information Commissioner's Office (ICO) at ico.org.uk.
We will respond to data subject requests within 30 days. Contact privacy@hedgelayer.ai for any request.
7. Agent clients
Hedge Layer Agent keeps local transcripts and uses the shared cloud agent. Hedge Layer Agent Terminal is retired; transcripts it saved remain on your device until you delete them. WhatsApp uses a separate cloud conversation for each linked number. The connector authenticates each WhatsApp turn with a short-lived read-only token for your account that is deleted after the turn; it is kept out of model context and conversation history. Other agent clients may connect directly to their chosen model providers and have their own storage practices.
8. Data Retention
Profile, token metadata and connected MCP servers are retained until you remove them or delete your account. Authentication sessions expire automatically.
When you delete your account, we keep a hash of your email address with only that week's estimated Hedge Layer Agent usage total, so a new account with the same email cannot reset the weekly allowance. It holds no other account data and stops affecting your allowance when the weekly period ends. Expired records are removed the next time an account is deleted on the service; until then, they remain stored.
New Hedge Layer Agent questions, answers and activity are retained in your account history without automatic expiry until you delete your account. You can download them from Account settings. Earlier conversations are not backfilled. Runtime session context resets after 14 idle days or a runtime update; its durable snapshots expire 90 days after a thread's last turn. Those lifetimes do not delete the separate account history. Sandbox files have a separate one-hour session lifetime. Local transcripts and messages in your WhatsApp app remain until you remove them there.
The WhatsApp connector clears sender numbers, question text, and reply content from finished inbox records. Message IDs and processing metadata are eligible for pruning after eight days, and inactive conversation identifiers after fourteen days; pruning runs when new messages are admitted. Pending or stalled work remains until it finishes or is handled by an operator. Your connected number remains until you disconnect it on the Connect page or delete your account; unused link codes expire after ten minutes. Hosting and database backups may retain earlier copies under the provider's retention settings.
Disconnect WhatsApp in Connect to stop new requests from your number. For removal of pending work or retained cloud data, contact privacy@hedgelayer.ai. Starting a new conversation with /new changes context; it is not a data-deletion request.
9. Security
We employ encryption in transit (TLS), row-level security in our database, API token hashing, and scoped access controls. We do not store passwords—authentication uses one-time codes delivered by email.
10. Children
Hedge Layer is not directed at individuals under 18 years of age. We do not knowingly collect personal data from children.
11. Changes to This Policy
We may update this policy from time to time. Material changes will be communicated via the website. Continued use of the service after changes constitutes acceptance of the updated policy.