1. Who we are
The controller of personal data processed through Fenestra (fenestrading.click, the Fenestra Lens extension and the Fenestra app) is the operator of the Fenestra service at fenestrading.click (contact: help@fenestrading.click). Contact us about privacy at help@fenestrading.click.
2. Data we collect
| Data | What it is | Why |
|---|---|---|
| Waitlist | Your email address; optionally, the callers or channels you follow; the page that referred you and campaign tags (UTM parameters) in the link you used. | To invite you when your access opens and to understand where interest comes from. Legal basis: consent, which you can withdraw at any time. |
| Account data | If you have an account: email, login and session data, your settings, the sources and agents you configure, and their activity (plans, simulated and live orders, results). | To provide the app. Legal basis: performance of our contract with you. |
| Wallet public addresses | The public address of a wallet you connect (for example your Hyperliquid account address) and signatures you choose to send us, such as the agent approval. | To verify that you control the account and to relay your approval to Hyperliquid. Public addresses and their on-chain activity are public by nature. Legal basis: contract. |
| Encrypted agent keys | If you approve an agent wallet, the private key of that agent (not of your wallet). It is encrypted with AES-GCM before storage, can only place and cancel orders on Hyperliquid (it cannot withdraw), and is destroyed when you revoke it. You can also revoke it on Hyperliquid directly at any time. | To place trades you have configured, within your limits. Legal basis: contract. |
| Basic logs | Technical request data such as IP address, user agent, requested URL, time and errors, kept by us and our hosting provider. Security and audit events, such as an agent approval or revocation. | To run, secure and debug the Service and prevent abuse. Legal basis: legitimate interests. |
| Messages to us | What you send to help@fenestrading.click, including dispute evidence. | To answer you and handle disputes. Legal basis: legitimate interests, or contract. |
When you use the Buy button, the swap is built and signed in your browser. Your public wallet address and the swap request go to Jupiter to get a quote and execute; we do not store them in an account.
3. Data we don't collect
- Private keys or seed phrases of your wallets. We never ask for them and never receive them. Your wallet signs locally. Nobody from Fenestra will ever ask for them.
- Telegram or X logins. We do not ask you to sign in with Telegram or X and do not access your accounts there. Public caller data is read from public pages without logging in.
- Your exchange withdrawal rights. The agent key cannot withdraw or transfer funds, and we hold no other exchange credentials for Hyperliquid.
4. Public caller data
Fenestra tracks people and channels who publicly post crypto calls ("callers"), so that anyone can check what happened after their calls. For callers, we process:
- Public posts only. We read posts that are publicly visible without logging in (today, public Telegram channels through their public web preview). We do not read private groups, direct messages or anything behind a login.
- Display names and handles as shown publicly by the caller, and the channel's public statistics.
- Links to the original posts, the time they were posted, and what we extracted from them (the token, direction and any prices). We keep the post text to score it and to detect edits and deletions; public pages show the extracted call and link to the original post rather than republishing the text.
- Derived data: outcomes, scores and flags (deleted, edited, late), as described in the Methodology.
Our legal basis is legitimate interests: the public, and people deciding whether to act on a call, have a real interest in an accurate, verifiable record of public market commentary. We limit what we process to what is needed for that record.
Callers' rights. If you are a caller, you can ask us to correct inaccurate data (for example a misread call or a wrong attribution), to see the data we hold about you, or object to processing. See Disputes for how to send a correction with evidence. Deleting a post does not remove it from the record, because a record that only keeps the calls a caller chose to leave up would mislead the public; the call is shown with a "deleted" flag instead. We assess every objection individually.
5. How we use data
We use data to provide and secure the Service, to build public caller records, to run the agents you configure, to contact you about your waitlist place or account, and to meet legal obligations. We do not sell personal data, and we do not use your data for third-party advertising.
6. Processors and third parties
We use these providers to run the Service. The list below is a placeholder pending confirmation of each provider's role, location and transfer safeguards.
| Provider | Purpose | Data involved |
|---|---|---|
| Vercel Inc. (functions in Frankfurt, EU) | Hosting, serverless functions, request logs | Logs, all data in transit |
| Neon Inc. (AWS Frankfurt, EU) | Database | Waitlist, account data, wallet addresses, encrypted agent keys, caller data |
| LLM providers: Anthropic (Claude); Google (Gemini) if enabled as a fallback | Reading public posts to extract calls; AI features in the app | Public post text; prompts you enter in the app |
| Jupiter | Swap quotes and execution for the Buy button | Your public wallet address, swap details |
| Hyperliquid | Agent approval and order placement | Your account address, signed approval, orders |
| RugCheck; Solana public RPC as a fallback | Token safety checks on token pages and in the Lens extension (mint and freeze authority, LP lock, holders, creator history) | Token addresses only, requested by our servers; no personal data |
| DexScreener, GeckoTerminal, Binance public market data | Token prices and pools | Token addresses and tickers only, no personal data |
| Our email provider | Sending waitlist and account emails | Email address |
Some providers may process data outside your country, including outside the EEA and UK. Where required, transfers rely on the European Commission's adequacy decisions or standard contractual clauses. Blockchains are public: anything you sign onto a blockchain is permanently visible to anyone and cannot be deleted by us.
7. Retention
- Waitlist entries: until you get access or ask us to remove you, and at most 24 months.
- Account data: while your account is open, then deleted within 30 days, except what we must keep by law.
- Agent keys: destroyed when you revoke the agent or close your account.
- Logs: up to 90 days.
- Public caller records: kept while the record serves its purpose, subject to corrections and objections.
8. Security
Data is encrypted in transit. Agent keys are encrypted at rest with AES-GCM using a key held separately from the database. Access to production data is limited. No system is perfectly secure; if you believe your account or agent wallet is at risk, revoke the agent on Hyperliquid and contact us.
9. Your rights (GDPR)
If the GDPR or a similar law applies to you, you have the right to access your personal data, to have it corrected, to have it erased, to restrict or object to its processing, to data portability, and to withdraw consent at any time without affecting earlier processing. You also have the right to complain to a data protection authority, in particular in your country of residence. To use any of these rights, email help@fenestrading.click. We may need to verify your identity, and we answer within one month (extendable where the law allows).
10. The Lens extension
Fenestra Lens shows who called a coin, and their record, on supported chart and trading sites, and a caller's record on their X profile.
- Permissions. Lens requests one browser API permission,
storage, to remember the panel's position and your settings. Its host access is limited to fenestrading.click and the supported sites listed in the extension (such as DexScreener, pump.fun, Birdeye, GMGN, Axiom, Photon and X). - What it sends. On a supported chart page, it sends the token address it finds for the page you are viewing to the Fenestra API (fenestrading.click) to look up callers. On an X profile page, it sends that profile's handle. These lookups do not include cookies or your identity.
- What it reads. It reads only the page URL and, on pair pages, the token links on the page, to find the token address. It does not read your wallet, keystrokes, form fields, messages or other page content, and it does not collect your browsing history.
- Logs. Like any request to our API, a lookup creates a basic server log entry (see above).
You can turn Lens off per site in its options, or remove it at any time.
11. Cookies and local storage
The public pages do not use advertising or analytics cookies. The logged-in app uses what it needs to keep you signed in. Pages and Lens may store small preferences in your browser (such as a selected filter or the panel position).
12. Changes and contact
We will update the "Last updated" date when this policy changes and give notice of material changes. Questions or requests: help@fenestrading.click. See also our Terms.