Security
Security at SkyLink API
This page states what is true of the system today, and nothing more. Where something is not in place, it is listed as such below.
Summary
Controls in place today
One line per area. Each row links to the detail below or to the document that states it.
Area
What we do today
Detail
Transport
API and website served over HTTPS only. Both send HSTS, X-Frame-Options, X-Content-Type-Options and Referrer-Policy headers.
Authentication
One API key per subscription, sent in the x-api-key header. Issued at checkout, managed from the customer portal.
Customer data
The API holds no customer accounts or payment data. Billing and account records are held by the payment provider.
Logging and errors
The API gateway keeps a request log (client IP, time, path, status, latency, customer ID) for 30 days, then deletes it automatically. Application errors go to Bugsink, without IP addresses or API keys.
Webhooks
HTTPS destinations only, screened against private and internal addresses. Up to four retries; disabled after ten consecutive failures. Payloads are not signed.
Hosting and sub-processors
Hosting location and every sub-processor, with role and location, are listed in the Privacy Policy.
AI briefing
Weather, NOTAM and PIREP text is sent to Cloudflare Workers AI. No customer personal data is included.
Availability
One production region. Availability published on the status page; 99.5% monthly commitment for customers with a signed agreement.
Vulnerability reporting
Report by email or via security.txt. Acknowledgement target: 3 business days. No legal action for good-faith research.
How the service works
Transport, authentication and stored data
Transport
The API and the website are served over HTTPS only. The website sends Strict-Transport-Security (HSTS, with includeSubDomains and preload), X-Frame-Options, X-Content-Type-Options and Referrer-Policy headers.
Authentication
There is one API key per subscription, sent in the x-api-key header. Keys are issued at checkout and can be managed from the customer portal.
What the API stores about customers
The API does not hold customer accounts or payment data. Billing and account records are held by the payment provider named in the Privacy Policy.
Webhook subscriptions store the destination URL, the event filters and a hash of the API key. The API gateway keeps a request log with the client IP address, time, path, status code, latency and customer ID for 30 days, used for abuse prevention and security investigation, and then deletes it automatically.
Errors
Application errors are sent to Bugsink, an error-tracking service hosted in the EU, for debugging. Error reports include no IP address and no API key.
Webhooks
Delivery rules, and what is not signed
Destinations and retries
Destinations must be HTTPS. When a webhook is created, its destination is screened against private and internal network addresses. A failed delivery is retried up to four times, and a webhook is disabled after ten consecutive failures.
Payloads are not signed today
Webhook payloads carry no signature. Until signing ships, use an unguessable URL path for your destination and treat the path as a secret.
Hosting and data flows
Hosting, sub-processors and the AI briefing
Hosting and sub-processors
The Privacy Policy states where the servers are hosted and lists every sub-processor with its role and location. It is the authoritative list.
AI briefing endpoint
To produce a briefing, the weather, NOTAM and PIREP text for the requested airports is sent to Cloudflare Workers AI, a third-party inference provider. No customer personal data is included in that request.
Availability
The service runs in one production region. Live and historical availability is published on the status page. The 99.5% monthly commitment for customers with a signed agreement is set out in the SLA.
Data use
All data is informational. It is not certified for navigation or any other safety-critical use.
Reporting a vulnerability
Tell us, and we will acknowledge within 3 business days
Good-faith security research will not be met with legal action.
How to report
Write to hello [at] skylinkapi [dot] com. The same contact details are published in a machine-readable security.txt.
What to include
- The affected endpoint or page.
- Steps to reproduce the issue.
- What you observed, and what you expected.
- How we can reach you.
Ground rules
Do not access other customers' data, degrade the service, or run automated load testing without written consent. Our acknowledgement target is 3 business days.
Security questionnaires
For security questionnaires
Security questionnaires are answered on request. Write to hello [at] skylinkapi [dot] com.
Useful references for a review: this page, the Privacy Policy, Annex III (technical and organisational measures) of the Data Processing Agreement and the Service Level Agreement.
Contact
Bring us your security or procurement review
Send us your questionnaire or your contract requirements and you will reach the engineers who run the service. Self-serve plans start at checkout.

