accountmade is designed to make deck creation and delivery trustworthy without turning the workflow into a mystery system. This page explains the operating boundaries teams ask about during evaluation: how workspace content is handled, how brand controls work, what the renderer outputs, and what teams should know before rollout.

1. Workspace content and source material

accountmade stores the content you choose to put into the workspace: prompts, uploaded files, pasted text, saved URLs, deck content, brand settings, and exported presentation artifacts. This material is used to create, refine, share, and export decks inside the product.

We do not use your workspace content to train public models. Content remains associated with your workspace and is retained according to the terms described in our legal documents.

2. Workspace brand-lock

The brand kit — colors, fonts, logo, and related visual tokens — is set once at the workspace level by an admin. Brand controls are enforced at render and export time so the final deck stays closer to the workspace standard.

Users can still edit the deck, but the workspace remains the source of truth for the presentation system the team is trying to preserve.

3. Rendering and the .pptx output

Decks are stored as a typed JSON intermediate representation, not as a binary. Re-rendering from the same inputs produces a byte-identical .pptx. This makes decks reproducible, branchable, and auditable.

The renderer outputs native OOXML — the same format PowerPoint uses internally. Slides remain editable in PowerPoint without re-flow. Fonts, charts, tables, and shapes are PowerPoint-native, not flattened images.

4. Access control and collaboration

Workspaces, brand kits, saved inputs, and team settings are managed through owner, admin, and member roles. Public share links are token-based and can include expiry, passwords, watermarking, and download controls depending on workspace configuration.

5. Compliance posture

• Security review materials — privacy, terms, DPA, and subprocessors are published for evaluation.
• GDPR / DPA — see the Data Processing Agreement.
• Subprocessors — published and version-controlled at Subprocessors.
• Data deletion — workspace deletion cascades through deck IR, prompt history, rendered files, and related workspace records.

6. Operational safeguards

• Brand kits and workspace content are reviewable at the workspace level.
• Renders are deterministic — a render bug produces the same wrong output every time, not random ones, which makes incident reproduction trivial.
• Vendor usage is documented publicly through the subprocessor list.
• Share and export behavior is controlled through workspace and per-share settings.

7. Related documents

For adjacent trust and compliance details, review:

• Privacy Policy
• Data Processing Agreement
• Subprocessors
• Terms of Service

Questions about security or rollout requirements can be sent to hello@accountmade.com.