Privacy at SalesOps

• Minimization. Collect only what the platform needs to operate.
• Purpose limitation. Use information for the purpose disclosed to Users and customers.
• Customer authority. Workspace content belongs to the customer; SalesOps acts as processor for that content.
• Transparency. Publish subprocessors, cookie categories, and retention practices.
• Restraint on sensitive data. SalesOps is not designed for health, biometric, financial-account, or government-ID information.

• Workspace-scoped access controls

  Current Control

• Cookie consent surface on the marketing site

  Current Control

• Verified subprocessor list

  Current Control

• Workspace export supported

  Current Control

• Workspace-initiated permanent deletion

  Current Control

• Documented retention schedule

  Published at /legal/data-retention.

  Current Control

• Data Processing Addendum on request

  See /legal/dpa.

  Available by Agreement

• Records of Processing Activities (Article 30) template

  In Development

Depending on where you live, you may have rights to access, correct, delete, restrict, or object to processing of your personal information; to withdraw consent; to portability; and to lodge a complaint with a privacy regulator. Requests can be sent to info@salesops.ca. If your information sits inside a customer's workspace, we will route your request to that customer.

The primary SalesOps database region is Germany. Certain approved subprocessors process information in other jurisdictions (see Subprocessors). Where required, we rely on lawful transfer mechanisms such as the EU Standard Contractual Clauses.

• Privacy Policy
• Cookie Policy
• Subprocessors
• Data Retention
• Data Processing Addendum