Security and key promise
Your keys are safe. In black and white.
The OS only really works once you connect it to your own systems. For that, you give us a key. Here you can read what we do with it, and especially what we do not.
Encrypted at rest
Isolated per workspace
Approve first, then execute
Encrypted traffic everywhere
Your accounts, your keys
Our promise
- Your keys are encrypted per workspace.Encrypted with AES-256-GCM, with a unique key per workspace.
- No one at SocialNow sees your key.Not in the app and not in the admin screen. It never goes back to the browser.
- Only used for what you switch on.We only use your key for the connection you switch on, in your own workspace.
- Nothing changes without your approval.The OS only writes to your systems after a proposal you approve. Every action is logged.
- Never in logs, never sent to AI.Keys are filtered out of log files and never go into a request to an AI model.
- Revoke any time, at the source.Revoke the key at Odoo, Meta, Google or LinkedIn and the connection stops. You remove your social channels key yourself in the OS.
- You hear about a breach within 24 hours.If something goes wrong with your data, we report it to you within 24 hours.
How to connect safely
- Create a separate API userCreate a separate user or key in Odoo, Meta, Google or LinkedIn for the OS. Never your own login.
- Grant only the rights that are neededLimit that user to what the OS needs to read or do. Nothing more is needed.
- Paste the key into the OSThe key goes straight into the vault, encrypted. The OS then only shows whether the connection works.
- Revoke it whenever you wantRevoke the key at the source, or ask us via privacy@socialnow.nl. You stay in control.
The official document
The key promise as a PDF, in Dutch and in English. Read more in our security measures and the Data processing agreement.