Skip to content
artifact.guru

Artifact Guru / Security and data protection

Security and data protection

How each customer's files are kept apart, what our team can see, and what happens when you delete something.

Updated 20 October 2026

Each workspace is kept apart

Every workspace gets its own database, separate from every other customer's. Its titles, versions, comments, sharing settings, view counts and search text live there and nowhere else. Every file you upload is stored under that workspace alone.

Before anything is read or changed, the app checks that the person or agent asking belongs to that workspace, or has been given access to that page. One workspace can't search, list or open another's files.

We don't currently guarantee that your data stays in a particular country or region.

Who owns it and who can open it

You keep your rights in everything you upload. Our terms only let us store, process and show it to provide the features and the sharing you choose.

New artifacts are private to your workspace. For each one you decide who else can open it: people you invite by email, who must sign in with that address; anyone with the link and a secret code; or anyone with the link. When you narrow sharing, links already given to people outside your workspace stop working within about a minute.

An agent you connect can do what you can do, in the workspace you picked when connecting it, and you can disconnect it at any time.

What our team can see

The app has no admin screen, support view or way to sign in as you. Nobody at Artifact Guru browses customers' workspaces.

The engineers who run the service can reach the underlying storage, as the people running any hosted service can. They use that access only to keep the service running and fix problems, to help when you ask us, and to investigate abuse.

Our product analytics never include file contents, file names, link names, access codes or IP addresses.

How it is protected

The app, shared links and previews are served over HTTPS. Stored files and databases are encrypted at rest with AES-256. Secrets you give an automation, like a Slack webhook address, are encrypted again by us before they are stored, and are never sent back to the app or to agents.

Files open through signed links that expire: after an hour for downloads and twelve hours for interactive previews. Shared web pages run on a separate domain, usercontent.artifact.guru, inside a browser sandbox, so a page's code can't reach your artifact.guru account.

Wrong guesses at a secret code are rate-limited, and the service is protected against denial-of-service attacks.

When you delete something

Deleting an artifact is permanent; there is no trash. Its versions, comments, sharing settings, view counts and search entries are removed, and its files are deleted from storage straight after. Deleting older versions works the same way. Cached preview pictures can take up to 30 days to expire.

To have a whole workspace or your account erased, email us and we'll do it.

Copies that people downloaded, or that an AI client kept, are outside our reach. Our providers' logs and recovery data expire on their own schedules. We don't keep separate backups of your files, so keep your own copy of anything important.

Who else handles your data

Our hosting provider runs the servers, storage and databases, sends our emails and converts iPhone photos for previews.

Clerk handles accounts, sign-in, teams and billing, with Stripe for payments. Artifact Guru never receives your password.

PostHog, hosted in the US, receives product usage events with your account's name and email.

Google Tag Manager runs only on our marketing pages, never in the app or on shared pages. Previews load open-source libraries from jsDelivr and esm.sh, which see the viewer's IP address.

Anything you connect, such as an AI agent, Slack or a webhook for Zapier, Make or n8n, receives what you or your automations send it. The privacy policy has the full details.

Contact

Artifact Guru

michael@fulcrum.rocks