Privacy Policy

This policy describes personal data handled for the Skyviewor Data website, accounts and API service. Checkout and transaction data handled by payment provider are also subject to its own privacy policy.

1. Who is responsible

Skyviewor Data is a brand operated by an individual, not a company. The individual operator is responsible for personal data processed for this website, accounts, API access and technical support. payment provider is a separate Merchant of Record and authorized reseller; the payment provider entity on a receipt is not the operator of this website.

Send privacy questions and applicable data protection rights requests to [email protected].

2. Data and purposes

• Accounts: email addresses, verification status, password hashes, sessions, security tokens and profile details you supply, such as name, company and time zone. These support authentication, recovery, notifications and account management.
• Optional Google or GitHub sign-in: provider account identifiers and profile and email information needed to link an account and check trial eligibility. We do not receive your provider password.
• API access: application names, key identifiers and prefixes, protected credentials, entitlement dates and status, and HTTP request and WebSocket delivery counters. These provision service, enforce limits, show usage and support troubleshooting.
• Security: IP-related verification and rate-limit information, authentication events and administrative audit records. These protect accounts and help investigate abuse. Hosting services also process request metadata to deliver and secure the service.
• Successful sign-in records include time, method, network-exit IP and available country. API access records aggregate by Key identifier, IP, country and hour for account security, abuse investigation and support, visible only to authorized administrators. Service records are retained approximately 30 days; gateway buffers and unsynchronized journals may retain metadata longer during synchronization outages. Collection can be delayed or incomplete; a proxy exit does not identify physical location. Request bodies and complete credentials are not recorded.
• Purchases: billing email, payment provider customer, transaction and subscription IDs, purchased items, amounts, currency, payment status and access periods. These reconcile payments and manage access, renewals and billing support. We do not store complete payment card numbers.
• Support: contact information, messages and related account or transaction information you submit, used to investigate and answer your request. Do not send passwords, complete API keys or full card numbers.

3. Providers and separate services

Relevant data are handled using hosting and infrastructure providers, including Cloudflare for website delivery and, when enabled, support archive storage. Resend delivers account and security emails when configured as the email provider. Google and GitHub process information under their own policies when you use their sign-in services.

Where AI-assisted support or translation is enabled, DeepSeek processes support messages and relevant account, billing or usage context to help answer or translate your request. Avoid including sensitive information not needed to resolve the issue.

Payment channels are under review; payments are temporarily unavailable. When enabled, the payment provider and any Merchant of Record will be identified at checkout and on the receipt. Skyviewor Data provides API access and technical support.

4. Retention

Account, purchase and support records are used while managing the service and resolving billing, security or legal issues. Retention depends on the purpose, whether access or a dispute remains active, and applicable record-keeping requirements. There is no self-service account deletion function; contact the privacy address to request deletion.

Current cleanup configuration retains hourly usage counters for approximately 90 days and daily counters for approximately 365 days. Temporary authentication records are cleaned up after expiry. Unclaimed encrypted key copies are cleared after 24 hours; this is not a separate claim step after creating an application. Older support messages can be moved into archives; archiving is not deletion.

5. Processing locations

Infrastructure and external providers may process data outside your country. Their own privacy information describes their arrangements. Contact us for further information about processing locations and safeguards applicable to your data.

6. Rights and choices

Depending on applicable law, you may request access, correction, deletion, portability or restrictions on processing, or object to processing. Email [email protected] and describe your request. We may need proportionate information to verify your identity, but do not send passwords or API keys. Some records may need to be retained to meet applicable obligations or resolve disputes. You may contact the relevant data protection authority where applicable.

Manage profile and email settings in Settings. Requests about information held independently by payment provider can also be directed to payment provider.

7. Security and browser storage

We use password hashing, access controls and protected authentication credentials. No service can guarantee absolute security. Keep keys out of browser code, public repositories and support messages. See our cookie policy for browser storage.

8. Changes

Changes to processing practices will be reflected here. Contact the privacy address for questions about this policy or a previous version.