Security and POPIA

Your business data, protected and accounted for

How your data is kept apart from every other business, who can reach it, what is put on record, and how requests about personal information are handled.

Each myS1 customer is kept apart in the database

  • Your data is separated in the database itself

    Every query is filtered to your business inside the database itself, not only by application code.

  • The application cannot switch the separation off

    myS1 connects to the database with a restricted account that has no power to bypass those rules. A new session can see no customer data at all until it is tied to a signed-in customer.

  • A separate user directory per customer

    Each customer gets its own organisation in the identity provider. Which customer a request belongs to is read from the signed sign-in token, never from anything the browser sends.

  • Tested on every change

    Automated tests with two separate customers check that neither can reach the data of the other.

Who can sign in to myS1, and what they can do

Multi-factor sign-in
Authenticator apps, passkeys and security keys, and one-time codes by email. An admin can require a second factor for everyone, and the requirement is enforced on the server.
Password rules and lockout
A minimum length with mixed character types, and lockout after repeated failed attempts. You can tighten the rules for your own workspace; nobody can loosen them below the platform floor.
Sessions you can see and end
Each user can see their active sessions and sign them out. Signing out, or an admin forcing a sign-out, ends the session straight away. Idle sessions time out.
Roles, groups and permissions
Access is granted through roles, groups and granular permissions. A second authorisation check runs at the API gateway before a request reaches the application.
API tokens kept as hashes
API tokens are stored only as hashes, carry their own permission list, can expire and can be revoked.

One audit trail of who did what in myS1

  • An audit trail of who did what

    Sign-ins, changes and exports are recorded with the person, the action, the record, the time and the context.

  • Tamper-evident records

    Each audit entry carries a hash linked to the entry before it, so an integrity check can detect an edit.

The tools in myS1 for your duties under POPIA

myS1 includes a queue for data-subject requests, per-contact consent records, retention periods with automated deletion, one-click unsubscribe on marketing email and an audit trail. You remain the responsible party for the personal information you put into myS1; mySolutions acts as your operator.

A queue for data-subject requests
Your privacy officer can log, assign and track requests to access, export, correct, restrict or erase personal data. Each request gets a due date, and closing one requires a record of how it was carried out.
Users can get their own data
Any user can download a copy of their own data and file a privacy request from their account.
Retention set by policy
Each type of data has a retention period, and an automated job deletes or anonymises data when the period ends. You can shorten the periods for your workspace. Legal holds pause deletion.
Unsubscribe is honoured
Every marketing email sent from myS1 carries a one-click unsubscribe, and an unsubscribe blocks future marketing email to that address.
Consent recorded per contact
Record the marketing consent of each contact and the lawful basis for it, with a history of changes.

How Ask Otto handles your data

  • Ask Otto reads with your access only

    Otto looks up records through the same permission checks as the rest of myS1, as the person asking, inside your workspace only.

  • Identifiers are masked before a question leaves myS1

    Email addresses, phone numbers, South African ID numbers and card numbers in your question are replaced with placeholders before it leaves myS1, and put back by myS1 when the answer returns. The records Otto looks up to answer are processed by our AI model provider.

  • Nothing changes without approval

    Otto proposes changes and a person approves them. It never sends an email or books a meeting without an approval for that specific action.

  • Admins stay in control

    Admins decide which users may use AI and can cap monthly AI spend. AI usage is logged per user and feature.

Read how Ask Otto works

Encryption in transit, stored secrets and rate limits

Encrypted in transit
All traffic to the app is served over HTTPS, with security headers set at the gateway.
Secrets encrypted before storage
Secrets the app holds on your behalf, such as sign-on and webhook secrets, are encrypted before they are stored. Passwords are held by the identity provider, hashed, and never in the application database.
Rate limits
Requests are rate-limited per user and per customer, with a separate limit per address at the edge.

Questions about security

Another question about myS1? Write to [email protected].

How is my data kept separate from other customers?
In the database itself. Every query is filtered to your business there, and the application connects with an account that cannot bypass that rule.
Can I require two-step sign-in for my team?
Yes. An admin can require a second factor for everyone. Authenticator apps, passkeys and email codes are supported.
How does Ask Otto keep my data safe?
Otto works inside your workspace, with the access of the person asking and nothing more. Email addresses, phone numbers, ID numbers and card numbers in your question are masked before it leaves myS1 and put back when the answer returns. The records needed to answer are processed by our AI model provider, and nothing in myS1 is changed until a person approves it.
Can Ask Otto see records I cannot?
No. Otto works with the access of the person asking and reads through the same permission checks as the rest of myS1.

The legal documents behind this page

The terms, the privacy policy and the operator terms are published in full.

See all legal documents

  • Terms of Service

    The agreement between you and mySolutions for using myS1: plans, billing, your data, and what each of us is responsible for.

    Version 1.0, effective
  • Refund, Cancellation and Delivery Policy

    How myS1 is delivered when you subscribe, how to cancel, and when we refund a payment.

    Version 1.0, effective
  • Privacy Policy

    What personal information mySolutions collects through mys1.app and myS1 accounts, why we use it, who receives it, and the rights you have under POPIA.

    Version 1.0, effective
  • Data Processing Addendum

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

    Version 1.0, effective
  • Acceptable Use Policy

    The rules everyone must follow when using myS1, including rules for sending email, restricted kinds of data, AI use and security.

    Version 1.0, effective
  • Cookie Notice

    Which cookies and similar technologies are used on mys1.app and in the myS1 app, and the choices you have.

    Version 1.0, effective
  • How myS1 uses AI

    A plain-language explanation of Ask Otto and the other AI features in myS1: what they read, what is sent to an AI model provider, and what stays under your control.

    Version 1.0, effective