S13 SupportDesk ← Back home

Privacy Policy

Last updated: 7 October 2026.

1. Who this applies to

A distinction worth getting right: this app is a data processor for the support conversations, contacts, and tickets a tenant stores here — that data belongs to the tenant and their own end customers, governed by the tenant's own privacy policy and any data processing agreement between us. This policy is about data S13 Software Solutions Inc. ("S13", "we", "us") collects as the data controller — from the people who sign up for and administer a workspace ("you"), and from visitors of this site itself.

S13 also runs its own products (for example ClearanceBay and NetQuality) on this Service, in a single S13-owned workspace. For the people who use those products and contact their support, S13 is the tenant — the organization that decides what is collected and why — and the same protections described here apply to that data. Each of those products' own privacy notices describe anything specific to it.

This policy is written against the Personal Information Protection and Electronic Documents Act (PIPEDA), which applies to S13 as a Canadian organization handling personal information in the course of commercial activity.

2. What we collect

We collect the following categories of personal information:

  • Account information: name, email address, and password (stored as a salted hash, never in plain text) for you and any agent you invite to your workspace.
  • Billing information: billing email and subscription details. Card numbers are collected and stored directly by our payment processor, Square — we never receive or store full card numbers ourselves.
  • Workspace configuration: your organization's name, branding, custom domains, and integration settings you choose to connect (e.g. Slack, WhatsApp, GitLab, Linear, Jira).
  • Usage and log data: sign-in activity, API request metadata, and error/diagnostic data used to operate, secure, and improve the Service.
  • Site visitor data: for visitors of our marketing pages who are not yet account holders, standard web server logs (IP address, user agent, requested page). We do not run third-party analytics or advertising trackers on this site.

We do not treat Customer Data (your own tickets, contacts, and messages) as covered by this section — see §1.

Two kinds of information about people who are not our customers pass through the Service on behalf of a workspace, and we describe them here so you know what they involve:

  • Visitors to a workspace's help centre: we record anonymous events (which article was read or searched for and, if the visitor chooses to answer "was this helpful?", their answer and an optional comment of up to 500 characters, which is free text and may contain whatever the visitor typed; it is shown only to workspace members who have access to analytics). No cookie is set. A visitor is counted with a one-way code generated afresh each day for each workspace, held only in temporary memory until midnight UTC and never stored, so it cannot be turned back into a person or linked from one day to the next. Crawlers, requests with no user agent and visitors who send a Global Privacy Control or Do Not Track signal are not counted as visits (a helpfulness answer a visitor chooses to give is still recorded).
  • Recipients of a workspace's campaign emails: for each recipient we record whether and when a message was opened (using a small tracking image) and which links were clicked (the link without its query string), so the workspace can see how a campaign performed. A workspace is responsible for having the recipient's consent; every campaign email carries an unsubscribe link, and a withdrawal is recorded and honoured.

3. How we use it

We use the personal information described above to:

  • Create and administer your account and workspace, and authenticate you;
  • Process payment, send billing notices, and enforce plan allowances;
  • Provide customer support and respond to inquiries you send us directly;
  • Send service-related communications (security notices, changes to these terms, planned maintenance) — these are not marketing and cannot be opted out of while your account remains active;
  • Send product and marketing communications, where you have not opted out, in accordance with applicable anti-spam law;
  • Detect, investigate, and prevent fraud, abuse, and security incidents; and
  • Meet legal, tax, and regulatory obligations.

We do not sell personal information, and we do not use it to train any AI model — see §5 for how AI providers are used.

4. Cookies and similar technologies

We use a session cookie to keep you signed in and a CSRF-protection cookie to secure form submissions — both are strictly necessary for the Service to function and are not used for tracking or advertising. We do not currently use analytics or advertising cookies on this site. If that changes, this section will be updated first, and consent will be requested where required by applicable law. The anonymous help-centre visitor counting described in §2 sets no cookie.

5. Third-party service providers (sub-processors)

We use the following categories of sub-processor to operate the Service. Each receives only the personal information necessary to perform its function, under a contract that requires it to protect that information.

  • Payment processing: Square — billing and card storage.
  • Transactional and marketing email: Postmark — delivering account, notification, and (where applicable) campaign email on your behalf.
  • File storage: S3-compatible object storage, encrypted at rest — ticket attachments you or your end customers upload, stored after a malware scan. The provider is named in the table below.
  • Network and edge: Cloudflare — all traffic to the Service passes through Cloudflare for DNS, TLS, DDoS protection and secure tunnelling to our servers, and Cloudflare issues certificates for a tenant's own verified custom domain, and Cloudflare Turnstile checks that a public form is filled in by a person. Cloudflare therefore sees request metadata (such as IP addresses) in transit.
  • Error monitoring: application error diagnostics, used to keep the Service reliable, are processed on S13's own infrastructure and are not sent to a third party.
  • AI providers: by default, AI-assisted features (triage, suggested replies, translation, knowledge-base search) run on models operated by S13 on its own hardware, so no third party receives that content. Workspaces on an eligible plan may instead configure their own AI provider (for example Anthropic, OpenAI, Google (Gemini), Cohere, or AWS Bedrock); that provider is then the workspace's own service provider, and its terms govern, not ours.
  • Communication channel integrations you choose to connect: Meta (WhatsApp Business), Slack, and similar, only when you enable that integration.
Sub-processors
Vendor Purpose Data Location
Cloudflare Network and edge: DNS, TLS, DDoS protection, certificates for a workspace's own custom domain, and Turnstile (checking that a public form is filled in by a person) Request metadata in transit (IP address, user agent, requested page); form-check tokens Global network
Postmark Email delivery: account and notification email, workspace campaigns, and inbound support email Sender and recipient addresses, and the content of the emails United States
Square Payment processing and subscription billing Billing email and subscription details; card details, which Square holds and we never receive United States and Canada
S3-compatible object storage provider (named on request) File storage: ticket attachments, after a malware scan, encrypted at rest Files that you or your end customers upload Named on request
Twilio Text messages, only for a workspace that uses SMS Recipient phone number and message text United States
Google Firebase Cloud Messaging Push notifications, only for a workspace that uses push A device's push token and the notification text United States

Locations are as stated in each vendor's published documentation.

What is removed before content reaches an AI model. When a message is saved we automatically mask payment card numbers (checked with the standard card-number test), US Social Security numbers and Canadian Social Insurance numbers. We do not remove email addresses, phone numbers or names, because they are routinely what a ticket is about, and we do not scan attachments, so AI-assisted features may process the personal information in a ticket. We do not use customer content to train any AI model. A workspace can switch off AI processing by third-party providers entirely; that setting restricts which AI is used and is not a statement about where data is stored.

A current list naming each specific sub-processor and its role, updated as this list changes, is available on request at [email protected].

6. Data retention

We retain account and billing information for as long as your workspace is active, and for a limited period after cancellation to allow for reactivation or as required for tax and accounting records. Backups are retained on a rotating schedule (recent backups daily, tapering to a small number of yearly backups kept up to 2 years) and age out of that rotation in the ordinary course, rather than being retained indefinitely.

If you close your workspace, we delete or anonymize the personal information described in §2 within 90 days of closure, except where we are required to retain it longer by law (for example, financial records) or where it persists in a backup until that backup ages out of rotation per the schedule above.

Tickets and messages. Ticket messages and attachments are kept while a workspace is active. They are deleted on request, and a workspace can erase an individual's data at any time (§7). Automated deletion 24 months after a ticket is closed is being introduced; this section will be updated when it takes effect.

Visitor and campaign records. Raw help-centre visitor events (§2) are deleted after 90 days; daily totals, which contain no comments and no individual, are kept for 400 days. Per-recipient campaign opens and clicks (§2) are kept for 90 days and then reduced to daily totals with no recipient attached, kept for 400 days. A person's engagement timeline used for lead scoring is kept for 400 days. Chat and form submissions held for a workspace's review are discarded after 14 days.

Do-not-contact records. When someone withdraws consent, complains, or an address or number hard-bounces, the workspace keeps a record of that address or number, the date and the source, even after the person's contact record is deleted, so that they are not contacted again by mistake. If the person is erased, only a one-way code (a hash) of the address or number is kept: it can no longer be read back as an address, and it can still block a future send to that same address.

7. Your rights (access, correction, deletion, export)

Under PIPEDA, you have the right to know what personal information we hold about you, to request access to it, to request correction of inaccurate information, and to withdraw consent to its use (subject to legal or contractual restrictions and reasonable notice). To exercise any of these rights over the account/billing information described in §2, contact [email protected]. We will respond within the time PIPEDA requires.

If you are an end customer of one of our tenants — someone who has submitted a support ticket or chatted with a tenant's widget — your data is controlled by that tenant, not by us; direct your request to them. Every workspace has built-in tools (in its contact settings) to export or erase an end customer's data on request, which we provide specifically so tenants can honor requests like yours.

Deleting is not erasing. When a workspace deletes a contact, the contact disappears from its lists and a returning person becomes a new contact; the old email, phone and external id are kept on the deleted record so that this works. When a workspace erases a contact, those are removed too.

What erasure does. It removes the person's name, email, phone, external id and other stored attributes; deletes their campaign opens and clicks, their engagement timeline, and notes and tasks written about them in the workspace's CRM; removes an address they typed into the chat widget from their conversations and from copies held on other contacts; reduces any do-not-contact record to a one-way code; and removes their own known email, phone, external id and name from the text of their tickets, messages (theirs and agents' replies), survey comments and related records, replacing them with "[erased]".

What erasure does not do. It cannot find personal information written in ordinary sentences (for example "my neighbour John's number is ..."), and it does not remove other people's information. It deliberately keeps the date a person unsubscribed from marketing or opted in to WhatsApp, so an erased person is never quietly made contactable again. Backups age out on the schedule in §6.

8. International data transfers

Several of the sub-processors listed in §5 operate outside Canada, including in the United States. Personal information may therefore be processed in a jurisdiction with different data protection laws than Canada's, and may become accessible to that jurisdiction's courts, law enforcement, or national security authorities. Consistent with PIPEDA's accountability principle, we use contractual protections with our sub-processors intended to provide a comparable level of protection to personal information transferred this way.

9. Security

We maintain technical and organizational measures designed to protect personal information, including encryption in transit (TLS) for all traffic to the Service, encrypted storage of sensitive credentials (API keys, integration secrets), password hashing, and access controls limiting who can reach production systems. Our current security posture is documented in more detail in COMPLIANCE.md in our source repository, including what is not yet in place — we believe in stating gaps plainly rather than implying a level of maturity we haven't reached yet.

No method of transmission or storage is completely secure. If we become aware of a breach creating a real risk of significant harm, we will notify affected individuals and the Office of the Privacy Commissioner of Canada as PIPEDA requires.

10. Children's privacy

The Service is a business tool and is not directed to children. We do not knowingly collect personal information from anyone under 16 as part of operating the Service itself. If you believe a child has provided us personal information, contact [email protected] and we will delete it.

11. Changes to this policy

We may update this policy from time to time. If a change is material, we will provide notice (such as an email to your workspace's owner, or a notice within the product) before the change takes effect. The "Last updated" date at the top of this page reflects the most recent revision.

12. Contact

Questions about this policy, or requests to exercise the rights described in §7, can be sent to [email protected], or by mail to:

S13 Software Solutions Inc.
1460 Chevrier Blvd, Unit 200
Winnipeg, MB, Canada R3T 1Y6