Nimbus Takeoff Privacy Policy

Accountable organization: Nimbus Takeoff Inc.

Mailing address: 51 Guided Ct, Etobicoke, ON M9V 5G2, Canada

Privacy Officer: Privacy Officer, Nimbus Takeoff Inc.

Version: 3.2

Effective Date: October 2026

Privacy and support contact: support@nimbustakeoff.com

Privacy Summary

This summary does not replace the complete Policy below.

What Nimbus receives: Nimbus receives account, company, billing, device, usage, support, and security information, together with documents and other content customers submit to the Services.
Google sign-in: Optional Google sign-in provides basic identity information through the openid, email, and profile scopes. It does not give Nimbus access to Gmail, Google Drive, Google Photos, or Google Workspace content.
Customer Content and AI processing: Nimbus processes Customer Content to provide, secure, maintain, and support the Services and meet legal obligations. Under this version, Nimbus does not use Customer Content for generalized Nimbus model training. Any future generalized training requires a separate, affirmative opt-in before it begins.
Payments: Stripe processes payment credentials. Nimbus does not intentionally receive or store full card numbers, but it receives Stripe identifiers and payment metadata needed to operate billing and maintain records.
Cancellation and deletion: An explicitly elected ordinary end-of-term cancellation of paid Pro service, or an unconverted trial naturally reaching its previously identified scheduled terminal end, may enter the prospective six-month retention path in Section 8.1. Early trial cancellation, nonpayment, and other exceptional termination paths do not. A separately confirmed permanent company-deletion request follows a different path.
No sale; website analytics and advertising measurement are optional: Nimbus does not sell personal information or Customer Content. If you accept optional website analytics and advertising measurement, Google tags may measure visits, traffic sources, campaigns, engagement, scrolling and selected public-page controls, and we may link a Google ad click to your company's trial start and first subscription payment and report these to Google, as explained in Section 6.4. We do not use your project content or Google sign-in identity information for these purposes. Rejecting or changing your choice does not affect your access to Nimbus or your subscription.

1. Scope and Accountability

This Privacy Policy (“Policy”) explains how the accountable organization identified above (“Nimbus,” “we,” “us”) collects, uses, discloses, stores, retains, and deletes information when a customer or authorized user uses Nimbus Takeoff websites, applications, support channels, and related services (the “Services”).

Nimbus has designated the Privacy Officer identified above to oversee this Policy and Nimbus's privacy request, complaint, and breach procedures.

Nimbus Takeoff is a business service. A customer organization controls which users may access its company account and the Customer Content those users submit. The organization and its administrators may manage user access and use the company-data controls available on particular product surfaces. Individual users should direct organization-controlled requests to their company administrator first.

The Terms of Service govern Customer Content licenses, account use, billing, and the Services. This Policy describes Nimbus’s privacy practices and forms part of the agreement identified in the Terms.

2. Information Nimbus Collects

2.1 Account, User, and Company Information

Nimbus may collect:

name, email address, telephone number, job title, and account preferences;
company name, address, trade, business type, tax or billing details, and company settings;
user role, permissions, invitation status, account status, acceptance records, and authentication history;
an email/password credential stored as a one-way password hash for users who set a Nimbus password; and
basic Google identity information for users who choose Google sign-in, as described in Section 4.

Google-authenticated users may not have a usable Nimbus password unless they separately establish one.

2.2 Customer Content

“Customer Content” includes drawings, specifications, documents, images, pages, project and customer records, measurements, quantities, rates, estimates, bid information, annotations, labels, prompts, feedback, saved estimate snapshots, Project outcome records, portfolio and outcome analytics generated from Customer Content, and other material submitted to the Services or created through the Services from customer inputs.

Processing Customer Content may create derived information such as rendered pages, thumbnails, crops, extracted text, geometry, measurements, detected or classified elements, annotations, labels, embeddings or feature representations, model outputs, portfolio and outcome analytics generated from retained Customer Content, and product-quality records.

Customer Content may contain personal information, confidential business information, intellectual property, or information about third parties. Customer is responsible for having the authority required to submit and license it.

Unless Nimbus expressly enables and authorizes a compliant use in writing, the Services are not intended to receive protected health information, full payment-card or bank-account credentials, government identification numbers, export-controlled information, or other specially regulated or highly sensitive information that the Services do not require.

2.3 Billing and Transaction Information

Stripe processes payment credentials and is the source of truth for subscription and invoice state. Nimbus does not intentionally receive or store full card numbers. Nimbus may receive and retain:

Stripe customer, subscription, invoice, payment-intent, payment-method, tax, and related identifiers;
billing names, email addresses, telephone numbers, and addresses;
card brand, last four digits, card fingerprint, expiry information, and payment-method type;
subscription status, billing cadence, seat quantity, currency, tax information, invoice and payment status, and transaction timestamps; and
subscription-change, billing-support, refund, dispute, payment-failure, grace-period, and customer-support records.

Stripe processes payment information under its own privacy terms.

2.4 Usage, Device, Browser, and Security Information

Nimbus may collect account-linked and device-linked information such as:

IP address, user agent, browser and operating-system information, language, locale, time zone, and device characteristics;
login, logout, session, token, account-switch, invitation, enrollment, feature-use, page, action, error, performance, and audit events;
fraud, abuse, rate-limit, email-validation, signup, payment-risk, and security signals;
a device or browser identifier produced for enrollment-abuse and security controls; and
diagnostic logs and request metadata needed to operate, secure, debug, maintain, and support the Services.

This information is not necessarily anonymous. Nimbus may associate it with a user, company, session, request, project, or transaction where needed for the purposes in this Policy.

Nimbus may use device, IP, email-validation, payment-risk, and related signals to block, rate-limit, or route an enrollment, trial, login, or payment attempt for additional review or support.

2.5 Support, Communications, and Feedback

Nimbus may collect messages, attachments, support history, product feedback, survey responses, and other information a user sends to Nimbus. In-product assistant or AI interactions may include prompts, Customer Content, generated responses, tool activity, and feedback needed to provide, secure, maintain, troubleshoot, and support the feature. Under this version, Nimbus does not use Customer Content inside those interactions or submissions for generalized model training.

2.6 Optional Website Analytics and Advertising Measurement

If you accept optional website analytics and advertising measurement, Google Analytics and Google Ads tags on our home, Privacy, Terms and Third-Party Notices pages may collect visit and session activity, engagement, the public page address and title, marketing campaign labels, the origin of a referring website, cookie identifiers, consent settings, browser and device information, and ordinary network information such as your IP address. On the home page, we also measure selected scrolling thresholds, sign-in, preview and support-link activations, navigation choices and opening or closing the mobile menu. These controls are described with fixed action and location labels; we do not send their surrounding page text or form contents. A sign-in link activation is not a report that you successfully signed in or created an account.

We limit page information supplied by Nimbus to those public pages. Browser acquisition uses the current page's permitted campaign fields, Google ad click identifiers and aggregate advertising source and campaign identifiers, not a click retained from an earlier visit for server reporting. After permission, permitted Google advertising parameters may appear in the public page address so Google's tags can read them. We exclude other query values, fragments and free-text search terms from the page information we supply. For referral information, we send only a public website origin, excluding credentials, ports, paths, query values and fragments; we exclude local or IP-address hosts. Campaign labels must not contain personal information. The tags do not run on our sign-in, signup, password, payment or authenticated application pages. This information is not necessarily anonymous.

With this optional permission, we may also save a Google ad click identifier from the address of a Nimbus page you visit, when we saved it, and a record of your choice and the notice shown to you. Google calls these identifiers gclid, gbraid, or wbraid. They can help Google link a later event to an ad interaction; they are not necessarily anonymous.

If you then create a new company account, we may link that identifier and your choice to the company and the account that gave permission. We record the trial start and first successful subscription payment, including when they occurred and the payment's amount and currency. We also keep limited records to verify the payment and avoid reporting the same event twice. Existing company accounts are not added to this measurement later.

3. How Nimbus Uses Information

Nimbus may use information to:

create, authenticate, administer, and secure accounts and company workspaces;
provide document processing, takeoff, estimating, collaboration, billing, support, and Customer-requested AI functions;
create and present saved estimate snapshots, Project outcome history, and Company-scoped portfolio and outcome analytics from retained Customer Content;
process enrollment, subscriptions, invoices, taxes, payment actions, cancellations, renewals, authorized refunds, and related support through Stripe;
communicate service, security, billing, trial, legal, and support information;
prevent fraud, enrollment abuse, unauthorized access, and other misuse;
diagnose errors, measure performance, understand account-linked feature use, and maintain the Services;
enforce agreements, preserve evidence, protect rights and safety, comply with law, and resolve disputes;
perform customer-requested inference and analysis and the purpose-limited Customer Content processing described in Section 5;
with separate optional consent, understand traffic sources and interactions on our public website and measure whether Nimbus advertising leads to new-company trial starts and first subscription payments, as described in Section 6.4; and
perform other uses disclosed when information is collected or authorized by Customer.

Nimbus does not use a trial-warning acknowledgement as payment authorization. The enrollment terms and payment-method authorization govern automatic continuation of a trial subscription.

4. Google Sign-In Information

4.1 Information Accessed

If a user chooses Google sign-in, Nimbus requests only the standard openid, email, and profile scopes. Google’s standard UserInfo response may transiently include additional profile fields, such as a display name or profile-image URL. Nimbus selects and persists only the stable subject identifier, verified email address, and given and family names needed for account creation and access; it does not intentionally retain unselected profile fields after the sign-in exchange.

Nimbus does not request access to Gmail, Google Drive, Google Photos, Google Calendar, contacts, or Google Workspace document content through Google sign-in.

4.2 How Google Information Is Used and Stored

Nimbus uses Google identity information to authenticate the user, create or link the Nimbus account, display account identity, protect the signup and login flow, and support the account. Nimbus stores the stable Google identifier, verified email address, and given and family names needed for those purposes in its account records.

The Google access token used to verify sign-in is processed transiently and is not intentionally retained by Nimbus after the authentication exchange. During signup, a short-lived Nimbus enrollment credential derived from the verified Google exchange may briefly pass through the signup route so the user can complete the ordinary company-enrollment form; Nimbus removes it from the visible browser address after it is read.

Revoking Google access stops Google authentication unless the user authorizes it again, but does not by itself delete the Nimbus account, end a subscription, or delete Customer Content. A user may use the applicable Nimbus account or deletion process separately. Documents or other content that a user independently uploads to Nimbus are Customer Content; they are not Google user data merely because the user authenticates with Google.

4.3 Google Information Restrictions

Nimbus does not sell Google identity information, use it for advertising, include it in Nimbus model-training material, or permit service providers to use it to train their independent models. Nimbus shares it only as necessary to operate and secure the Services, comply with law, or complete a user-requested function under this Policy.

4.4 Google-Powered Address Search and Validation

Where enabled, Nimbus address-entry surfaces use Places Autocomplete and Address Validation. Authenticated Company and Project address validation uses the signed-in Nimbus session. Signup address validation is available only after a signed private-email enrollment admission or a verified Google signup continuation; authority-free public email signup uses manual entry. As a user types in an enabled search surface, the user’s browser sends the address query and a short-lived session token directly to Google and receives a suggestion list shown with the required Google Maps attribution. When the user selects a suggestion, the browser sends the selected suggestion text and the same session token to Nimbus; Nimbus verifies the applicable signed-in or signup authority before sending only those values to Google Address Validation and returning a filtered, normalized candidate for review with the same required attribution. Nimbus does not call Place Details in this flow or request a selected place identifier.

The normalized candidate remains transient until the user chooses Use this address, or chooses manual review or correction and later submits the form. Required Google Maps attribution remains visible while provider-derived candidate fields remain visible during manual correction, until save, reset, cancellation, or abandonment. Only then does Nimbus construct and retain the user-confirmed or user-corrected address in the applicable company or project record. Failed or incomplete validation does not substitute the prediction text. Nimbus does not intentionally persist the raw suggestion list, prediction text as a fallback, session token, raw Address Validation response, response identifier, geocode, verdict or component-validation metadata, provider metadata, or a Google-returned timezone field. Any stored company or project timezone is supplied or derived separately from Google address content.

Nimbus does not use Google Maps Platform content—including Places predictions and Address Validation response content—to train, test, validate, fine-tune, or otherwise improve machine-learning or artificial-intelligence models.

Use of these address features is subject to the then-current Google Maps End User Additional Terms of Service and Google Privacy Policy. Google may receive the typed query or selected suggestion text, session token, IP address, browser or server request information, and the fields needed to return suggestions and validate the address. Blocking or not using the feature leaves manual address entry available.

5. Customer Content and AI Processing

5.1 Purpose-Limited Service Processing

Nimbus processes Customer Content to provide, secure, maintain, and support the Services and meet legal obligations. This includes document rendering, OCR, customer-requested inference and analysis, collaboration, fraud and abuse prevention, troubleshooting, backup, and support. An enabled AI model may process Customer Content to answer a Customer request; that processing is not a license for secondary or generalized model training.

Under this version, Nimbus does not select, retain, or use Customer Content for generalized Nimbus model training. Any future generalized Nimbus training using Customer Content is a separate feature and may begin only after Nimbus publishes updated disclosures and obtains a distinct, affirmative opt-in. Continued use of the Services or acceptance of ordinary service processing is not that opt-in.

Nimbus does not sell Customer Content or use it for third-party advertising.

5.2 AI-Provider Training Boundary

Nimbus configures its AI providers so that Customer Content is not used to train their models. Nimbus limits provider processing to the requested service and related operational needs. Depending on the verified provider terms and account settings, providers may retain or process limited Customer Content or request information for service delivery, short-lived caching, abuse and safety monitoring, security, or legal obligations. Nimbus does not describe that boundary as Customer Content never leaving Nimbus or as universal zero retention.

Google Maps Platform content, including Places predictions and Address Validation response content, is not included in Nimbus training, testing, validation, fine-tuning, or model-improvement material. This exclusion does not reclassify independently uploaded Customer Content merely because that content contains a street address.

5.3 Ownership and Required Customer Authority

Customer retains ownership of Customer Content, including outputs covered by the definition in the Terms, subject to the limited operating license in the Terms. Nimbus owns its software, model parameters, interfaces, documentation, and other Nimbus technology; this does not transfer ownership of Customer Content to Nimbus.

Customer must have all rights, permissions, notices, consents, and lawful authority needed to submit Customer Content and permit the uses in the Terms and this Policy, including where third-party drawings, documents, people, contact details, or confidential information are involved. A customer that cannot grant those permissions must not submit that content to the Services.

6. When Nimbus Discloses Information

6.1 Within a Customer Organization

Nimbus makes account and Customer Content available to authorized users of the same customer organization according to product roles, permissions, collaboration features, and company-administrator controls. Company administrators may manage users and access company-level information.

6.2 Service Providers

Nimbus uses service providers to host, deliver, secure, maintain, and support the Services. Depending on the enabled feature and deployment, these may include:

Render for application hosting and managed infrastructure;
Amazon Web Services, including S3, CloudFront, and Textract, for storage, content delivery, and document extraction;
Stripe for payments, subscriptions, invoices, tax functions, fraud prevention, and billing support;
Google for optional sign-in; where a customer separately uses an enabled feature, mapping/place or Gemini-powered processing; and, with separate optional consent, the website analytics and advertising measurement described in Section 6.4;
third-party AI model and inference-infrastructure providers for enabled AI processing;
Postmark for transactional and authorized service/broadcast communications;
ZeroBounce, where enabled, which receives the signup email address and client IP for email validation and enrollment-abuse controls;
Sentry, where enabled, for error and performance diagnostics;
hosted database, cache, job-processing, and real-time delivery infrastructure used by Nimbus.

Browser-executed software does not become a separate data recipient merely by running locally. Under the reviewed release configuration, Nimbus serves its version-matched PDF.js worker from the Nimbus origin and uses a locally executed FingerprintJS package. Nimbus disables FingerprintJS vendor monitoring and does not send its optional installation-statistics request to openfpcdn. Applicable software licenses and notices are provided through Nimbus's Third-Party Notices surface.

Nimbus limits information sent to a provider to what is reasonably needed for the enabled function. Providers process information under their applicable terms and, where applicable, agreements with Nimbus. Some providers independently process information under their own terms, particularly Stripe and Google when a user interacts directly with their services.

Nimbus configures its AI providers so that Customer Content and Google identity information are not used to train their models, subject to the provider-processing limits described in Section 5.2.

6.3 Legal, Safety, and Business Transfers

Nimbus may disclose information when reasonably necessary to comply with law or legal process; protect customers, users, Nimbus, or others; investigate fraud, abuse, security incidents, or disputes; enforce agreements; or establish, exercise, or defend legal claims.

Nimbus may disclose or transfer information in connection with a financing, merger, acquisition, reorganization, sale of assets, insolvency, or transfer of all or part of the Services, subject to applicable law and appropriate protection of the information.

6.4 No Sale; Optional Google Website Analytics and Advertising Measurement

Nimbus does not sell or rent personal information or Customer Content. With your separate permission, we use Google Analytics and Google Ads for the limited purposes below.

Public website measurement: Google tags run only on our home, Privacy, Terms and Third-Party Notices pages after you accept optional website analytics and advertising measurement. They help us understand traffic sources, campaign performance, visits and session activity, engagement, scrolling and the selected home-page controls described in Section 2.6. We begin measuring those interactions after permission and do not replay earlier clicks or scrolling. Google receives the browser information described in Section 2.6, including network information such as your IP address, and may set or read measurement cookies. We disable Google's enhanced measurement, Google signals, advertising personalization and user-provided-data collection; Nimbus supplies only the selected public interaction events. We do not use this integration to create remarketing audiences, collect form contents, or measure activity inside the authenticated application. We do not supply names, email addresses, phone numbers, addresses, Nimbus account identifiers, device fingerprints, Google sign-in identity information, payment credentials or Customer Content to these tags.

Trial and first-payment reports: Our servers send Google the saved ad click identifier, whether your company started a trial or made its first successful subscription payment, when that happened, and a random reference that prevents duplicate reporting. We report zero value for a trial and the actual amount and currency of the first payment. Later subscription payments are not reported through this integration. These reports come only from our servers; the browser tags do not report trial starts or subscription payments.

These server reports do not include your name, email address, phone number, address, browser IP address, Nimbus account identifier, device fingerprint, Google sign-in identity information, payment credentials, or project content such as drawings, estimates and notes. We send Google a signal denying advertising personalization for these events. Google describes offline conversion imports as using restricted data processing. That description applies to these server reports; it does not mean that all Google browser processing has the same terms or limits.

Google's applicable terms and Privacy Policy govern its handling of information. See How Google uses information from sites or apps that use its services for information about Google's collection and processing. Section 7 explains your choice, and Section 8.4 explains retention and withdrawal.

7. Cookies, Browser Storage, and Similar Technology

Nimbus uses cookies, browser storage, session storage, tokens, and similar technology to authenticate users, route requests, preserve settings, support cross-tab behavior, secure enrollment, prevent abuse, and operate features.

Depending on the flow, the browser may store Nimbus access and refresh tokens, a limited user/session representation, authentication and OAuth state, an application-authentication cookie, locale and interface preferences, in-progress assistant or feature state, dismissal state, and device or enrollment-abuse identifiers. Stripe and content-delivery providers may set or use their own cookies or storage when their services are loaded.

Some state remains on the particular browser or device until Nimbus code removes it, it expires, the user clears it, or browser settings remove it. Signing out or deleting an account on one device does not guarantee that every non-sensitive preference or cached browser value is immediately removed from every other device, although expired or invalid credentials no longer authorize server access.

Cookie preferences lets you accept or reject the optional website analytics and advertising measurement described in Sections 2.6 and 6.4. We do not load these Google measurement tags or send measurement requests from them before you accept. If you reject, the tags remain blocked; we do not send Google a cookieless measurement request merely to report your rejection. Previous permission for server-side advertising measurement alone does not authorize the new browser measurement; it requires a fresh affirmative choice. We remember either choice in this browser for up to 90 days. You may be asked again after that period, if the notice changes, or if you clear browser storage or use another browser. Required sign-in, security and billing features work independently of this choice. Using Nimbus, signing in with Google, or accepting the Terms or this Policy does not give separate permission for website analytics or advertising measurement.

You can change this browser's choice later using Cookie preferences beside the Privacy link on our public pages. Rejecting turns off further browser measurement and new ad click capture. We remove the measurement cookies we can control and the saved ad click identifier unless your browser prevents the change. A request already in progress may still complete, and removing cookies does not delete information Google has already received. We keep the choice and any information needed to finish a pending withdrawal as explained in Section 8.4. If your browser prevents us from saving your choice, new capture stays off for that session and we explain that the choice could not be saved.

If you previously permitted server-side advertising measurement, asking for or accepting the additional browser purpose does not withdraw that existing permission. Accepting the additional purpose also does not extend the original choice's 90-day period. The added browser permission lasts only until the earlier of that original expiry and 90 days after the added acceptance. Choosing Reject withdraws permission for both purposes.

Clearing browser storage does not by itself withdraw permission already linked to an account. The account that originally gave permission can also withdraw it while signed in from another device by visiting our public Cookie preferences control. Contact support@nimbustakeoff.com if you no longer have the original browser or access to that account.

Blocking required cookies or browser storage may prevent authentication, billing, document viewing, or other Services from working correctly.

8. Retention, Cancellation, and Deletion

Nimbus retains information only for as long as reasonably necessary for the purposes described in this Policy, the Terms, the customer relationship, security and dispute needs, and legal or accounting obligations. Different categories follow different rules.

8.1 Six-Month Post-Subscription Retention

When a company administrator explicitly elects ordinary end-of-term cancellation of a live paid Pro subscription and that exact Stripe Subscription reaches terminal end, Nimbus retains the former customer’s operational company data before scheduled finalization. The same rule applies when an unconverted trial naturally reaches the exact scheduled terminal end that Nimbus identified for this path before that end occurred. This rule applies prospectively; Nimbus does not infer a retention window from legacy or ambiguous cancellation state.

The deadline is six UTC calendar months after the exact terminal Stripe Subscription’s ended_at time, and finalization becomes eligible at that deadline. Merely scheduling a future cancellation does not start the clock. Early trial termination, paused or unpaid service, nonpayment, material breach, fraud or security action, administrative termination, and Nimbus-initiated termination do not enter this path. A separately confirmed permanent company-deletion request under Section 8.2 also follows a different path. Retention does not itself grant application access, a complete export right, or restoration of the former Stripe subscription.

An incomplete replacement Stripe Subscription, or a not-started or active Stripe Subscription Schedule, is unresolved billing activity. Nimbus preserves the operational company data and retries the finalization check while that state remains unresolved; it does not by itself cancel finalization. If Nimbus verifies a replacement Stripe Subscription in an active or otherwise resumable state before irreversible finalization, Nimbus cancels finalization and preserves the retained operational company data under the renewed account. If the finalization check verifies that neither unresolved billing activity nor a replacement Subscription prevents finalization, Nimbus finalizes the company at or after the six-calendar-month deadline, subject to the distinctions below and applicable law.

8.2 Customer-Initiated Company Deletion

A confirmed voluntary company-deletion request immediately disables customer access and begins terminal account and billing cleanup. Voluntary company deletion follows the finalization process below instead of the six-month subscription-retention path.

Nimbus may temporarily retain inaccessible operational data during a limited internal incident-response window to investigate a suspected unauthorized deletion and, when Nimbus verifies one, perform the support-only account-recovery process described in the Terms. That temporary window is not a general retention entitlement or a customer right to reverse voluntary deletion.

At finalization, Nimbus removes ordinary operational company information, including ordinary project, customer, and company document copies, subject to technical completion and applicable law.

8.3 Information That May Survive Operational Finalization

Operational finalization does not require Nimbus to delete:

Protected records: Nimbus may retain the minimum identifying billing, tax, accounting, payment-dispute, fraud-prevention, security, litigation, legal-acceptance, and immutable-audit records reasonably required for their documented purpose and retention period.
Required temporary or technical copies: limited backups, logs, queued work, or provider copies may remain until overwritten, expired, or deleted through the applicable technical cycle, provided they remain protected and are not restored to ordinary use except for continuity, security, or legal purposes.

Saved estimate snapshots, Project outcome records, and associated estimate ledgers used to generate portfolio or outcome analytics are ordinary operational Project content. Their product immutability or auditability does not, by itself, make them protected records under this Section.

Protected records are access-restricted, excluded from generalized model training, and are not described as anonymous when a required identifier remains.

8.4 Website Analytics and Advertising Measurement Retention and Withdrawal

Google measurement cookies and Analytics records: We configure Google measurement cookies with a 90-day expiration period. The main Google Analytics identifier cookie expires within 90 days of creation without renewing on each visit. Google may refresh the Analytics session-state cookie's expiry during measurement, for up to 90 days from that activity. Browser restrictions can shorten these periods. These cookie settings are separate from how long Google retains information it has already received. We configure Google Analytics user-level and event-level retention to two months, with renewal of user-level retention on new activity turned off. Google applies deletion through its monthly processing cycle. This setting does not set a two-month limit for standard aggregated reports or for Google Ads records. Google's applicable terms and retention practices govern information it retains; withdrawing permission is not a promise that Google deletes all prior information.

Your browser choice and saved ad click: We treat a saved browser choice as valid for up to 90 days. We allow new reports using a saved ad click identifier for up to 90 days from when we captured it; revisiting a click we still hold does not extend that period. After that, no new report can be approved for sending with that identifier, although one already being processed may still be sent. We remove our server copies through scheduled cleanup. Browser expiry is checked when you next use Nimbus, so information may remain in an unused browser until then or until you clear its storage.

Withdrawing permission: Rejecting stops further browser measurement and new ad click capture in this browser immediately and removes the saved click and measurement cookies we can control if browser storage permits. We clear the associated server copy when we receive and record your withdrawal. If a connection problem delays this, the control shows that withdrawal is pending and retries automatically. Limited references needed to finish withdrawal remain until it is confirmed. If the browser will not save changes, old saved information may remain and closing it can interrupt withdrawal recovery. The control reports when your choice cannot be saved; contact us if you cannot complete withdrawal.

Once we record your withdrawal, we stop preparing new reports for Google. A report already being processed may still be sent afterward. Withdrawal does not undo information already sent to Google or confirm that Google has deleted it. Section 10 explains how to contact us about a privacy request.

Company records: We retain limited records of your choice, the trial and first payment, and reporting outcomes to honour withdrawals, verify the payment and prevent duplicate reporting. These follow the company retention and deletion rules in Sections 8.1–8.3; withdrawal does not immediately delete them. Accepting later does not restore a withdrawn account permission or cause past events to be reported again.

A small record to preserve withdrawal: We also keep a protected, one-way reference to the original permission, with only the dates the record was created and permission was withdrawn, if applicable. We retain this minimal record without a scheduled deletion date solely to prevent an old withdrawn permission from being used again, including after company measurement records have been deleted. This retention exception does not extend to ad click identifiers, payment information or Customer Content. The record is not used for advertising. We will reassess its retention if the permission mechanism changes or is retired. You can ask about its retention through Section 10.

9. Security

Nimbus uses administrative, technical, and organizational safeguards appropriate to the nature of the Services and information. These include authentication, tenant-scoped access controls, password hashing for email/password users, transport security in deployed environments, and private or signed delivery controls for protected documents.

No system is completely secure. Customers are responsible for controlling user access, protecting their devices and credentials, reviewing company permissions, and promptly reporting suspected unauthorized use. Nimbus investigates known security incidents and provides notices required by applicable law.

10. Privacy Choices and Requests

Subject to the customer organization’s authority, identity verification, applicable law, and legitimate retention needs, a person may ask Nimbus to:

provide information about Nimbus’s processing of their personal information;
provide access to or correct personal information Nimbus controls;
address a concern or challenge compliance with this Policy;
withdraw consent where consent is the applicable legal basis and withdrawal is legally available; or
delete personal information that Nimbus is not required or permitted to retain.

For optional website analytics and advertising measurement, use Cookie preferences to change your choice or contact us about access, withdrawal or deletion. Withdrawing permission does not cancel your subscription, change a billing obligation or prevent you from using Nimbus. Tell us if you no longer have the original browser or account; do not send payment credentials or sensitive project information. We will explain what we have done and any limits that apply to information already sent to Google.

Send requests to support@nimbustakeoff.com. Nimbus may need to verify the requester’s identity and authority, and may direct organization-controlled requests to the customer’s company administrator. Nimbus will respond as required by applicable law. Some requests may be limited where information concerns another person, is subject to privilege or legal restriction, is needed for security or dispute purposes, or cannot be separated from required protected records.

Google access can also be reviewed or revoked through the user’s Google account controls. Revocation does not by itself delete the Nimbus account or Customer Content.

11. International Processing

Nimbus and its service providers may process information in Canada, the United States, and other countries where the providers operate. Information processed outside a person’s province, state, or country may be subject to the laws and lawful-access regimes of that jurisdiction.

Nimbus uses contractual and operational safeguards appropriate to the service and information. This Policy does not claim that every privacy law applies to every customer; Nimbus handles requests and obligations according to the law applicable to the particular processing and relationship.

12. Children

The Services are intended for business users who are at least 18 years old. Nimbus does not knowingly offer the Services to children. If Nimbus learns that a child provided personal information contrary to this restriction, Nimbus will take appropriate steps to delete or otherwise address it.

13. Changes to This Policy

Nimbus may update this Policy to reflect changes to the Services, law, security, or business practices. Nimbus will identify the version and effective date and provide notice required by applicable law or the agreement. Where Nimbus requires explicit acceptance of a new version, continued access may be conditioned on that acceptance.

A new version does not silently replace the text attached to a previously recorded acceptance. Before a material change affecting Customer Content governs an existing customer, Nimbus will provide the notice and obtain any affirmative acceptance required by applicable law or the applicable agreement. Before introducing generalized Nimbus model training using Customer Content, Nimbus will publish updated disclosures and obtain a distinct, affirmative opt-in before that use begins; a change notice or continued use alone is not that opt-in.

14. Contact

Questions, requests, and complaints about this Policy may be directed to the Privacy Officer at support@nimbustakeoff.com. The same monitored address also accepts general product and account support.

Privacy Officer, Nimbus Takeoff Inc.<br> 51 Guided Ct<br> Etobicoke, ON M9V 5G2<br> Canada

The applicable affirmative acceptance record confirms that Customer read and understood the presented version of this Policy. Ordinary use of the Services and acknowledgement of a supplemental trial warning do not replace a required Privacy Policy acceptance record.