Legal
Privacy Policy
Last updated: October 2026
How we collect, use, share and retain personal data when you use the SkyLink API and this website. Our Terms of Use incorporate this policy by reference.
Who we are
Sergio Nicolini, a sole trader established in Italy, VAT IT04163490123, trading as SkyLink API (“we”, “us”), operates the SkyLink aviation data API and the skylinkapi.com website. We are the controller of the personal data described in this policy, except where stated otherwise.
Privacy enquiries and rights requests: [email protected].
Summary
- We collect the minimum needed to run a metered, paid API: who you are, what you called, and how much.
- We do not sell or share your personal information, and we do not use it for cross-context behavioural advertising.
- Request logs, which include your IP address, are deleted after 30 days.
- Payment card details never reach our systems — our payment provider handles them.
- Your API key is stored hashed wherever we associate it with your resources.
Personal information we collect
3.1 Account and billing information
Where you subscribe directly, this is collected and processed on our behalf by Polar Software Inc. (“Polar”), our merchant of record and licensing provider.
| Data | Source | Notes |
|---|---|---|
| Name, email address | You, via Polar checkout | |
| Billing address, country | You, via Polar | Also used for tax determination |
| VAT / tax identifiers | You, via Polar | Where applicable |
| Payment method details | You, via Polar | We never receive or store card numbers. Polar is PCI-DSS compliant and holds these directly |
| Subscription plan, status, renewal dates | Polar | |
| Invoices and payment history | Polar | Retained for statutory accounting periods |
If you subscribed through the RapidAPI marketplace instead, RapidAPI is your merchant of record. Your account, billing and payment data is collected and held by RapidAPI under their privacy policy, not ours — we receive only the subscription identifier and usage needed to serve and meter your requests.
3.2 API credentials
| Data | Notes |
|---|---|
| Licence key (API key) | Issued by Polar; identifies your subscription on every request |
| Hashed API key | Where we associate resources with your account — webhook subscriptions, for example, are stored against an api_key_hash, never the raw key |
| Customer ID | An internal identifier of the form polar:<id> |
3.3 Usage and metering data
Necessary to bill you correctly and to enforce plan quotas.
| Data | Where | Retention |
|---|---|---|
| Request counts per customer | Redis, then Polar | Aggregated; billing records retained per §6 |
| Endpoint path, HTTP method, status code | Request logs | 30 days |
| Response latency, timestamp | Request logs and metrics | 30 days (logs) |
| Per-plan and per-customer request metrics | Prometheus / Grafana | 90 days |
3.4 Technical and security data
| Data | Purpose | Retention |
|---|---|---|
| IP address | Abuse prevention, per-IP validation budgets, security investigation | 30 days |
| User agent, request headers | Debugging, abuse detection | 30 days |
| Failed authentication events | Detecting credential stuffing and compromised keys | 30 days |
IP addresses are personal data under the GDPR even where we cannot link them to a named individual, and we treat them as such.
3.5 Webhook configuration
If your plan includes webhooks, we store the destination URL you supply, the event types, your filters, the creation timestamp, and a delivery failure counter. Do not put credentials, tokens, or personal data in a webhook URL — use a header or a signed path instead.
3.6 Support communications
If you use Priority WhatsApp Support, we process your phone number and the content of your messages. WhatsApp is operated by Meta Platforms, and your use of it is additionally governed by Meta's own privacy terms, which we do not control. Email support correspondence is processed similarly.
3.7 Website and cookies
The API endpoints themselves set no cookies and use no tracking technologies. This website uses:
- Google Ads conversion tracking (the gtag.js tag), to measure advertising performance — a site-wide tag, plus conversion events when a checkout completes, when a FREE Trial application is submitted, and when a Data Marketplace purchase completes. These tags run under Google's Privacy Policy and only after you accept cookiesin the consent banner shown on your first visit. You can change your choice by clearing this site's data, and opt out of personalised advertising via Google Ads Settings.
- Netlify bot protection on all forms, using honeypot fields and automated detection. No third-party CAPTCHA service is used.
- Umami (cloud.umami.is) for aggregate traffic analytics. Umami is cookieless — it sets no cookie and stores no identifier on your device, so it runs without consent. It processes your IP address transiently to derive approximate country and does not retain it.
- Sled (usesled.com), a site-wide tag used for marketing attribution — understanding which channels and campaigns bring visitors to the site. This tag loads only after you accept cookies; if you reject, it is never added to the page.
If you subscribe to our newsletter or opt in to updates, we send service announcements, product updates, and editorial content. You can unsubscribe from any email, or by contacting us.
3.8 AI-generated content (Cloudflare Workers AI)
Certain API features — specifically the AI Flight Briefing endpoint — use Cloudflare Workers AI to generate natural-language summaries from aviation data. When you use these features, the relevant aviation data (METAR, NOTAMs, PIREPs) is sent to Cloudflare Workers AI for processing within Cloudflare's infrastructure, under Cloudflare's Privacy Policy and their Workers AI terms. AI-generated briefings are informational only and must not be relied upon for safety-critical flight decisions (Terms of Use §11).
3.9 Aviation data and third-party individuals
The Service returns aviation data including aircraft registrations, ADS-B positions, callsigns, and flight movements. Some of this can constitute personal data where an aircraft is owned or operated by an individual rather than a company — a privately registered tail number can identify a natural person and reveal their movements.
- Where we process such data, our legal basis is legitimate interests (Art. 6(1)(f)) in operating an aviation information service, balanced against the fact that the underlying broadcasts are unencrypted, publicly transmitted, and already published by aviation authorities and community networks.
- Individuals whose data appears in the Service may exercise the rights in §8 — contact us and we will assess suppression of a specific registration.
- You, as a customer, become an independent controller of any such data you retrieve and retain. Terms of Use §8 applies.
3.10 Tally forms
This website shows a form operated by Tally (tally.so). If you fill it in, we collect what you submit — typically your name, email address, phone number and your answers.
By submitting the form and ticking its privacy policy checkbox, you agree that we may use this information to:
- contact you by email or by phone about your answers, your use case, or SkyLink API plans and services; and
- send you marketing communications, such as product updates, offers and news about SkyLink API.
This processing is based on your consent (Art. 6(1)(a) GDPR). You can withdraw it at any time — use the unsubscribe link in any marketing email, tell us when we call, or write to [email protected]. Withdrawing consent does not affect contact that took place before it, and we will not sell these details or share them with third parties for their own marketing.
Why we process it, and our legal basis (GDPR)
| Purpose | Categories | Legal basis |
|---|---|---|
| Providing the API; authenticating requests | Credentials, usage | Contract — Art. 6(1)(b) |
| Metering, invoicing, overage billing | Usage, billing | Contract — Art. 6(1)(b) |
| Enforcing quotas and abuse ceilings | Usage, IP | Legitimate interests — Art. 6(1)(f): preventing fraud and protecting availability |
| Security monitoring, incident investigation | IP, logs, auth failures | Legitimate interests — Art. 6(1)(f) |
| Customer support | Contact details, messages | Contract / legitimate interests |
| Accounting, tax, statutory records | Billing | Legal obligation — Art. 6(1)(c) |
| Service announcements affecting your integration | Contact details | Legitimate interests — Art. 6(1)(f) |
| Marketing emails | Contact details | Consent — Art. 6(1)(a), withdrawable at any time |
| Marketing and follow-up contact by email or phone after a Tally form submission (§3.10) | Name, email, phone number, form answers | Consent — Art. 6(1)(a), given on the form, withdrawable at any time |
| Aviation data as described in §3.8 | Third-party data | Legitimate interests — Art. 6(1)(f) |
We do not carry out solely automated decision-making producing legal or similarly significant effects within the meaning of Art. 22. Automated quota enforcement and abuse blocking affect service access only, and a human will review any suspension on request.
Who we share it with, and who we receive it from
5.1 Recipients we disclose to
We do not sell your personal information. We disclose it only to:
| Recipient | Role | Purpose | Location |
|---|---|---|---|
| Polar Software Inc. | Processor / merchant of record | Billing, subscriptions, licence keys | United States |
| Cloudflare, Inc. | Processor | CDN, TLS termination, WAF, DDoS protection, Workers AI | Global edge |
| Infomaniak Network SA | Processor | Server hosting | Geneva, Switzerland |
| Netlify | Processor | Website hosting and form bot protection | Global edge |
| Google (Ads / gtag) | Independent controller | Advertising measurement, subject to consent | Global |
| Umami Cloud (cloud.umami.is) | Processor | Cookieless traffic analytics | United States |
| Sled (usesled.com) | Processor | Marketing attribution, only with consent | Global |
| Tally (tally.so) | Processor | Website forms and surveys (§3.10) | European Union |
| Professional advisers, auditors | Processor / controller | Accounting, legal | EU |
| Law enforcement or regulators | — | Where legally compelled | — |
Each processor is engaged under a written data processing agreement meeting Art. 28 GDPR. We will also disclose data in connection with a merger, acquisition, or asset sale, subject to notifying you.
5.2 Sources we receive personal data from
The parties below are not recipients of disclosures from us. Data flows the other way: they are platforms you chose to use, and they pass your data to us so that we can serve you.
| Source | Role | What reaches us | Location |
|---|---|---|---|
| RapidAPI (marketplace subscriptions) | Independent controller | Your subscription identifier and plan, plus the requests you make. We send them no personal data about you | United States |
| Meta Platforms (WhatsApp support) | Independent controller | Your phone number and the messages you send us, if you choose that channel. We upload no customer lists or contact details to Meta | Global |
Two things follow from the fact that both are also intermediaries, not just sources. Requests to the marketplace host pass through RapidAPI's gateway, so RapidAPI processes that traffic as the operator of the route you chose. And WhatsApp is a two-way channel — our replies travel back through Meta's infrastructure, as any message on that platform does. In both cases their own privacy terms apply to that processing, and we do not control it.
How long we keep it
| Data | Retention |
|---|---|
| Request logs (incl. IP) | 30 days, then automatically deleted |
| Cached licence key validations | Up to 7 days |
| Short-lived auth caches | Up to 5 minutes |
| Usage counters | Until aggregated and reported for billing |
| Webhook configuration | Until you delete it, or 30 days after account closure |
| Account and subscription records | Duration of the contract, then 12 months |
| Invoices and accounting records | 10 years, as required by applicable tax law |
| Support correspondence | 24 months |
| Tally form submissions (§3.10) | Until you withdraw consent, or 24 months after our last contact with you |
International transfers
Our servers are hosted by Infomaniak in Switzerland, which benefits from a European Commission adequacy decision. Some recipients listed in §5.1 — notably Polar, Cloudflare and Google — operate globally. Where personal data leaves the EEA or the UK, we rely on:
- an adequacy decision where one applies; or
- the European Commission's Standard Contractual Clauses (2021/914), plus the UK International Data Transfer Addendum for UK transfers; and
- a transfer impact assessment, together with technical measures including TLS in transit and encryption of credentials at rest.
You may request a copy of the relevant safeguards at [email protected].
The sources in §5.2 are outside this framework: RapidAPI and Meta determine their own transfer arrangements for the data you give them directly, under their own privacy terms.
Your rights
8.1 Under the GDPR / UK GDPR
You have the right to: access your data; rectify inaccurate data; erase it (“right to be forgotten”); restrict processing; data portability; object to processing based on legitimate interests; and withdraw consent at any time without affecting prior lawful processing.
To exercise these rights, contact [email protected]. We respond within one month, extendable by two further months for complex requests. There is no charge unless a request is manifestly unfounded or excessive.
You may lodge a complaint with your supervisory authority. UK residents may complain to the ICO (ico.org.uk).
8.2 Under the CCPA/CPRA (California)
In the preceding 12 months we have collected the following statutory categories:
| Category | Collected | Source | Business purpose | Disclosed to |
|---|---|---|---|---|
| A. Identifiers (name, email, IP, account ID) | Yes | You, automatically | Service delivery, billing, security | Recipients in §5.1 |
| B. Customer records (billing address, payment info) | Yes | You, via Polar | Billing | Polar |
| D. Commercial information (subscription, usage) | Yes | You, automatically | Billing, quotas | Polar |
| F. Internet activity (API request logs) | Yes | Automatically | Service delivery, security | Recipients in §5.1 |
| G. Geolocation | Coarse only, inferred from IP | Automatically | Security, tax | Recipients in §5.1 |
| K. Inferences | No | — | — | — |
| Sensitive personal information | No | — | — | — |
We do not sell personal information, and we do not share it for cross-context behavioural advertising, as those terms are defined by the CCPA. We have not done so in the preceding 12 months. We do not knowingly collect or sell the personal information of consumers under 16.
California residents have the right to know, delete, correct, opt out of sale/sharing (not applicable here), limit use of sensitive personal information (not applicable here), and to non-discrimination for exercising these rights. You may use an authorised agent, who must provide written proof of authorisation.
To exercise these rights, email [email protected] or use our contact form. We verify your identity by matching your request against the account email and subscription records, and respond within 45 days, extendable once by a further 45.
8.3 Other US states
Residents of states with comparable privacy laws — including Virginia, Colorado, Connecticut, Utah, Texas, Oregon and Montana — have equivalent rights of access, correction, deletion and portability. Use the same contact route as §8.2.
Security
Measures we apply include:
- TLS for all API traffic; plain HTTP is redirected.
- HSTS, X-Content-Type-Options, X-Frame-Options, Referrer-Policy and a framing-restrictive CSP on API responses.
- API keys hashed where associated with stored resources.
- Credentials encrypted at rest in our configuration store.
- Authenticated internal datastores, not reachable from the public internet.
- Rate limiting and per-plan abuse ceilings to bound the damage from a compromised key.
- Least-privilege access to production systems, and audit logging.
No system is perfectly secure. You are responsible for keeping your API key confidential (Terms of Use §4). If you believe your key is compromised, rotate it immediately and contact [email protected].
Breach notification
Where a personal data breach is likely to result in a risk to your rights, we notify the competent supervisory authority within 72 hours of becoming aware of it (Art. 33), and we notify you without undue delay where the risk is high (Art. 34). We maintain an internal breach register.
Children
The Service is a commercial B2B product and is not directed at children. We do not knowingly collect personal information from anyone under 16. If you believe a child has provided us data, contact [email protected] and we will delete it.
Changes
We will post any change here and update the “Last updated” date. For material changes we notify active subscribers by email at least 30 days before they take effect. Continued use after that date constitutes acceptance.
Contact
Privacy enquiries, rights requests and security disclosures: