Privacy policy

Who this policy covers

Artifact Guru provides the website at artifact.guru, hosted file previews and the MCP connection at mcp.artifact.guru. This policy covers people who create accounts, connect an agent, upload content or open shared links. Contact details for the service operator are below.

Information we process

Account and workspace information includes account identifiers, name, email address, workspace names, membership and invitations. Our sign-in provider, Clerk, handles authentication and session information. We do not receive your Google password when you use Google sign-in.

Content includes uploaded files, filenames, titles, tags, projects, version history, edits, extracted text for search and generated preview images. Files can contain personal information that you or your collaborators choose to include.

Sharing information includes access settings, invited email addresses, secret access codes and activity such as who changed or opened an artifact. Technical data can include IP address, browser information, request URLs, timestamps, errors and security logs. Requests you send to support include your contact details and the information you provide.

Why we use this information

We use this information to authenticate users, maintain workspaces, store and render files, search content, preserve versions, enforce sharing settings, run requested MCP actions and provide support. We also use operational information to protect the service, investigate abuse and diagnose failures.

Where data protection law requires a legal basis, processing necessary to provide an individual account is based on performance of our agreement with you; service security, business administration and support are based on legitimate interests; mandatory disclosures and records are based on legal obligations. Where consent is required for optional processing, we request it separately.

Connected AI agents and MCP

Connecting an agent authorizes it to act in the workspace you select. The service receives tool arguments and sends results to that client. Depending on the action, results may include file contents, search excerpts, titles, filenames, versions, URLs, invited email addresses, access codes or preview images. Do not connect a workspace to a client you do not trust.

The MCP connection does not automatically give Artifact Guru your entire chat history or access to your computer. We receive the information the client sends through tool calls or uploads. The AI client separately processes the information it receives under its own terms and privacy policy. Disconnecting a client does not delete files already stored in Artifact Guru or copies retained by the client.

Who can access your files

New artifacts start private to the connected workspace. Workspace members with access can use its content. Email sharing grants access to the invited addresses once they sign in; secret code sharing grants access to someone who has both the link and the code; public sharing lets anyone with the link open the content. Public files can be copied or indexed by others.

When sharing narrows (the access mode changes, a new secret code replaces the old one, or an invitation is removed), preview and download links already given to people outside the workspace stop working within about a minute. Links used by workspace members are not affected and expire after up to one hour for raw downloads and up to twelve hours for interactive previews. Copies already downloaded, or kept in a browser's cache, cannot be recalled. Membership checks for connected agents can be cached for up to five minutes.

Views of shared links

Members of a workspace can see how its shared links are used. When a link requires sign-in (private to the workspace, or shared with invited email addresses), the workspace sees the name and email address of each signed-in person who opened it, how many times, and when they first and last opened it. For every link, the workspace also sees the same aggregate counts described below: views, daily unique visitors, country, referring website and device type.

When a link can be opened without signing in (public, or protected by a secret code), the workspace sees counts only: views, daily unique visitors, the country, the referring website's domain and whether a phone or a computer was used. To count a visitor once per day we keep a keyed hash of their IP address, browser details and the date, so the value changes every day; it is deleted at the next midnight UTC. We do not store the IP address itself, and we do not identify these visitors. Opens by the workspace's own members while signed in to artifact.guru are not counted; on a workspace's own domain nobody is signed in, so every open counts there. Link previews, crawlers and browser prefetches are ignored.

View counts are deleted together with the artifact.

Service providers and external content

Cloudflare provides hosting, file storage, databases, OAuth storage, queues, preview rendering and operational infrastructure. Clerk provides account authentication and organization management. PostHog (US hosting region) receives event counts, your account identifier, name and email address, workspace identifiers, the kinds of pages opened, timings, status codes, and filtered logs and request traces. We exclude document contents, filenames, artifact and link names, access codes, signed URLs, request bodies, IP addresses and raw exception messages from PostHog telemetry. These providers process information needed to operate their services.

Our marketing pages (the home page for visitors, use cases, blog, docs and policies) load Google Tag Manager, provided by Google LLC. We use it to run Google tags, such as Google Analytics and Google Ads conversion tracking, that show us how people find the site and whether our ads work. Until you allow analytics, these tags run in Google's consent mode: they set no cookies and send Google only cookieless measurements with the page address, the referring website, your IP address and your browser and device details, which Google uses to estimate visits. If you allow analytics, the tags can also set cookies and send the identifiers stored in them. We use Google tags to measure ads, not to personalize them. Google uses this information under its own privacy policy and, depending on your Google settings, may associate it with your Google account. We do not send Google your name, email address, files or artifact names, and Google Tag Manager does not run on artifact, workspace, settings or sign-in pages. Our pages load fonts from Google Fonts. Some interactive previews load libraries from esm.sh and jsDelivr. These requests expose normal network information, such as your IP address, to those providers. Content authors can also include external resources, scripts, links or forms in an artifact; those services receive information when your browser contacts them. Review the content before entering personal information into a shared page.

We disclose information to recipients you choose through sharing or an agent connection, and may disclose information when legally required or necessary to investigate abuse and protect the service.

Storage and retention

Artifact content and versions are kept while stored in your workspace so you can access and restore them. You can delete an artifact or remove older versions. Deleting an artifact removes its application records, search entries and stored version files from active service storage; this does not erase copies held by recipients or AI clients.

Upload tickets expire after one hour. Expiry prevents further use of the ticket; cleanup of abandoned upload objects is a separate process. Operational logs, support records and provider recovery data can remain for the periods needed for security, troubleshooting, recovery or applicable legal obligations. These are not an immediate-erasure guarantee. Contact us for an account-level deletion request or details relevant to your data.

Cookies and browser storage

We use authentication cookies and browser storage for sign-in, session security, preferences and access to code-protected artifacts. A code-protected viewer session can last up to thirty days, subject to the access code and current sharing checks. Blocking essential cookies may prevent these features from working. Optional browser usage analytics run only after you select Allow analytics. They record the pages you open and the controls you use, with a random identifier kept in browser storage and linked to your account when signed in. On our marketing pages, allowing analytics also lets Google tags set cookies, such as the Google Analytics _ga cookie, which can last up to two years. Until you allow them, or if you decline, we count page views only, without cookies or browser storage: our server sends PostHog a hash of your IP address and browser details, made with a random value that we replace every day and then delete, so once the day is over the hash can't be traced back to you. With it go the kind of page, the referring website's domain, your country, and your browser and device type. Your IP address itself is not sent to PostHog. Google tags on our marketing pages also run before you choose, without cookies, as described above. Declining removes our analytics identifier and the Google cookies set on artifact.guru from your browser. You can decline or change your choice through Analytics preferences. Service-side operational diagnostics continue to help us secure and maintain the service; browser session recording is disabled.

International processing and security

Our infrastructure providers operate internationally, so information may be processed outside your country. Artifact Guru does not currently offer a contractual country-specific data residency commitment through this policy. Where required, applicable transfer safeguards must cover international processing.

We use HTTPS, authenticated workspace access and signed file URLs. Shared interactive content is served separately with browser sandbox restrictions. No internet service is completely secure; keep your own backups and avoid uploading credentials or other information unnecessary for your task.

Your choices and rights

You can update content and sharing settings, download files, delete artifacts and disconnect a client in that client’s connection settings. To request account access, correction, export, deletion or server-side connection revocation, contact us using the details below. We may need to verify your identity and authority over a workspace.

Depending on your location, you may have rights to access, correct, erase, restrict or object to processing, request portability, withdraw consent where applicable, and complain to your local data protection authority. Organizational content may require coordination with your workspace administrator.

Children and changes

The service is intended for adults and is not directed to children. Contact us if you believe a child has provided personal information. We may update this policy as the service changes and will show the revised date on this page. Material changes will be communicated through the service where appropriate.