Showcase Security Overview

Showcase Security Overview

Showcase Security Overview

Showcase Security Overview

Last updated: 17 November 2026

This page answers the questions customers’ IT and security teams usually ask before they approve Showcase. It describes what we do today. Where we do not yet have something, we say so.

Hosting and data location

  • Our database runs in Stockholm, Sweden (Supabase, AWS eu-north-1), and our application servers run in Stockholm too (Vercel, region arn1).

  • Some subprocessors (for example AI and email providers) process data outside the EU, under the transfer safeguards described in our DPA. Each one is listed with its location on our subprocessor page.

Encryption

  • In transit: all traffic uses TLS (HTTPS): browser to application, application to database, and application to every third-party API.

  • At rest: the database, its backups and file storage are encrypted at rest by our hosting provider (AES-256).

  • Extra layer for credentials we hold: calendar, LinkedIn and Slack access tokens are also encrypted by our own application (AES-256-GCM) before they are stored. HeyReach API keys are readable only by our servers, and are being moved to the same encryption.

Tenant separation

  • Showcase is a multi-tenant service. Every record belongs to one customer workspace (team) or to one of its AI Twins, and access is enforced in two independent layers:

    • Application: every request is checked against the signed-in user’s workspaces before data is read or written.

    • Database: the database itself (PostgreSQL row-level security) returns only the rows of the workspaces and AI Twins the signed-in user belongs to. Even a request that bypassed our application would see nothing from another customer.

  • A signed-in browser session can read its own workspace’s data but cannot change it directly: changes go through our servers, which check access first. The only exception is a user disconnecting their own LinkedIn account.

  • Our shared database of public business contacts and companies, and internal tables (billing, API keys, usage and cost logs, webhook logs), cannot be reached from a browser session at all; only our servers read them.

  • Uploaded files (brand images, documents) are written only by our servers. Brand images are published at public links so they can appear in LinkedIn posts; nobody can list, change or delete another customer’s files.

  • Anonymous (not signed-in) access to the database is revoked entirely, and secret columns (tokens, API keys) are readable only by our servers.

  • Every change to these access rules is tested before release against real user roles in a rolled-back test, to confirm no user can see or change another workspace’s rows.

  • Showcase staff access customer data only to provide the service (support, Done For You campaign management). This includes the LinkedIn inbox conversations Showcase syncs for the Customer: campaign conversations, replies to the Customer’s own outreach, and conversations the Customer imports.

Authentication and access

  • Every user, admins included, must sign in to reach any workspace data. Sign-in is by email and password, or “Sign in with Google”, which applies the user’s own Google account security, including their Google 2-step verification.

  • Roles separate what a user can do (workspace user, workspace admin, Showcase staff).

  • Multi-factor authentication for email and password sign-in is on our roadmap; it is not available today.

  • Single sign-on with Microsoft Entra ID is not available for signing in to Showcase today. Connecting an Outlook calendar does go through Microsoft’s own sign-in and consent, so the customer’s Entra policies (MFA, conditional access, admin consent) apply to that connection.

Calendar integration

  • Supported: Microsoft 365 / Outlook (Microsoft Graph) and Google Calendar.

  • Microsoft permissions requested: Calendars.ReadWrite, User.Read (to identify the signed-in account) and offline_access (to stay connected). The app is “Showcase Calendar”, published by Showcase.ai AB as a Microsoft verified publisher.

  • Google permissions requested: calendar.readonly and calendar.events, plus basic profile and email to identify the account. Google’s OAuth verification of these permissions is approved.

  • What we read: to find free slots, only the start and end time and busy/free status of events (for Google also the user’s own accept/decline response). We do not fetch the titles, descriptions, locations or attendees of these events. For the meetings booked through Showcase, we also read that meeting’s attendee responses, to show whether the prospect accepted.

  • What we write: only the meetings booked through Showcase. We create those events and can reschedule or cancel them. We never modify or delete any other event.

  • Not free/busy only: neither Microsoft nor Google offers a free/busy-only permission that also allows creating meetings, so the read/write permission is needed for booking. The fields we fetch are limited in our code, as described above.

  • Calendar event data is used only to compute availability at the moment it is requested, is not stored, and is never sent to any AI provider.

  • The user can disconnect at any time in Showcase. Access can also be revoked from the Microsoft or Google account (for Microsoft: Entra ID, then Enterprise applications).

  • The calendar integration is included in both the Self Service and Done For You plans.

Security monitoring and incident response

  • Automated alerts go to our team in Slack: application and AI-service errors, failures of key background jobs, and an hourly check for unusual sign-in activity.

  • We have a documented incident response process: triage, containment, investigation, customer notification and follow-up.

  • If a personal data breach affects a customer’s data, we notify that customer without undue delay and no later than 48 hours after we become aware of it, so the customer can meet its own 72-hour GDPR obligation.

Business continuity and disaster recovery

  • The database is backed up automatically every day, and the last 7 daily backups are kept, encrypted, in the EU. Backups do not include files in object storage (uploaded documents and images).

  • The application runs on managed, redundant infrastructure (Supabase and Vercel), with no servers of our own to fail. The complete application is kept in version control and can be redeployed from it.

  • Our hosting providers are responsible for the physical security and redundancy of their data centres.

Key and secret management

  • Encryption keys and API secrets are stored as encrypted server-side environment variables in our hosting platform. They are never included in code sent to the browser or committed to our code repository.

  • Automated secret scanning (gitleaks) runs on every pull request and weekly across the whole repository, to catch any secret committed by mistake.

  • We have a written key and credential rotation runbook.

  • Database storage encryption keys are managed by our hosting provider.

Malware and vulnerability protection

  • We do not operate our own servers: the application runs on managed serverless infrastructure that the providers patch and protect.

  • Every pull request runs static code analysis (semgrep, including the OWASP Top 10 rule set), secret scanning and an audit for critical dependency vulnerabilities. Dependabot raises vulnerability alerts and update pull requests.

  • Uploaded files are processed, never executed.

Logging

  • Sign-in events (authentication audit log), database logs and application logs are recorded by our hosting providers. Our own records cover AI usage and key actions.

  • Logs are analysed automatically by the alerts above; we review them when investigating an incident.

  • Log retention is set by our providers’ plans and is short (days, not months). We do not run a separate long-term log archive today.

Certifications

  • Showcase.ai AB does not hold ISO 27001, ISO 27017/27018, SOC 2 or TISAX certification.

  • The providers that host customer data do: Supabase (SOC 2 Type II), Vercel (SOC 2 Type II, ISO 27001), Amazon Web Services (ISO 27001, 27017, 27018, SOC 2), and for calendars, Microsoft and Google.

Data protection

  • We sign a GDPR Data Processing Agreement (Art. 28) with customers.

  • Subprocessors are listed with their purpose and location; we give 30 days’ notice before adding one.

  • On termination, the customer’s workspace data is deleted within 30 days, unless the customer asks us to return it first or the law requires us to keep it. Anonymised usage records and our shared database of public business-contact information are kept (DPA section 9).

Company

Showcase.ai AB, org. no. 559456-4170, VAT SE559456417001.

Office: Västra Hamngatan 11, 411 17 Gothenburg, Sweden.

Registered address: c/o Jonas Karles, Toltorpsgatan 21, 431 69 Mölndal, Sweden.

Contact: aviv@theshowcase.ai