SawirPost

Security

Last updated: November 9, 2026

SawirPost holds the keys to your social accounts, so we keep what we store small, encrypt what matters, and give every person and agent only the access their role allows. This page explains how. For what we collect and why, see the Privacy Policy.

Hosting and network

  • The application, database and cache run on servers from Hetzner in Helsinki, Finland (EU), in ISO/IEC 27001-certified data centers.
  • All traffic reaches us through Cloudflare, which provides TLS, DNS and DDoS protection. The application, database and cache listen only on the server's internal interfaces and can't be reached from the internet directly.
  • Media you upload is stored in Cloudflare R2, which encrypts every object at rest.
  • The full list of companies that process data for us, and where, is on our sub-processors page.

Encryption

  • In transit: every page, API call and MCP connection uses HTTPS. Plain HTTP requests are redirected to HTTPS.
  • Platform credentials: the OAuth tokens, refresh tokens, API keys and app passwords issued by the platforms you connect are encrypted with AES-256 before they're written to the database, using a key kept outside the database.
  • Webhook secrets are encrypted the same way, and every webhook we send is signed with HMAC-SHA256 so you can verify it came from us.
  • Passwords are hashed with bcrypt. We never see your social platform passwords: connecting a channel goes through the platform's own sign-in.

Accounts and access

  • New accounts verify their email address before they can use the app. You can also sign in with Google or GitHub.
  • Each organization has roles and permissions. Every action, in the app, the REST API, the MCP server or the AI assistant, is checked against the role of the person making it.
  • API tokens and AI agent connections (MCP over OAuth) act as the person who created them and can do no more than that person's role allows. You can revoke them at any time.
  • Sign-in, API and AI endpoints are rate limited to slow down guessing and abuse.
  • Inside SawirPost, only a small number of named administrators can reach the admin tools. We access a customer account only to resolve an issue the customer raised, or to investigate abuse.

Connected channels

  • We ask each platform only for the permissions needed to publish what you schedule and to read the metrics we show you.
  • Disconnecting a channel deletes its stored tokens and stops all publishing and syncing for it. You can also revoke our access from the platform's own settings at any time.
  • You can invite someone to connect their account through a link, so they never have to share their password with your team.

AI features

  • The AI assistant and AI writing help send your prompt, and the post and account details needed to answer it, to Anthropic (Claude). Image generation uses Google (Gemini). Nothing is sent to them unless you use these features.
  • We use both under their commercial API terms, which don't allow them to train models on your content.
  • The assistant works with your role's permissions, and it can't publish, schedule or delete anything until you click Approve in the chat.

Payments

Payments are handled by Stripe, a PCI DSS Level 1 service provider. Card numbers go straight to Stripe and never touch our servers.

Certifications

SawirPost itself doesn't hold a SOC 2 report or ISO 27001 certification. The providers that host and process your data do: Hetzner (ISO/IEC 27001), Cloudflare (SOC 2 Type II, ISO/IEC 27001), Amazon Web Services (SOC 2, ISO/IEC 27001), Stripe (PCI DSS Level 1, SOC 2), Anthropic (SOC 2 Type II, ISO/IEC 27001) and Google Cloud (SOC 2, ISO/IEC 27001). If your security review needs more detail, email us.

Incidents

If a security incident affects your data, we'll tell you without undue delay: what happened, what data was involved and what we're doing about it. Where GDPR applies, we notify the relevant authority within 72 hours.

Your data

You can delete posts, media and channels at any time, and ask us to delete your account and personal data. See Retention and deletion. For government requests, see our Government Data Request Policy.

Reporting a vulnerability

If you think you've found a security issue, email support@sawirpost.com with "Security report" in the subject and the steps to reproduce it. We'll confirm we got it within three business days and keep you updated until it's fixed.

Please test only against accounts you own, don't access or change other people's data, and don't run denial-of-service, spam or social engineering tests. We won't take legal action against good-faith research that follows these rules. Our contact details are also in security.txt.