Your client data, our highest priority.

Agencies manage sensitive client data through Senly. That's why security isn't a feature we add later — it's built into the foundation of the platform.

How we do it

Six pillars of responsible platform design.

Encryption at rest & in transit

All data is stored encrypted (AES-256-GCM) and transmitted over TLS 1.3. Social-media cookies are additionally bound to the agency they belong to.

Multi-tenant isolation

Every data query is scoped per agency (tenant); an agency can only access its own data.

Privacy & GDPR

A data processing agreement per agency, sub-processors in the EU and US (under the EU-US Data Privacy Framework/SCCs), and data-rights workflows in-product (export, delete, access).

Role-based access & audit logs

Granular roles per team member, an audit log of every critical action (SyncLog), JWT sessions with a 30-day lifetime and automatic rotation.

Rate limiting & abuse prevention

Login attempts, API routes and public endpoints are rate-limited. Brute-force, scraping and DoS attempts are stopped automatically.

Responsible disclosure

Security researchers can report vulnerabilities directly via security@senly.io. We confirm within 24 hours and patch critical issues within 72 hours.

Standards

Standards we adhere to.

AVG / GDPR

EU regulation 2016/679

TLS 1.3

Modern transport security

AES-256-GCM

At-rest encryption

bcrypt

Password hashing

HSTS

2-year HTTP Strict Transport

CSP

Content Security Policy headers

Senly Connector — security in detail

The optional Chrome extension has access to social-media session cookies. That is sensitive stuff. How we keep it watertight:

  • Opt-in per client: the extension only sends session cookies to Senly after you explicitly click "Connect" in a client profile. Before a growth run it checks in your own browser that the right account is logged in; no cookies are sent to Senly for that.
  • Bound to your agency: cookies are encrypted with AES-256-GCM, with your agency as a fixed part of the encryption. Agency A's encrypted cookies therefore cannot be opened as agency B's. The key is kept separate from the database.
  • No passwords: we only read session tokens from already-active sessions. Client passwords never touch our system.
  • Instantly revocable: "Disconnect" removes that account's encrypted cookies immediately. On LinkedIn, a client's personal profile and company page share one login: disconnect both to remove that session everywhere.
  • Open source extension: the Connector code is publicly inspectable, so researchers can verify that the extension does what we claim.

Incident response

In the event of a data breach that poses a risk to the individuals involved, we notify the agency in question within 24 hours of discovery. The agency is responsible for reporting to the Dutch Data Protection Authority within 72 hours, and we support with technical forensics and logs.

Reporting a vulnerability

Found something? We appreciate responsible disclosure. Send details to security@senly.io — preferably PGP-encrypted with our key (available on request). We confirm within 24 hours and keep you posted on the fix.

Questions about security?

We are happy to help you think it through.

Compliance questions, DPIA input, a security audit for enterprise clients? Book a call with our security team.