Trust
Security and data handling
Slideworks processes the text, figures and chart data your AI assistant puts on slides, and stores none of it. It never receives your conversation or the files you attach, and your content is not used to train models.
At a glance
| Topic | Slideworks |
|---|---|
| Data processed | Slide text, figures, chart data, layout choices and your theme. Never your chat history or attachments |
| Data stored | No slide content. The finished file is held in memory for 1 hour so you can download it, then deleted |
| Logs | Technical events and the short layout descriptions the assistant sends. No slide text, figures or chart data. Kept 30 days |
| Roles | For slide content, Slideworks acts on your instructions. For account, billing, theme and usage data, Slideworks is the controller. Your AI provider controls the conversation |
| Hosting | Render, in the US. Theme logos and cover photos on AWS in Ireland. Only the MCP server is reachable from the internet |
| Encryption | TLS 1.2 or higher for all traffic. Data encrypted at rest |
| Sign-in | Each user signs in with their own work email (OAuth 2.0 with PKCE). No shared logins or API keys. Single sign-on is not available yet |
| Model training | Your content is not used to train or evaluate models, by Slideworks or by the AI services it uses |
| Compliance | No SOC 2 or ISO 27001 report yet. We sign a data processing agreement and complete security questionnaires |
Evaluating Slideworks? Run your trial with public or illustrative material, such as a published report, until your security review is complete. Nothing in a trial requires client data.
Architecture
What is processed and for how long
Slideworks sees only what the assistant writes into a tool call: the content of the slides it is asked to build. That can include figures the assistant took from a file you attached; the file itself never leaves your AI provider.
| Data | What it contains | Kept |
|---|---|---|
| Slide content | Titles, text, figures, chart data and layout choices | In memory during the call only |
| Generated file | The .pptx and its slide specifications, so single slides can be re-rendered | In memory for 1 hour, then deleted |
| Render files | Intermediate files while a deck is built | Deleted when the render finishes, within 1 hour if it is interrupted |
| Logs | Account and organization, AI client, tool name, time, duration, outcome and errors, plus the short layout descriptions and search terms the assistant sends (up to 500 characters). No slide text, figures or chart data | 30 days |
| Layouts viewed | Which layouts each user has been shown, to protect the layout library | 30 days |
| Themes | Colors, fonts, footer text and logo files | Until you delete them or ask us to |
| Accounts | Email address, organization and access status | Until the account is closed |
Third parties
Only the hosting provider handles slide content. To pick a layout, Slideworks sends a one-line description of how each slide is built, for example bar chart with 6 bars and a side panel of 3 bullets. It can contain business terms or client names if the assistant includes them. Your content is not used to train models. The AI services may keep requests for a limited period to detect abuse, under their own terms.
| Service | Purpose | What it receives |
|---|---|---|
| Render (US) | Hosting | Slide content while a deck is built; themes, accounts and logs |
| Vercel AI Gateway (US) | Routes layout matching to the two models below | Layout descriptions |
| OpenAI API (US) | Text embeddings for layout matching | Layout descriptions |
| Typesafe AI (US) | Chooses the best layout | Layout descriptions and candidate layouts |
| Sentry (US) | Error tracking and logs | Account ID, email and organization; tool names, errors and layout descriptions |
| Amazon Web Services (Ireland) | Storage | Theme logos and cover photos |
| Stripe (Ireland) | Payments | Billing details. Slideworks does not store card details |
| logo.dev (US) | Company logos | A company's web domain, only when a slide shows its logo |
Security controls
| Area | Control |
|---|---|
| Access | OAuth 2.0 with PKCE. Every call carries a signed access token that expires after 1 hour; the server verifies it and checks your organization's access. Revoked access stops working within 60 seconds |
| Isolation | The rendering service has no public address and is reachable only from the MCP server, over the hosting provider's private network |
| Input | All slide content is validated against a strict schema. No code sent by users is executed |
| File delivery | The file is returned inside the assistant's reply. A backup download link carries a 128-bit random key and expires after 1 hour |
| Storage | Stored data is limited to themes, logos, accounts and logs, encrypted at rest |
| Logging | Request bodies, headers and cookies are excluded from error reports; slide content is excluded from logs |
| Secrets | Keys and signing secrets are held in the hosting provider's encrypted settings, never in code |
| Staff access | Limited to named Slideworks staff who need it, with multi-factor sign-in; access is logged |
Your AI provider
The conversation runs in ChatGPT or Claude under your organization's agreement with OpenAI or Anthropic, and follows its retention settings. Your admins decide who can use Slideworks: in ChatGPT Enterprise, custom apps can be enabled for one role or group and published only to them. Depending on your workspace settings, the assistant asks the user before each Slideworks call.
Contact, deletion and incidents
- Security questions, questionnaires and the data processing agreement: security@slideworks.io
- Deletion and personal data requests: info@slideworks.io. We delete themes, logos and accounts within 5 business days of a request.
- Incidents: if a security incident affects your data, we notify you without undue delay and within 72 hours of becoming aware of it.
- Vulnerabilities: report them to security@slideworks.io.
- Privacy policy: slideworks.io/privacy, Part 3 covers the MCP.
Last updated 16 November 2026