Privacy Notice

We process information submitted in beta applications and accounts, including business contact details, company information, acquisition parameters, Founder Clone preferences, and workspace membership data.

When an authorized source is connected or imported, the service processes the property, ownership, listing, valuation, rent, distress, and contact fields supplied by that source. Public-record data may include owner names and mailing addresses.

External API credentials are supplied by the workspace operator through environment configuration or encrypted workspace settings. Krova uses them only to perform requested provider and CRM actions. Secrets are never included in product analytics or audit metadata.

Owner phone and email values returned by connected contact-enrichment services are encrypted at rest. Krova stores limited source, reachability, suppression, and review metadata so operators can evaluate contact restrictions before a CRM action.

Information is used to operate accounts, correlate authorized source records, calculate scores and exit paths, generate decision-support analysis, prepare human-approved CRM payloads, provide support, secure the service, and measure aggregate funnel and product usage.

When an external AI provider is configured and enabled, Krova sends an allowlisted property and preference payload for the requested analysis. API credentials, passwords, raw contact fields, internal IDs, and unrestricted database records are not included in that AI payload. Deterministic analysis remains available when external AI is unavailable.

Krova records named product events, routes, internal account identifiers, and limited operational counts. The analytics system does not intentionally store email addresses, phone numbers, property addresses, seller data, IP addresses, API credentials, or free-form notes.

Information may be processed by hosting, database, transactional-email, licensed property-data, licensed contact-enrichment, AI, and CRM providers selected for the deployment. Krova does not use the application to sell customer or seller personal information. Information may also be disclosed when legally required or necessary to protect the service and its users.

Records are retained while needed to operate the workspace, satisfy the beta relationship, preserve required audit history, or meet legal obligations. Administrative deletion and export procedures should be coordinated with the account administrator. Krova uses access control, tenant isolation, encryption for stored integration secrets and enriched contact values, secure session cookies, request validation, rate limits, and audit logging, but no system can guarantee absolute security.

Workspace users can update account, acquisition, Founder Clone, and integration settings in the application. Requests concerning access, correction, or deletion should be submitted to the Krova AI account administrator identified in the beta invitation or service agreement.