Privacy Policy | Relsova

1. Scope

This Privacy Policy explains how Relsova handles information when you visit the public website, submit a demo, waitlist, or revenue-audit request, create or use a workspace, communicate with support, or interact with enabled product integrations.

A customer order form, data-processing agreement, integration agreement, or employment policy may add more specific terms. Where a specific agreement conflicts with this public policy, the specific agreement governs that relationship.

2. Information we collect

Business contact information such as name, work email, phone number, company, role, city, and preferred contact method.
Operating context such as team size, monthly lead volume, current tools, business type, workflow pain, requested edition, and implementation needs.
Workspace information submitted by authorized users, including leads, properties, activities, follow-ups, conversations, outcomes, users, and configuration data.
Technical and security information such as request identifiers, device and browser signals, IP-derived security hashes, audit events, authentication events, and rate-limit records.
Integration data received through customer-authorized providers, webhooks, imports, and APIs.
AI input and output required to provide enabled intelligence features, subject to product permissions, tenant scope, provider controls, and the customer agreement.

3. How we use information

Provide, secure, operate, support, and improve Relsova.
Create and administer organization-scoped workspaces, memberships, permissions, subscriptions, and usage limits.
Respond to demo, waitlist, audit, support, security, and commercial requests.
Generate decision support, summaries, matching, risk signals, suggested actions, and other enabled product functionality.
Detect abuse, prevent fraud, enforce rate limits, investigate incidents, maintain audit evidence, and comply with legal obligations.
Communicate service, security, billing, onboarding, and product information. Marketing communication is sent only where permitted and can be stopped using the available opt-out method.

4. AI and automated processing

Relsova may use approved AI providers to process authorized workspace information for decision-support features. Model output is treated as untrusted input and does not independently authorize business actions, determine tenant scope, or bypass approval controls.

Consequential actions remain subject to server-side permissions, edition access, validation, idempotency, audit, and human approval where required. Customers should review generated recommendations before relying on them.

5. Legal bases and customer instructions

Depending on the relationship and applicable law, Relsova processes information to perform a contract, take requested pre-contract steps, comply with legal obligations, protect legitimate security and business interests, or act on consent.

For customer workspace data, the customer generally determines the business purpose and authorized users. Relsova processes that data to provide the service and according to the customer agreement and documented instructions.

6. Sharing and service providers

Relsova does not sell personal information. Service providers receive only the access reasonably necessary for their contracted function and are expected to protect the information they process.

Hosting, database, authentication, monitoring, communication, payment, support, and AI providers used to operate the service.
Professional advisers, auditors, insurers, and authorities where reasonably necessary or legally required.
A successor or transaction participant in a merger, financing, acquisition, restructuring, or sale, subject to appropriate confidentiality and legal safeguards.

7. Security

Relsova uses organization scope, role-based access, server-side authorization, encryption in transit, security headers, audit logging, rate limiting, idempotency, secret-management controls, and monitored infrastructure. No system can guarantee absolute security.

Do not submit passwords, one-time passwords, payment-card data, identity documents, or confidential buyer records through public forms. Report suspected security issues to security@relsova.com.

8. Retention

Information is retained for as long as needed to provide the service, maintain security and audit evidence, resolve disputes, meet contractual and legal obligations, and support legitimate business operations. Retention periods vary by data category and customer agreement.

Public lead requests may be retained while the commercial conversation is active and for a reasonable period afterward for security, duplicate prevention, recordkeeping, and lawful follow-up.

9. International processing

Relsova and its service providers may process information in countries other than the country where it was collected. Where required, appropriate contractual, organizational, and technical safeguards are used for cross-border processing.

10. Your choices and rights

Request access, correction, deletion, restriction, portability, or objection where applicable.
Withdraw consent where processing depends on consent, without affecting prior lawful processing.
Opt out of non-essential marketing communication.
Contact the customer organization first for requests concerning data controlled by that organization. Relsova will assist the customer as required by the applicable agreement and law.

11. Children

Relsova is a business service and is not directed to children. Public forms and workspaces should not be used to submit information about children unless the customer has a lawful business purpose, appropriate authority, and a specific written agreement allowing that processing.

12. Changes to this policy

Relsova may update this policy to reflect product, provider, legal, or operational changes. The effective date will be updated, and material changes may be communicated through the website, product, or direct notice where appropriate.

1. Scope

2. Information we collect

Business contact information such as name, work email, phone number, company, role, city, and preferred contact method.
Operating context such as team size, monthly lead volume, current tools, business type, workflow pain, requested edition, and implementation needs.
Workspace information submitted by authorized users, including leads, properties, activities, follow-ups, conversations, outcomes, users, and configuration data.
Technical and security information such as request identifiers, device and browser signals, IP-derived security hashes, audit events, authentication events, and rate-limit records.
Integration data received through customer-authorized providers, webhooks, imports, and APIs.
AI input and output required to provide enabled intelligence features, subject to product permissions, tenant scope, provider controls, and the customer agreement.

3. How we use information

Provide, secure, operate, support, and improve Relsova.
Create and administer organization-scoped workspaces, memberships, permissions, subscriptions, and usage limits.
Respond to demo, waitlist, audit, support, security, and commercial requests.
Generate decision support, summaries, matching, risk signals, suggested actions, and other enabled product functionality.
Detect abuse, prevent fraud, enforce rate limits, investigate incidents, maintain audit evidence, and comply with legal obligations.
Communicate service, security, billing, onboarding, and product information. Marketing communication is sent only where permitted and can be stopped using the available opt-out method.

4. AI and automated processing

5. Legal bases and customer instructions

6. Sharing and service providers

Relsova does not sell personal information. Service providers receive only the access reasonably necessary for their contracted function and are expected to protect the information they process.

Hosting, database, authentication, monitoring, communication, payment, support, and AI providers used to operate the service.
Professional advisers, auditors, insurers, and authorities where reasonably necessary or legally required.
A successor or transaction participant in a merger, financing, acquisition, restructuring, or sale, subject to appropriate confidentiality and legal safeguards.

7. Security

Do not submit passwords, one-time passwords, payment-card data, identity documents, or confidential buyer records through public forms. Report suspected security issues to security@relsova.com.

8. Retention

Public lead requests may be retained while the commercial conversation is active and for a reasonable period afterward for security, duplicate prevention, recordkeeping, and lawful follow-up.

9. International processing

10. Your choices and rights

Request access, correction, deletion, restriction, portability, or objection where applicable.
Withdraw consent where processing depends on consent, without affecting prior lawful processing.
Opt out of non-essential marketing communication.
Contact the customer organization first for requests concerning data controlled by that organization. Relsova will assist the customer as required by the applicable agreement and law.

Relsova Privacy Policy

Choose the action you need.

1. Scope

2. Information we collect

3. How we use information

4. AI and automated processing

5. Legal bases and customer instructions

6. Sharing and service providers

7. Security

8. Retention

9. International processing

10. Your choices and rights

11. Children

12. Changes to this policy

Contact Relsova about privacy, legal, security, or account requests.

Relsova

You are not stuck.

Relsova Privacy Policy

Choose the action you need.

1. Scope

2. Information we collect

3. How we use information

4. AI and automated processing

5. Legal bases and customer instructions

6. Sharing and service providers

7. Security

8. Retention

9. International processing

10. Your choices and rights

11. Children

12. Changes to this policy

Contact Relsova about privacy, legal, security, or account requests.