Skip to content
Sokendi
  • Features
  • Pricing
  • Docs
  • Contact
FrançaisLoginSign Up
Menu
  • Features
  • Pricing
  • Docs
  • Contact
FrançaisLoginSign Up
Legal

Data Processing Agreement

How Sokendi processes personal information on behalf of the organizations that use it.

Last updated November 8, 2026

On this page

  1. Scope and parties
  2. Definitions
  3. Roles and instructions
  4. Confidentiality
  5. Security measures
  6. Subprocessors
  7. Requests from individuals
  8. Security incidents
  9. Deletion and return of data
  10. Information and audits
  11. Location and international transfers
  12. Liability and term
  13. Annex A: Details of processing
  14. Annex B: Security measures
  15. Annex C: Subprocessors

The short version

  • Your organization controls its data. We process it only to run the service.
  • We never sell it or use it for advertising.
  • We tell you about a security incident within 72 hours of confirming it.
  • We give 30 days’ notice before adding a subprocessor.

Scope and parties

This Data Processing Agreement (“DPA”) is between Sokendi Technologies Inc.(“Sokendi”) and the customer organization that has accepted ourTerms of Service (“Customer”). It forms part of the Terms and applies whenever Sokendi processes Customer Personal Data on the Customer’s behalf. If this DPA conflicts with the Terms on data protection, this DPA applies.

Definitions

  • Customer Personal Data: personal information in the data the Customer or its users put into the Service, including data collected by Sokendi agents from the Customer’s hosts.
  • Data Protection Laws: privacy laws that apply to the processing, such as Canada’s PIPEDA and Quebec’s Act respecting the protection of personal information in the private sector.
  • Subprocessor: a third party Sokendi engages that processes Customer Personal Data.
  • Security Incident: a confirmed breach of security leading to accidental or unlawful loss of, or unauthorized access to or disclosure of, Customer Personal Data.

Roles and instructions

The Customer controls Customer Personal Data and decides why and how it is processed. Sokendi processes it only on the Customer’s behalf and on its documented instructions. The Terms, this DPA, and the Customer’s configuration of the Service (such as which hosts run an agent, what is scanned, and which remote actions its agent policy allows) are the Customer’s complete instructions.

Sokendi will not sell Customer Personal Data, use it for advertising, or use it for any purpose other than providing and securing the Service. If Sokendi believes an instruction breaks Data Protection Laws, it will tell the Customer.

The Customer is responsible for having a lawful basis to collect the data, including giving any notice to employees and other users of monitored hosts that the law requires.

Confidentiality

Sokendi ensures that anyone authorized to process Customer Personal Data is bound by confidentiality. Access is limited to what is needed to run and support the Service. Support access to a Customer’s organization is limited to Sokendi platform administrators, uses separate temporary credentials, and is recorded in that organization’s audit log and in Sokendi’s own log of staff actions. While viewing an organization, staff can’t change its members, their roles, or anyone’s password.

Security measures

Sokendi maintains the technical and organizational measures described in Annex B and on our Security page, and may update them as long as the overall level of protection is not reduced.

Subprocessors

The Customer authorizes Sokendi to use the Subprocessors listed inAnnex C. Sokendi:

  • Has a written agreement with each Subprocessor requiring protection at least as strong as this DPA.
  • Will give at least 30 days’ notice before adding or replacing a Subprocessor, by updating Annex C and emailing organization admins.
  • Remains responsible for its Subprocessors’ performance of these obligations.

The Customer may object on reasonable data protection grounds within the notice period. If we can’t resolve the objection, the Customer may cancel the affected service.

Requests from individuals

If Sokendi receives a request from an individual about Customer Personal Data (for example, to access or delete it), Sokendi will direct them to the Customer and won’t respond itself, unless the law requires it. Sokendi will give reasonable help so the Customer can respond, including through the Service’s export and deletion features.

Security incidents

Sokendi will notify the Customer without undue delay, and in any case within 72 hours, after confirming a Security Incident affecting the Customer’s data. The notice will describe what happened, the data affected, the likely consequences, and the steps taken, and Sokendi will provide updates as more becomes known.

Sokendi will help the Customer meet its own notification obligations and keep records of Security Incidents as the law requires.

Deletion and return of data

The Customer can export its data and delete its organization from the Service at any time (any paid subscription must be cancelled first). Deletion ends all access to the organization immediately, and its data is no longer used. Sokendi keeps Customer Personal Data for30 days so it can be restored if the deletion was a mistake, then permanently deletes it automatically, including the organization’s audit log and the accounts of its users who belong to no other organization. Copies in backups age out within30 days. Sokendi may keep data longer only where the law requires, and continues to protect it under this DPA.

Information and audits

On reasonable request, Sokendi will provide the information needed to show it complies with this DPA, such as answers to security questionnaires. Further audits, such as on-site reviews, are available under an Enterprise agreement, with reasonable notice, at the Customer’s cost, and subject to confidentiality.

Location and international transfers

Customer Personal Data is stored in the location stated in ourPrivacy Policy. Some Subprocessors process data in other countries, as listed inAnnex C. Sokendi ensures any transfer is protected as Data Protection Laws require.

Liability and term

Each party’s liability under this DPA is subject to the limits in the Terms. This DPA lasts as long as Sokendi processes Customer Personal Data on the Customer’s behalf.

Annex A: Details of processing

Details of processing
Subject matterProviding the Sokendi security monitoring and scanning service.
DurationFor as long as the Customer uses the Service, plus the deletion period above. Scan results and agent data are deleted automatically at the end of the retention period of the Customer’s plan.
Nature and purposeCollecting, storing, analyzing, and displaying security data so the Customer can monitor its hosts, scan its verified domains, and detect threats.
Individuals concernedThe Customer’s users of the Service; employees, contractors, and other people who use hosts where the Customer installs the agent.
Types of personal informationNames and email addresses of Service users; IP addresses; local user account names, group memberships and sign-in session details on monitored hosts, including the source address of a sign-in and commands run with administrator rights; running processes and command lines; network connections; installed software; programs set to start automatically (services, scheduled tasks, startup items) and the accounts they run as; file paths and file hashes; approximate locations of IP addresses, worked out locally from a geolocation database; threat detection details, such as the matched file hash or behavior and the process, file, or command involved; remote actions run on hosts through the Service, who ran them, and their results; and any personal information contained in scan results.
Sensitive informationNot intended. The Customer should not use the Service to process sensitive categories of personal information.

Annex B: Security measures

  • Encryption of all data in transit with TLS, including connections between platform services (database, secrets manager, message queue).
  • Mutual TLS on the connection that delivers commands to agents; all other agent traffic over TLS, authenticated with the agent’s own credentials.
  • Per-customer database schema with row-level security enforced at the database layer.
  • Secrets and signing keys, including the agent certificate authority’s key, held in a dedicated secrets manager, not on disk or in code.
  • Role-based access control enforced by the API; passwords stored only as one-way hashes; sign-in paused after repeated failures.
  • Two-step verification (passkeys or security keys, authenticator app codes, single-use recovery codes), and re-confirmation before some sensitive actions.
  • Every request for Customer data requires a verified user sign-in or an enrolled agent’s own credentials; no shared or long-lived API keys are issued.
  • Sessions rotate their refresh token on every use, and a reused token ends the session; a password change or reset ends every session.
  • Agent enrollment tokens expire within 20 minutes and are single-use unless the Customer sets a use limit.
  • Agent reports must carry the reporting agent’s credential and signature and name only that agent and organization, so one host can’t submit data for another host or organization.
  • Signed commands to agents, verified again before delivery; remote actions run only when the Customer’s agent policy and the requesting user’s role allow them.
  • Signed, verified software updates for agents.
  • Active scanning limited to verified domains, re-confirmed every few days, and run in an isolated scan environment.
  • Business verification required before active scanning on Pro and higher plans; scannable domains limited to the plan’s allowance.
  • Automatic deletion of scan results and agent data at the end of the plan’s retention period, and of a deleted organization’s data 30 days after deletion.
  • Audit logging of account and administrative actions, including support access. The application can only add audit entries; changing or deleting them is blocked at the database layer, and only a restricted retention process removes entries older than the plan’s audit retention period (never less than 90 days).
  • Backups, and a documented incident response process.

Annex C: Subprocessors

The companies below help Sokendi provide the Service. Sokendi has a written agreement with each one, as described in the Subprocessors section above, and will give 30 days’ notice before this list changes.

Infrastructure and service providers

These companies process customer data as part of running Sokendi.

Subprocessors
CompanyPurposeData involvedLocation
OVHcloud (OVH Hosting Inc. / Hébergement OVH Inc.)Cloud servers, database hosting and encrypted backups for the Sokendi platformAll customer dataCanada (Beauharnois, Quebec); encrypted backup copy in Toronto, Ontario
Cloudflare, Inc.DNS, network security and traffic delivery; file storage for agent downloads; cookieless website analytics (Web Analytics)Website and dashboard traffic, including IP addressesUnited States (global network)
Resend (Plus Five Five, Inc.)Sending service emails (verification, password reset, notifications)Email addresses and email contentUnited States
Stripe Payments Canada, Ltd.Subscription billing and payment processingBilling contact details and organization name; card details are entered directly with Stripe and never reach SokendiCanada (company); data processed in the United States
Microsoft 365 (Microsoft Corporation)Receiving and storing email sent to Sokendi (support, privacy, security, sales)Senders’ email addresses and the content of their messagesCanada (mailboxes and files); directory and sign-in data in the United States (Microsoft Entra ID)

Threat intelligence lookups

Some scan modules check public threat intelligence sources. These services receive only the specific value being checked, during scans the Customer runs, and get no other access to Customer data.

Threat intelligence services
CompanyPurposeData involvedLocation
National Vulnerability Database (NIST)Looking up known vulnerabilities (CVEs)CVE identifiers, and the search terms of a lookup, such as keywords or product names and versionsUnited States
Have I Been Pwned (Superlative Enterprises Pty Ltd)Checking email addresses against known data breachesEmail addresses on the Customer’s verified domainsAustralia (company); data stored in the United States (Microsoft Azure)

Website only

Used on our public website only. These don’t process Customer data, and are listed for completeness.

Website services
CompanyPurposeData involvedLocation
Cloudflare, Inc. (Web Analytics)Website analytics (cookieless, aggregate only)Aggregate visit data on sokendi.com only (pages, referrers, browser and device type, country); no cookiesGlobal network (United States company)

Stay ahead of threats

Weekly security insights and zero-day alerts. No spam.

Be an early user. Unsubscribe anytime.

Sokendi

Distributed security orchestration for modern infrastructure.

Product

  • Features
  • Pricing
  • Documentation

Solutions

  • For Startups
  • Enterprise

Company

  • About
  • Contact
  • Support

Legal

  • Privacy Policy
  • Terms of Service
  • Security
  • Cookie Policy
  • Data Processing Agreement

© 2026 Sokendi Technologies Inc.

·IP Geolocation by DB-IP
Crafted for security teams worldwide