Privacy policy

Cuadrabot is the controller of account, billing, product-usage, and support information used to operate this service. The legal operator and tax identity are shown on your Checkout screen and invoice. You can contact us at [email protected].

• Account details such as name, work email, company, and authentication records.
• Coarse business location such as country, region, and city from your profile or billing data.
• Private project materials, including plan PDFs, scope notes, generated quantities, marked plans, workbooks, and validation records.
• Billing references, subscription state, purchased and consumed credits, invoices, refunds, and disputes. Stripe stores complete payment-card data; Cuadrabot does not.
• Operational events such as uploads, job stages, downloads, support requests, service health, audit records, and security logs.
• With consent, first-party marketing events such as page paths, campaign tags, referring host, random browser and session identifiers, device category, browser and operating-system category, language, timezone, screen-size band, and coarse profile or billing geography when available.

We process data to create and secure accounts; verify, measure, and validate plan sets; deliver files; collect payment; manage credits and subscriptions; provide support; prevent abuse; monitor reliability; improve the product using aggregated operational evidence; and meet legal, tax, accounting, and security obligations.

Depending on context, our legal bases include performing the service contract, legitimate interests in operating and securing the service, legal obligations, and consent where required.

Project materials may be sent to contracted infrastructure and processing providers solely to provide the takeoff service. Cuadrabot does not use customer plans to train its own models without separate, explicit consent. Provider handling remains subject to the relevant business terms and data-processing commitments.

We use service providers for hosting, database and object storage, payment processing, email, monitoring, and automated analysis. We disclose only what each provider needs for its role. Where data moves outside the EEA, we use an available lawful transfer mechanism, such as an adequacy decision or approved contractual safeguards.

Account and billing records are retained while the account is active and as required for tax, accounting, dispute, and legal obligations. Once an uploaded plan passes verification, its original PDF is kept in a private source archive for customer project history, recovery, support, and dispute handling while the account is active. The archive registry records ownership, file size, page count, and a SHA-256 fingerprint. Customers may download their original plan from the project workspace and may request deletion subject to identity verification and any applicable legal hold.

Unverified or abandoned uploads are removed after 24 hours. Processor working copies and generated deliverables are removed by a scheduled process after the terminal-job retention window has elapsed; the current window is available through support. Provider recovery copies, when enabled, follow a separate restricted and finite lifecycle. Job history, billing, credit, security, and audit records may be retained or de-identified for the purposes above. A legal hold or other obligation may require longer retention.

The board has not yet approved a fixed age-based retention schedule for marketing events, so automated age-based deletion is disabled and the policy is marked for governance review. This does not override an applicable deletion right, withdrawal of consent, legal requirement, or documented legal hold. We may aggregate or anonymize older records when they no longer need to identify a browser or person.

Cuadrabot uses necessary cookies and similar storage for sign-in, security, language, consent choices, and core service functions. With applicable regional rules require opt-in, we wait for your permission before setting first-party random visitor and session IDs and a limited campaign-attribution cookie. Elsewhere these optional tools may be enabled by default, with a persistent opt-out. These let us build an internal marketing-intelligence database from the categories listed above. We do not copy arbitrary browser cookies or store raw IP addresses, payment details, or uploaded plans in that database.

We use a server-side country lookup to choose the applicable consent experience. Country.is processes the request IP transiently for that lookup and states that it does not log requests. Cuadrabot stores only a signed regional classification and coarse country code, not the IP address. If the country cannot be resolved, optional storage remains opt-in. We also honor supported Global Privacy Control signals as an opt-out.

The same regional choice controls Google Ads conversion measurement. Purchase events sent to Google include the transaction reference, currency, and amount confirmed by Stripe, but not full payment-card details. Advertising, analytics, ad-user-data, and ad-personalization consent are denied by default in opt-in regions until you choose. When denied, Google tags may send consent-aware, cookieless measurement signals with ads data redaction. When allowed, Google may read or write advertising identifiers for measurement. You can reject, allow, or later change this choice with the Cookie settings control available throughout the site. Reject and allow are presented at the same level. See Google's privacy policy for its processing and international-transfer safeguards.

Depending on your location, you may request access, correction, deletion, restriction, portability, or objection, and may withdraw consent where processing relies on it. You may also complain to your local data-protection authority. Email [email protected]. We may verify identity before acting on a request.

We use encrypted transport and provider-managed encryption at rest, private storage, tenant-level access rules, short-lived signed links, server-only credentials, checksum-backed source records, scheduled object-presence checks, audit logs, and restricted administrative access. No system is completely secure. We will update this policy when processing materially changes and will post the new effective date.