Presentations are often shared outside the group for which they were originally created. A deck goes to participants, clients, directors, colleagues or a broader audience. Precisely for this reason, presentations can contain privacy risks: a name in an example, an email address in a screenshot, a token in a URL, a social security number in test data, or sensitive information in speaker notes.
OciDeck therefore treats privacy as part of the creation and export process, not as a separate check afterwards.
OciDeck web runs in your browser
If you want to use OciDeck in the browser, go to ocideck.nl. OciDeck web is a Flutter web app. The application is downloaded to your browser and runs there. The real work happens client-side: editing, live preview, privacy checks with OciWacht, export to PDF, PPTX and HTML, and the CVSS builder.
Deck content therefore does not need to go to a backend for processing. The hosting server has no application-level insight into your deck, edits, privacy findings or exports. There is also no telemetry or analytics built in: no hidden usage measurement, no tracking code and no phone home to the OciDeck hosting server.
There are a few practical nuances:
- A webserver always sees ordinary access logs. The server that serves the app may therefore have log lines with, for example, IP address, time, requested files and user-agent. That shows that someone loaded the app, but not what that person does in OciDeck.
- For URL import, OciDeck web can use an optional fetch proxy when a source does not allow CORS access. Only in that specific case does the server see the URL you entered and fetch the bytes. The proxy is intended as a limited relay, not as content inspection of your deck.
- Other network connections are user-initiated and go to destinations you choose or configure yourself, such as optional AI assistance, WebDAV/Nextcloud, a CVE database, secmodule provisioning or a URL you import yourself.
The short version: OciDeck web processes your presentation in the browser. The host does not see deck content or edits, but as with any web app, ordinary server logs may exist, and when the fetch proxy is used, the external URL you entered is visible to that proxy.
What OciDeck controls
OciWacht searches locally for data that may be sensitive. Consider identification numbers, IBANs, payment cards, email addresses, telephone numbers, API keys, tokens, private keys, passwords, special categories of personal data and patterns that are easily missed in regular scans, such as user paths or share links with built-in access.
The check is intended as an aid. OciDeck does not decide whether something is legally allowed to be shared or not. The author remains in control and chooses what should be done with each finding.
Why this is different from black bars
Much redaction in documents is cosmetic: a black bar is placed over text, while the original information can sometimes still remain in the file, the metadata, the notes or an export layer.
OciDeck takes a different approach. Data that must be omitted for a target group is stopped at a projection boundary. This means: what is not allowed to go to the recipient does not reach the rendering or export layer. It does not belong on the screen, not in the PDF, not in the PPTX, not in HTML, not in speaker notes and not in document metadata.
This is especially important for presentations that are used in multiple formats. A full deck may be necessary for the client or researcher, while an edited version is suitable for a broader group. OciDeck supports this from one source.
Choices per slide
For each finding you can choose from practical options:
- Accept if the data is deliberately included in the presentation.
- Accept with warning if the recipient needs to see that the slide contains personal data or sensitive data.
- Omit from display and export if the data is not allowed to go to this target group.
That choice can be applied per slide or more broadly. This makes OciDeck suitable for training, incident presentations, pen test findings, legal contexts and internal briefings in which the same source may not always show the same content for everyone.
Why this is special
In OciDeck, privacy protection is close to the content. The tool has slides, notes, tables, code, graphs and exports as parts of one presentation. This allows privacy checks to take place before a presentation is shown or shared.
This makes the approach useful in professional settings:
- it reduces the chance of unintentional data leaks;
- it makes deliberate sharing choices more explicit;
- it supports different target groups from one source;
- it prevents edited data from remaining in an export file;
- it is appropriate for situations where confidentiality, audit value and reproducibility are important.
OciDeck does not guarantee that every sensitive value will always be found. No scanner can reliably promise that. The goal is clear: to reduce the chance that sensitive data will go unnoticed when a presentation is shown, shared or exported.