Privacy policy

• Procora · CVR 46668162
• Kingosvej 11, 1. mf., 2630 Taastrup, Denmark
• privacy@procora.ai

Procora controls its own website, account administration, billing, support and requested sales follow-up. Contact us about the relevant processing using the address above.

A business using Procora determines the purposes of its customer conversations and related records. Procora processes those records on that business’s instructions under the applicable data-processing agreement. Ask the business you contacted about its lawful basis and use of your information. You can contact that business or Procora to identify the records covered by a request. Account administration and customer-content processing are different roles.

When AI analysis is enabled, necessary bounded public excerpts and prompts are sent to the configured model provider to prepare recommendations. The report-delivery email and private report access key are excluded from that model payload. OpenCode is configured as an audit model gateway; the selected downstream model and provider matter as well. OpenAI is used by the website-assistant processing path where configured. A configured credential alone does not prove a successful model request.

Do not put sensitive or private information in prompts or drafts. Model identity and available provenance are recorded with measurements. No blanket promise of EU-only processing, zero provider retention or no model training applies to every provider/model. Read the provider and processing information and request the terms for your actual setup before sharing restricted information.

Scenario inputs calculate locally until you explicitly save them. Saved scenarios expire with the public report or private snapshot and can be deleted with it. Creating a private project stores its URL, owner-entered profile and the reports, tasks, drafts and measurements you choose to create, within your organisation’s workspace.

Saved observations have a 30-day retention limit and at most 12 report snapshots. Expiry cleanup runs during project activity or maintenance; immediate physical erasure at the exact expiry time is not promised. Profiles remain until project deletion. Backups, billing/security records and cost-accountability records can have different retention; clearing a project identifier does not necessarily remove aggregate cost records.

Explicit PageSpeed and CrUX measurements send the project URL to Google. Search Console requires a verified Procora account and your separate read-only Google authorisation. Encrypted tokens and matching property references remain while connected. A necessary HTTP-only OAuth security cookie expires after ten minutes. Disconnecting removes local tokens; you may also revoke access in Google. Previously saved observations follow project retention. Search Console access does not connect Analytics, sales, backlinks or consumer AI services.

• Messages you send and the assistant’s replies.
• A randomly generated visitor/conversation identifier and recent message history in browser storage so the conversation can survive a reload. This does not itself identify you and is not used by the product to track you across unrelated websites.
• Contact and enquiry information you choose to provide, such as name, email, phone, requested service, approximate area, timing or budget, so the business can follow up.
• Where a business has connected a supported messaging channel, the platform account identifier and display name needed to deliver replies.

Procora does not sell personal information or build cross-business visitor profiles. The product’s necessary conversation storage is separate from optional marketing-website analytics.

• Account email and a salted password hash, never a readable password.
• Business and assistant configuration, opening hours, services, area and contact details.
• Knowledge you add or authorise us to collect from public pages.
• Subscription, invoice and payment status. Stripe handles payment-card details; Procora does not store the card number.
• Operational message and AI-usage information for limits, security and workspace reporting.

Advice or pilot enquiries store the contact/business information, requested work, optional website/phone, submission reference, language and time, and the operator’s status, owner, next step and notes needed to handle the enquiry. A request is not a paid order or a marketing subscription. We retain it for the requested follow-up and any resulting engagement; ask us to close or delete an enquiry that is no longer needed. No shorter automatic expiry is promised for this separate record.

A scoped quotation pilot can store the source reference/version, customer/contact link, approved quote summary and amount/currency/dates, drafts, tasks, checks, approvals and the outcome recorded by an owner. The current pilot prepares drafts and does not send customer emails. A quote import is not consent to contact and a recorded acceptance is not proof of payment. Confidential documents and unnecessary personal information do not belong in an initial enquiry.

The provider directory explains hosting, AI, payments, email, optional Google/channel integrations, storage and consent-controlled marketing measurement. Data sent to a provider depends on the selected feature, account and configuration. A supported adapter is not automatically an active recipient for every customer.

The operational runbook identifies Hetzner EU application hosting. That does not establish EU-only downstream processing or every backup/support location. Providers may process or access information outside the EU/EEA. The applicable agreement must identify the recipient chain, locations and transfer safeguards for the actual setup. Public vendor terms are references, not proof that a particular contract, SCC or Data Privacy Framework arrangement applies to your account. Request the relevant documentation before approving restricted processing.

For processing on a customer business’s behalf, that business determines the lawful basis and gives documented instructions. For Procora’s own activities:

• Contract performance and requested pre-contract steps, Article 6(1)(b), where applicable to the account/service or request.
• Legitimate interests, Article 6(1)(f), for proportionate business-contact follow-up, operational security, preventing abuse and troubleshooting. This is not a substitute for marketing consent.
• Legal obligation, Article 6(1)(c), for required accounting/tax records.
• Consent, Article 6(1)(a), for optional analytics/marketing technologies and the separate email-marketing choice. You can withdraw it.

Request the applicable agreement from support@procora.ai, including before signup. It sets out instructions, the relevant subprocessors and what happens when processing ends. The directory is not a signed agreement or a compliance certification.

The conversation-retention setting defaults to 365 days and can be shortened by the business. Scheduled cleanup removes expired conversation/enquiry records under that setting; cleanup is not a promise of erasure at an exact second. Individual visitor deletion removes the associated conversations/messages and derived enquiry records covered by the operation. Related customer, quotation, billing, provider and backup records need their own scope checks.

Account information remains while the account is open, subject to the closure process and legally required records. Backups follow their separate rotation and retention. Removing a widget is not deletion of stored data. See deletion instructions for requests and identity checks.

• Organisation data access is isolated through database access controls.
• Stored integration tokens are encrypted.
• Traffic is encrypted in transit; passwords are stored as salted hashes.
• Access to customer records and administration is restricted. Backup protection and expiry must be assessed for the actual backup system rather than inferred from the public website.

You can request access, correction, deletion, restriction or portability where applicable, and object or withdraw consent where relevant. Rights have conditions; legal retention can still apply. Contact the responsible business or privacy@procora.ai. We respond without undue delay and normally within one calendar month; where a lawful extension or exception applies, we explain it. You can complain to Datatilsynet. See the EDPB guidance on individual rights.

Necessary login cookies support the workspace. The widget uses local conversation storage for continuity. On the marketing website, Google Analytics, Meta Pixel and Microsoft Clarity load only after the applicable choice and when configured. Private reports, audit-input pages, login and customer workspaces are excluded from this marketing tracking.

Change or withdraw your choice through “Cookie settings” in the footer. The choice is stored locally. Withdrawal can reload the page to stop previously loaded tools. Resource-calculator inputs and test notes stay in the page unless you copy/download them; consent-controlled resource events contain only an identifier and action, not those values or notes. These worksheets do not silently save to your account.

Procora is a business service, not directed at children; we do not knowingly collect information from children under 13. If the notice changes materially, we update the date and notify affected business customers through the applicable process. Questions and requests: privacy@procora.ai.