SKYANALYST AI LLC PRIVACY NOTICE
Last updated: 28 September 2026
This notice explains what we do with personal data on this website: what we collect, why, who else sees it, and what you can ask us to do about it. It is written to be read, not filed. If anything here is unclear, write to us and we will explain it.
1. Who we are and how to contact us
SkyAnalyst AI LLC is the controller of the personal data described in this notice. That means we decide what is collected and why.
Postal address
SkyAnalyst AI LLC
382 NE 191st St, Miami FL 33179-3899, United States
Email: info@skyanalyst.ai. Use the same address for any request about your data. It reaches the people who can act on it.
2. What we collect
None of this is compulsory. Every form on this site is voluntary, and no law or contract obliges you to give us anything. If you would rather not give us an email address, the only consequence is that we cannot reply to you or send you the thing you asked for.
2.1 When you contact us or book a demo
You give us these details yourself, by filling in a form. What we ask for depends on the form:
- Demo booking: name, email, WhatsApp number, company, anything you write in the notes, and whether you want our emails.
- Consultation or waitlist: name, email, phone, your experience level, your goals, and how you prefer to be contacted.
- Institutional enquiry: name, email, phone, company, job title, assets under management, number of seats, and what you want to use the product for.
- Free digital book: first name, last name, email, phone and experience level.
- Job application: name, email, the position, a link to your portfolio and your message.
- Investor relations: name, email, firm and message.
- Market Pulse: email address, and whether you want it by email, Telegram or WhatsApp.
2.2 Automatically when you visit
- Your IP address. We use it to limit how often the same visitor can submit a form and to stop abuse. It is held in memory for that check and is not stored against a person.
- A coarse country, read at the network edge. It decides which language we show you and whether cookies wait for your agreement.
- If you allow performance cookies, an attribution record: a random id, plus utm_source, utm_medium, utm_campaign and ref from the link you arrived on, and the time of that first visit. Section 4 explains this one in full, because it is the least obvious thing on this page.
2.3 From the services we use
- Our email provider tells us whether a message was delivered, opened or bounced. It also sends us the IP address and browser behind an open. We throw both away on purpose and do not store them.
3. What we use it for, and our legal basis
| Purpose | What this involves | Legal basis |
|---|---|---|
| Arranging demos and replying to you | Reading the form you sent, arranging the call, creating the calendar invitation, and answering you. | Contract, or the steps leading to one. GDPR Art. 6(1)(b). |
| Keeping the site safe | Rate limiting form submissions and blocking abusive traffic. | Legitimate interests. GDPR Art. 6(1)(f). |
| Marketing email | Sending the market and product emails you asked for. The box is not ticked for you, and every message carries an unsubscribe link. | Your consent. GDPR Art. 6(1)(a). |
| Non-essential cookies, including the Meta Pixel and the attribution cookie | Setting and reading cookies that are not needed for the site to work. | Your consent. GDPR Art. 6(1)(a) and Art. 5(3) of the ePrivacy Directive. |
| Deciding which enquiry to answer first | Looking at where an enquiry came from and how recently, so the team works through the queue in a sensible order. | Legitimate interests. GDPR Art. 6(1)(f). |
Where we rely on legitimate interests you can object. See section 8. We do not rely on legitimate interests for advertising or for measurement: those need your consent, and they wait for it.
4. Cookies and similar technologies
We group cookies into four categories:
- Strictly necessary. Your language choice, your cookie decision itself, and the password unlock for our internal plan pages. These cannot be switched off, because the site cannot do its job without them.
- Functional. Conveniences that are not essential. An embedded YouTube video loads only if you allow this category, and we load it from youtube-nocookie.com.
- Performance. One cookie, ours, named sa_attrib. See below.
- Targeting. The Meta Pixel, which sets _fbp and _fbc, each lasting 90 days. It loads only if you allow this category.
The full table, with every cookie name and lifetime, is on our cookie policy.
sa_attrib, put plainly
It records which link or site sent you here, along with a random id, for 90 days. It is not always anonymous. If you later give us your email address, the recorded source is attached to your record, and from that point the id is tied to you. We use that to decide which enquiries the team contacts first.
The random id is also added to links that go from this site to skyanalyst.app, as a parameter called aid, which is how a signup in the app is matched back to this visit.
We keep it in the performance category rather than the advertising one because it is our own measurement and is never handed to an ad network, so refusing advertising does not switch it off. Refusing performance does.
How to change your choice
On your first visit a banner asks. Your answer is remembered for 12 months, then we ask again. If you are in the EEA, the UK or Switzerland, nothing non-essential runs until you agree. Elsewhere, non-essential cookies run until you refuse them. We honour Global Privacy Control, so if your browser sends that signal we treat it as a refusal.
You can change your mind whenever you like. Use the cookie link in the footer of any page, or go to your preferences. Withdrawing advertising consent takes effect once the page reloads, and the page reloads itself so you do not have to.
5. Who we share it with
| Recipient | What they get | Where they process it |
|---|---|---|
| Vercel | Hosting. Every request to this site, including the IP address it came from. | United States |
| Supabase | Our database: CRM records, bookings, subscribers and the blog content. | United States, Ohio region |
| Resend | The address we send to, and delivery, open and bounce reports. | United States |
| For a booked demo, a calendar event naming you as the attendee, and the Meet link for the call. | United States | |
| Meta | Pixel events from your browser, and only if you have allowed advertising cookies. | United States |
| Reddit Ads | Ad events from your browser, and a report when a sign-up came from one of our Reddit ads. Both only if you have allowed advertising cookies. | United States |
| Google Ads | Ad events from your browser, and a report when a sign-up came from one of our Google ads. Both only if you have allowed advertising cookies. | United States |
| Amazon Web Services | Media files, stored in S3 in the us-east-2 region. | United States |
| YouTube | A request for an embedded video, and only if you have allowed functional cookies. | United States |
We do not sell personal data. Everyone in the table above is a supplier working on our instructions, not a buyer.
When you arrive from one of our ads
A link from one of our paid ads carries a click identifier that the ad platform adds to it. If you have allowed performance cookies, we store that identifier together with the pseudonymous visitor id described in section 4. If you have not, we store neither.
We use this to tell which ad led to a later sign-up. Only if you have also allowed advertising cookies do we report that sign-up back to the platform that showed you the ad. We keep this data for 90 days and then delete it.
The platforms are Reddit Ads and Google Ads. You can read how each handles data in the Reddit privacy policy and the Google privacy policy.
6. Sending your data outside the EEA and the UK
We are based in the United States, and so is every provider in the table above. So if you are in the EEA, the UK or Switzerland, your data is transferred to the United States and processed there.
These transfers rely on the standard contractual clauses in each provider's own terms. We do not go further than that on this page, because that is what we can actually verify. If you want to know more about a specific provider, write to us.
7. How long we keep it
- Your cookie decision: 12 months. Then the banner asks again.
- Cookies: each one has its own lifetime, listed on the cookie policy. The longest we set lasts 365 days.
- Unsubscribe links: they keep working for 365 days after the email was sent.
- Email delivery logs: cleared after 30 days.
- Enquiry and customer records: we keep them while there is a live relationship or an open conversation, and we review them once there is not.
To be straight with you: there is no automatic deletion running today, so we are not going to promise you a number. What we will say is that you can ask us to delete your record at any time, and we can do it across the whole CRM. See section 8.
8. Automated decisions and profiling
We do not make decisions about you by automated means that have a legal effect, or an effect of similar weight. No software of ours decides whether you get a trial, what you pay, or whether you get a reply.
What we do is smaller, and worth naming anyway. When an enquiry arrives, the order we work through the queue is influenced by where it came from, which link or campaign brought you, and how recently you were in touch. A person reads every enquiry and decides what happens next.
Our product analyses markets, not people. The AI behind SkyAnalyst studies instruments and trades. It does not build a profile of you and plays no part in how we handle your enquiry.
If you would rather we did not sort you that way, say so at info@skyanalyst.ai and we will stop.
9. How we keep it safe
The site is served over HTTPS only, with strict transport security and a content security policy that limits what is allowed to run on the page. Our database is reachable only by our own servers, with a key that never reaches your browser. Staff tools sit behind a separate login. Public forms are rate limited, which blunts automated abuse.
No system is perfect, and we would rather write that than imply otherwise. If you find a weakness, tell us at info@skyanalyst.ai and we will act on it.
10. Your rights
If you are in the EEA, the UK or Switzerland, you have the right to:
- ask what we hold about you and get a copy (access);
- have something wrong corrected (rectification);
- have your data deleted (erasure);
- have us pause using it while a question is resolved (restriction);
- object to processing we base on legitimate interests;
- object to direct marketing at any time, which we always honour, with nothing to weigh up;
- receive the data you gave us in a portable form (portability);
- withdraw consent you gave, at any time, without affecting what was lawful before.
How to use them: email info@skyanalyst.ai and say what you want. One address, no form to fill in. We will answer within one month. If we cannot tell that a request really comes from you, we may ask for something that confirms it, which is there to stop somebody else asking for your data.
For marketing email specifically, the unsubscribe link in any message is faster. For cookies, use the footer link or your preferences.
11. Complaints
If you think we have handled your data badly, tell us first at info@skyanalyst.ai. We would rather fix it than have you chase us. You can also complain to the data protection supervisory authority in the country where you live or work. In the United Kingdom that is the Information Commissioner's Office. You do not need our permission and you do not have to come to us first.
12. Children
This site is aimed at adults. Under our Terms of Use, anyone under 18 needs a parent's or guardian's consent to use the service, and we do not set out to collect data from children. If you believe a child has sent us their details, write to info@skyanalyst.ai and we will remove them.
13. Changes to this notice
We update this notice when what we do changes. The date at the top and in section 12 is the date of the version you are reading. If you want to know what changed, ask us.
14. Last updated
Version 1.1, 28 September 2026. Version 1.0 was published the same day.