DecktlySecurity & IT
Local editing. Explicit external services.
Your sign-in
Email and password to the authentication provider. Nothing else.
App updates
Checking for and downloading new versions.
Optional services
AI assistants, shared folders, and external resources in your HTML may make additional connections.
Manual editing does not upload your deck to Decktly. Comments stay inside the file, and the optional AI assistants talk to your own AI provider directly from your machine - never through Decktly. Shared folders and external resources referenced in the HTML can also use the network. Your IT team decides which services are appropriate.
Questions from IT
Frequently asked questions.
What does IT need to approve?
IT should review the app, authentication, updates, and any optional AI, sharing, or external resources used in your workflow. Your organisation decides what approval and data-protection review are required.
Where do the comments live if there's no cloud?
Inside the HTML file itself. Comments, replies, and @-mentions travel with the deck wherever it's shared, and they're invisible to anyone who opens the file in a normal browser - recipients see only the deck.
Does the browser version upload my file?
No. app.decktly.com uses your browser's built-in File System Access feature to read and write the file directly on your own disk. All editing and saving logic runs locally and produces the same on-disk result as the desktop app.
What happens when I enable an AI assistant?
The optional AI assistants use your own account and send the content they need to your selected AI provider. Review that provider’s terms and your organisation’s rules before sharing confidential material. This is separate from manual local editing.
The full local-first architecture - desktop app and browser version - is written up on the about page.
Review the workflow with your IT team.
Understand local editing and optional services before working with confidential material.