Skip to content

Policies and legal information

Last Updated: November 19, 2026

At Fourdeck, the security of your business, audience data, and social media channels is our highest priority. We build our platform on defense-in-depth principles, encryption of sensitive credentials, and strict multi-tenant isolation.

1. Authentication & Social Media Authorization

Zero Social Media Password Storage

Fourdeck NEVER sees, requests, or stores your social media account passwords. All integrations (Instagram, Facebook, LinkedIn, YouTube, TikTok, Pinterest, Threads, Canva, Google Drive, Dropbox) are established using official OAuth 2.0 authorization workflows directly on the respective platforms.

AES-256 Encryption at Rest

OAuth access and refresh tokens for connected accounts are stored in our database encrypted with AES-256, never in plain text.

Two-Factor Authentication (2FA)

Two-step sign-in with an authenticator app (TOTP) or a one-time code sent by email, with a single-use recovery code as a fallback.

Session Security

Session cookies are set with the HttpOnly, Secure, and SameSite=Lax flags, so scripts running in the page cannot read them.

2. Data Isolation & Multi-Tenancy

Tenant Boundary Enforcement

Every workspace operates in strict logical isolation. All database queries, server actions, and background publishing tasks enforce workspace ID tenancy constraints, preventing Insecure Direct Object References (IDOR).

Role-Based Access Control (RBAC)

Granular permissions (Owner, Admin, Editor, Publisher, Viewer) ensure team members only access what they are explicitly authorized to manage.

3. Payment & Financial Security

Zero Card Data Handling

Fourdeck does NOT collect, store, or process payment card numbers or CVVs on our infrastructure.

Payment Infrastructure

Billing, recurring subscriptions and payment methods are handled through iyzico.

4. Infrastructure & Network Defense

DDoS Protection & Bot Checks

The site is served from Vercel's edge network, which automatically mitigates DDoS attacks at the network and application layers. The sign-up, password reset, and demo request forms are protected by Cloudflare Turnstile, and sign-in, sign-up, password reset, and verification code requests are rate limited.

HTTPS Only & HSTS

Plain HTTP is redirected to HTTPS, and connections use TLS 1.2 or 1.3. Every page is sent with a two-year Strict-Transport-Security header (includeSubDomains; preload) and hardened security headers (X-Frame-Options, X-Content-Type-Options: nosniff, Content-Security-Policy).

Signed Scheduled Publishing

Scheduled posts are delivered by Upstash QStash, and the publishing endpoint verifies each request's QStash signature before anything is published.

5. Compliance, Privacy & Vulnerability Disclosure

KVKK Compliance

As a company established in Turkey, we process personal data as a data controller under the Turkish Personal Data Protection Law (KVKK). Our Data Deletion page explains how to delete your account and connected channels in the app or request deletion by email.

RFC 9116 Security Policy

We maintain a machine-readable security policy at /.well-known/security.txt.

Responsible Disclosure

If you discover a vulnerability or security issue, please contact us immediately at iletisim@fourdeck.com. Telling us how you found it and the steps to reproduce it helps us review it faster. We confirm receipt as soon as possible and keep you informed while we investigate and fix it.

Rules for Testing

  • Use only your own account and workspace. Do not access, change or delete other users' data. If you reach it by accident, stop there and tell us.
  • Do not run denial-of-service (DoS/DDoS) tests, spam, social engineering, phishing or physical attacks.
  • Do not test the systems of connected social platforms (Meta, TikTok, Google, etc.); they run their own reporting programs.
  • Do not disclose the issue publicly before giving us reasonable time to fix it.

We will not take legal action against good-faith research that follows these rules. We do not currently run a paid bug bounty program.

Official authorization and token encryption

Social accounts are connected using OAuth 2.0 authorization. Sensitive access tokens are encrypted with AES-256. Read our policies for details on data handling.

KVKK Compliant

Personal Data Protection

AES-256 Encryption

Tokens Encrypted at Rest

Cloudflare Bot Protection

Bot Checks on Forms

OAuth 2.0

Passwords Never Stored