Legal

Data Processing Addendum

The operator terms that apply when mySolutions processes personal information in your myS1 workspace on your behalf.

Version 1.0, effective .All legal documents

This Data Processing Addendum (the “Addendum”) forms part of the myS1 Terms of Service between you and mySolutions (Pty) Ltd. It applies automatically when you accept the Terms. You do not need to sign it. If you need a signed copy, email [email protected].

It is the written contract between a responsible party and its operator that section 21 of the Protection of Personal Information Act 4 of 2013 (POPIA) requires. It is also drafted to cover the points listed in Article 28 of the EU General Data Protection Regulation (GDPR).

1. Definitions

Words defined in the Terms of Service have the same meaning here. In addition:

  • Customer Data has the meaning given in the Terms of Service.
  • Customer Personal Information means personal information contained in Customer Data.
  • Responsible party has the meaning given in POPIA. It corresponds to “controller” under the GDPR.
  • Operator has the meaning given in POPIA. It corresponds to “processor” under the GDPR.
  • Personal information has the meaning given in POPIA. It includes information about identifiable living individuals and, where POPIA applies, identifiable existing juristic persons. It corresponds to “personal data” under the GDPR.
  • Data subject means the person to whom personal information relates.
  • Security compromise means an event where there are reasonable grounds to believe that Customer Personal Information has been accessed or acquired by an unauthorised person. It corresponds to a “personal data breach” under the GDPR.
  • Sub-processor means a third party that we engage and that processes Customer Personal Information for us.
  • Data protection law means POPIA and any other law about the protection of personal information that applies to the processing concerned.

2. Roles and scope

2.1 Roles. For Customer Personal Information, you are the responsible party and we are your operator. If you process the information as an operator for someone else, you remain our point of contact, we act as your sub-operator, and you confirm that the responsible party has authorised you to appoint us.

2.2 Scope. This Addendum applies to Customer Personal Information only. Information for which we are the responsible party, such as your account and billing details, is covered by our Privacy Policy.

2.3 Your responsibilities. You are responsible for:

  • having a lawful basis for the Customer Personal Information you put into myS1 and for the instructions you give us;
  • giving data subjects the notices that data protection law requires;
  • the accuracy and quality of the information; and
  • the way you configure and use myS1, including the roles and permissions you give your users and the security settings you choose.

3. Processing on your instructions

3.1 Your instructions. We process Customer Personal Information only with your knowledge and authorisation and on your documented instructions. Your instructions are:

  • the Terms of Service and this Addendum;
  • the way you and your users configure and use myS1; and
  • any other written instruction from you that we accept.

3.2 Purpose limit. We process Customer Personal Information only to provide myS1 to you, to keep it secure, to give you support when you ask for it, and to comply with the law. We do not sell it.

3.3 Legal requirements. If a law requires us to process or disclose Customer Personal Information in another way, we will tell you before we do so, unless that law prohibits it.

3.4 Instructions we believe are unlawful. If we believe an instruction breaks data protection law, we will tell you and may hold back from following it until you confirm or change it.

4. Details of the processing

Annex 1 describes the subject matter, duration, nature and purpose of the processing, the types of personal information and the categories of data subjects.

5. Confidentiality

We treat Customer Personal Information as confidential. We give access to it only to people who need that access to provide, secure or support myS1, and we make sure they are bound by a duty of confidentiality.

6. Security

6.1 Our measures. We establish and maintain the security measures referred to in section 19 of POPIA: appropriate, reasonable technical and organisational measures to prevent loss of, damage to, unauthorised destruction of and unlawful access to Customer Personal Information. Annex 2 describes the measures in place at the effective date.

6.2 Keeping them current. We identify reasonably foreseeable risks, maintain safeguards against them, check from time to time that the safeguards work, and update them in response to new risks. We may change the measures, provided the change does not materially reduce the overall protection.

6.3 Your part. Security also depends on you. You are responsible for your users’ sign-in details and devices, for the permissions you grant, and for using the security options myS1 offers, such as multi-factor authentication.

7. Sub-processors

7.1 General authorisation. You authorise us to use sub-processors to help provide myS1. The Sub-processors page on mys1.app describes them.

7.2 Our obligations. For each sub-processor we will:

  • enter into a written agreement that requires it to protect Customer Personal Information to a standard that is no lower than this Addendum; and
  • remain responsible to you for its handling of Customer Personal Information.

7.3 Changes. Before a new sub-processor starts processing Customer Personal Information, we will update the Sub-processors page at least 30 days in advance. Where an urgent replacement is needed to keep the service secure or available, we will give as much notice as we reasonably can.

7.4 Your right to object. You may object to a new sub-processor on reasonable grounds about the protection of personal information by emailing [email protected] before it starts processing. We will discuss your concern with you in good faith. If we cannot resolve it, you may stop using the affected feature or cancel your subscription under the Terms of Service.

7.5 Services you connect yourself. A third-party service that you choose to connect to myS1 is not our sub-processor.

8. Transfers outside South Africa

8.1 Where processing happens. Some sub-processors may process Customer Personal Information outside South Africa. The Sub-processors page gives the information we publish about this.

8.2 Basis for transfers. We transfer Customer Personal Information outside South Africa only on a basis that section 72 of POPIA allows, which includes a binding agreement with the recipient that provides an adequate level of protection.

8.3 Your authorisation. You authorise these transfers as part of your instructions. You are responsible for telling your data subjects about them where data protection law requires it.

8.4 Special personal information and children’s information. The Acceptable Use Policy asks you not to put special personal information or the personal information of children into myS1. One reason is that POPIA places extra restrictions on transferring those categories to other countries.

8.5 Other jurisdictions. Annex 4 is reserved for additional terms that a law outside South Africa may require for transfers of personal information to us.

9. Security compromises

9.1 Notice to you. We will notify you immediately when there are reasonable grounds to believe that Customer Personal Information has been accessed or acquired by an unauthorised person. We send the notice to your workspace administrator’s email address.

9.2 What we will tell you. As far as we know it at the time, and adding to it as we learn more, we will tell you:

  • what happened and when;
  • the categories of information and data subjects affected;
  • the likely consequences;
  • what we have done and intend to do about it; and
  • who to contact at mySolutions.

9.3 Co-operation. We will take reasonable steps to contain the compromise and restore the integrity of our systems, and we will give you the information you reasonably need to meet your own notification duties.

9.4 Your notifications. As the responsible party, you decide whether and how to notify the Information Regulator and the affected data subjects, and you make those notifications. Our notice to you is not an admission of fault or liability.

10. Helping you meet your obligations

10.1 Requests from data subjects. myS1 gives you tools to find, correct, export and delete the records you hold about a person. If a data subject sends us a request about Customer Personal Information, we will not answer it ourselves. We will refer the person to you, or pass the request on to you, where we can identify you as the responsible party.

10.2 Further help. If you cannot deal with a request using the tools in myS1, we will give you reasonable help on request.

10.3 Regulators and assessments. We will give you reasonable help, taking into account the nature of the processing and the information available to us, with an enquiry from the Information Regulator or another regulator about Customer Personal Information, and with any assessment of the impact of the processing that data protection law requires you to carry out.

10.4 Cost. If the help you ask for goes materially beyond what myS1 provides, we may charge a reasonable fee that we agree with you first.

11. AI features

11.1 When this applies. This section applies only if you and your users use Ask Otto or another AI feature. An administrator controls which users may use them.

11.2 What is sent. When an AI feature is used, the content needed to produce the response is sent to a third-party AI model provider acting as our sub-processor. For Ask Otto this includes the question, the conversation and the records Ask Otto looks up in your workspace to answer the question. Those records are sent as they are and may contain Customer Personal Information.

11.3 Limits on what Ask Otto reads. Ask Otto reads only what the user who is asking is permitted to see in your workspace.

11.4 Masking. By default, email addresses, phone numbers in common formats, South African ID numbers and card numbers in the typed question and the conversation are replaced with placeholders before they are sent, and restored on our side. A workspace administrator can change this setting, including turning it off. The masking does not apply to records that Ask Otto looks up.

11.5 Your instruction. By using an AI feature, you instruct us to process Customer Personal Information in this way.

11.6 More detail. The page “How myS1 uses AI” on mys1.app describes the AI features in plain language.

12. Information and audits

12.1 Information. On request, we will give you the information reasonably needed to show that we comply with this Addendum.

12.2 Audits. If that information is not enough to meet a requirement of data protection law that applies to you, you may ask to audit our compliance with this Addendum. An audit:

  • needs reasonable written notice and an agreed scope and time;
  • takes place no more than once in any 12 months, unless a regulator requires it or a security compromise has affected your Customer Personal Information;
  • must not put at risk the security of myS1 or the confidentiality of other customers’ information; and
  • is at your cost, and anyone you appoint to carry it out must be bound by a duty of confidentiality.

13. Return and deletion

13.1 During the agreement. You can export Customer Data at any time using the export features in myS1.

13.2 At the end. When your workspace is deleted, at your request or under the Terms of Service, the Customer Personal Information in it is permanently removed from the live system after a waiting period.

13.3 What may be kept. We may keep Customer Personal Information where a law requires us to keep it or a legal hold applies, and only for that purpose. Deletion from the live system does not immediately remove copies held in backups. This Addendum continues to apply to anything we still hold.

13.4 Confirmation. On request, we will confirm in writing that deletion has taken place.

14. Liability

The limits and exclusions of liability in the Terms of Service apply to this Addendum. Nothing in this Addendum limits a liability that the law does not allow to be limited, or reduces the rights a data subject has under data protection law.

15. Term and order of precedence

This Addendum applies for as long as we process Customer Personal Information for you. If it conflicts with the Terms of Service about the processing of personal information, this Addendum applies first.

Annex 1: details of the processing

Item Description
Subject matter Providing the myS1 service to you under the Terms of Service
Duration From the creation of your workspace until the Customer Personal Information has been deleted under section 13
Nature of the processing Hosting, storing, organising, retrieving, displaying and transmitting information; sending email on your behalf; running the automations you set up; and, where you use AI features, sending content to an AI model provider to generate responses
Purpose To let you manage your customers, sales, communication and day-to-day operations in myS1
Categories of data subjects Your customers and prospects; your suppliers; the staff and representatives of those businesses; recipients of the email you send; your own staff where they appear in your records
Types of personal information Names; contact details such as email addresses, phone numbers and addresses; job titles; company details; notes, emails, meetings and other interactions you record; quotes, invoices and other commercial documents; bank account details you record for companies; records of email sends, opens, clicks and unsubscribes; consent and objection records; files you upload; and anything you record in custom fields
Special personal information and children’s information Not intended. The Acceptable Use Policy asks you not to put these categories into myS1

Annex 2: security measures

These are the measures in place at the effective date.

Separation between customers

  • Each customer’s data is separated at the level of the database. Every query is filtered to the signed-in customer by row-level security in the database.
  • The application connects to the database with a restricted account that cannot switch that filter off.
  • Each customer has its own organisation in the identity service, so user directories are separate.
  • The customer that a request belongs to is taken from the signed sign-in token, not from anything the browser sends.
  • Separation between customers is checked by automated tests when the software is built.

Sign-in and sessions

  • Sign-in is handled by a dedicated identity service using the OpenID Connect standard.
  • Multi-factor authentication is available with an authenticator app or a passkey. Administrators can require it for their workspace.
  • Password rules and lockout after repeated failed attempts are enforced.
  • Sessions end after a period of inactivity and have a maximum lifetime. Signing out, or an administrator forcing a sign-out, ends the session straight away.
  • Users can see their active sessions and end them.

Access control

  • Access inside a workspace is controlled by roles, groups and individual permissions.
  • API tokens are stored only in hashed form, carry their own permissions and can be revoked.
  • Access by our staff to a customer’s workspace through the support-access feature is recorded in the audit trail.

Protection of data in transit and of secrets

  • Connections to the app use HTTPS.
  • Passwords are held in hashed form by the identity service and are not stored in the myS1 application database.
  • Sensitive secrets that the app holds, such as single sign-on secrets, webhook secrets and AI provider keys, are encrypted by the application before they are stored.
  • Tokens and secrets are removed from application logs before the logs are written.

Audit trail

  • myS1 records who did what and when in each workspace.
  • The audit trail is tamper-evident: each entry carries a hash that links it to the entry before it, and an integrity check can detect edits.
  • Each customer can see only its own audit records.

Resilience against misuse

  • Requests are rate-limited per user, per customer and per network address.
  • Code and container images are scanned for known vulnerabilities.

Annex 3: sub-processors

The Sub-processors page on mys1.app describes our sub-processors and is updated as section 7 requires.

Annex 4: terms for other jurisdictions

No additional terms apply at the effective date. If a law outside South Africa requires additional terms for the transfer of personal information from you to us, for example for customers in the European Economic Area or the United Kingdom, we will agree them with you in writing and they will form part of this Annex.