You've been asked to review DeckShift
Someone on the sales side wants this tool, and approving it landed on you. This page answers the questions that review actually turns on: what the software is, where the data goes, what trains on it, and how you get out. If a question is missing, a founder answers email directly.
The software, in plain terms
DeckShift is a web application. A user uploads an existing sales presentation and provides prospect input: a company URL, a written description, or a call transcript. The system researches the prospect, rewrites the deck's content for that specific company while preserving its visual theme, attaches a source and a confidence rating to generated claims, and returns a PPTX file with speaker notes. No agent installs on any machine, and the core product connects to none of your internal systems.
What enters, where it goes, what persists
1. What enters
The uploaded deck and the prospect input the user provides. Payment card data never touches our systems; billing runs through a payment processor. Content is encrypted in transit.
2. Where it goes
AI model providers process the content as our subprocessors, under contracts that bar them from training their models on it. Account identity and content are held separately.
3. What persists
Raw uploads are retained only as long as delivering the output requires, then deleted or reduced to de-identified form. The user's generated deck library persists with the account and is deleted with it.
4. What leaves
A PPTX download, returned to the user who generated it. DeckShift's own engine improvement uses de-identified, aggregated content only, with an opt-out in account settings.
These statements describe the designed behaviour of the system. The binding versions live in the privacy policy and terms of service, currently in counsel review, and the security page carries the user-facing version of the same commitments.
Couldn't we build this on an API key?
A fair question, and for a demo the answer is yes: one API call rewrites slide text convincingly. The gap opens after the demo. The production version of this job is a pipeline, not a prompt: prospect research that has to be right, claim verification with confidence scoring, theme preservation across a real corporate template, merging AI output with the edits reps make by hand, and PPTX export that survives contact with PowerPoint.
Owning that pipeline means owning its maintenance: model versions change under you, provider terms change, and the verification layer that keeps a hallucinated number off a customer-facing slide is the part a side project never gets to. Buying it makes that risk a vendor's contractual problem, reviewable on this page, instead of an internal system nobody is on the hook for.
Running it
Footprint
Browser only. Nothing to install, no extension, no agent, no network changes on your side.
Sign-in
Google SSO today. SAML is on the Enterprise roadmap and has not shipped yet; we state that here rather than imply otherwise.
Exit
Output is standard PPTX, already in your users' hands. Account deletion removes the library; privacy@deckshift.app handles deletion requests.
Reviewer questions
Does DeckShift train AI models on our decks?
Your decks never train third-party foundation models, and our AI providers are contractually barred from training on your content. DeckShift's own engine improves on de-identified, aggregated content only, with names, logos, and deal figures stripped first, and account owners can opt out in settings.
Which AI providers process our content?
AI model providers act as our subprocessors and are contractually required not to train on your content. A current subprocessor list is available by writing to privacy@deckshift.app while the public list is finalized.
What access does DeckShift need to our systems?
None. DeckShift is a web application. It reads the deck a user uploads and the prospect input they provide: a URL, a description, or a call transcript. The core product requires no access to your CRM, email, calendar, or file storage, and installs no agent.
What leaves DeckShift?
A PPTX file with speaker notes, downloaded by the user who generated it. Output goes back to that user and only that user.
How do we offboard?
Delete the account at any time in settings, or write to privacy@deckshift.app for a deletion request. Downloaded PPTX files are yours and live wherever your team saved them. De-identified aggregate data that no longer identifies you may be retained.
Do you support SAML single sign-on?
Not yet. Sign-in today is Google SSO. SAML is on the Enterprise roadmap and has not shipped, and we would rather tell you that here than have you find out in a trial.
Ask us directly
DeckShift is pre-launch and founder-run, which cuts both ways: no compliance department, and no queue between you and someone who can actually answer. Security questions go to a founder, data questions to privacy@deckshift.app.