NimbusNexus · Privacy & Data
NimbusNexus privacy & data
Read from NimbusNexus's own page on 2026-11-10. 31 statements quoted word for word; anything the page does not say is shown as unstated, never guessed. APIs.io verifies none of it.
Role
The page states nothing on this.
Data categories
category: contact
Account information including your name, email address, billing address, and (where you are an enterprise contact) company name and role.Read from NimbusNexus's own page on 2026-11-10
category: financial
Payment information processed by our payment provider — we receive a token and the last four digits, but we do not store full payment card numbers.Read from NimbusNexus's own page on 2026-11-10
category: device
Technical data including IP address, browser type, operating system, device identifiers, and pages or API endpoints accessed.Read from NimbusNexus's own page on 2026-11-10
category: behavioral
Usage data including the resources you deploy, metering data used for billing, and aggregated performance data.Read from NimbusNexus's own page on 2026-11-10
category: communication
Communications you send us, including support tickets, abuse reports, and feedback.Read from NimbusNexus's own page on 2026-11-10
category: identifying
Identity verification information where required for sanctioned-jurisdiction screening or higher-tier accounts.Read from NimbusNexus's own page on 2026-11-10
Purposes
purpose: Service provision
To create and manage your account, provision compute and storage resources, meter usage, and provide support.Read from NimbusNexus's own page on 2026-11-10
purpose: Billing and payments
To process payments and manage disputes.Read from NimbusNexus's own page on 2026-11-10
purpose: Fraud and abuse detection
To detect, prevent, and respond to fraudulent activity, payment fraud, account takeover, and abuse of the Service.Read from NimbusNexus's own page on 2026-11-10
purpose: Security
To detect, investigate, and respond to security incidents.Read from NimbusNexus's own page on 2026-11-10
purpose: Service improvement
To understand how the Service is used in aggregate so we can improve it.Read from NimbusNexus's own page on 2026-11-10
purpose: Legal compliance
To comply with applicable law, respond to lawful requests from public authorities, and enforce our agreements.Read from NimbusNexus's own page on 2026-11-10
Retention
scope: Account informationperiod: 60 days
For the duration of your account plus the post-termination retention windows in the Terms of Service (60 days for export, then deletion within 30 days from active systems and 90 days from backups).Read from NimbusNexus's own page on 2026-11-10
scope: Billing and tax recordsperiod: seven (7) years
For at least seven (7) years after the relevant transaction, as required by US tax law and applicable local equivalents.Read from NimbusNexus's own page on 2026-11-10
scope: Security and audit logsperiod: 24 months
For up to 24 months, then deleted or anonymized.Read from NimbusNexus's own page on 2026-11-10
scope: Support communicationsperiod: three (3) years
For up to three (3) years after the ticket is resolved.Read from NimbusNexus's own page on 2026-11-10
Residency
region: United States
Fortlab is established in the United States. When you use the Service, your personal information may be transferred to, stored in, and processed in the United States and in any country where we or our sub-processors operate.Read from NimbusNexus's own page on 2026-11-10
International transfers
mechanism: adequacy
Adequacy decisions where the destination country has been recognized as providing adequate protection by the European Commission, the UK Information Commissioner's Office, or Swiss authorities.Read from NimbusNexus's own page on 2026-11-10
mechanism: SCC
Standard Contractual Clauses (the European Commission's 2021 SCCs) for transfers to countries without an adequacy decision.Read from NimbusNexus's own page on 2026-11-10
mechanism: DPF
The EU-US Data Privacy Framework, UK Extension, and Swiss-US Data Privacy Framework where the recipient is self-certified.Read from NimbusNexus's own page on 2026-11-10
Subprocessors
url: /sub-processors
Our current sub-processors list is published at /sub-processors and updated when we add or change a sub-processor.Read from NimbusNexus's own page on 2026-11-10
Data processing agreement
available: trueurl: /dpa
the Data Processing Addendum at /dpa.Read from NimbusNexus's own page on 2026-11-10
Deletion
route: Email or account dashboard request
Ask us to delete your personal information, subject to legal exceptions (e.g. tax records we are required to keep).Read from NimbusNexus's own page on 2026-11-10
Data subject rights
right: Access
Access. Request a copy of the personal information we hold about you.Read from NimbusNexus's own page on 2026-11-10
right: Correction
Correction. Ask us to correct inaccurate or incomplete information.Read from NimbusNexus's own page on 2026-11-10
right: Deletion
Deletion. Ask us to delete your personal information, subject to legal exceptions (e.g. tax records we are required to keep).Read from NimbusNexus's own page on 2026-11-10
right: Portability
Portability. Receive your personal information in a structured, commonly used, machine-readable format.Read from NimbusNexus's own page on 2026-11-10
right: Withdraw consent
Withdraw consent. Where processing is based on consent, withdraw it at any time.Read from NimbusNexus's own page on 2026-11-10
right: Object
Object to processing based on legitimate interests, including profiling and direct marketing.Read from NimbusNexus's own page on 2026-11-10
right: Restriction
Restriction. Ask us to restrict processing in certain circumstances.Read from NimbusNexus's own page on 2026-11-10
Sale or sharing
stance: prohibited
We do not sell personal information. We do not sell or rent personal information to third parties for their own marketing purposes, and we have not done so in the prior 12 months.Read from NimbusNexus's own page on 2026-11-10
Document
Download YAML · schema: API Commons Privacy & Data 0.1.0 · transcribed by claude-haiku-5-5, checked verbatim against the fetched page