Legal
Privacy Policy
How Webrenew collects, uses, and protects your data when you and your agents use artifacts.space.
Effective · Last updated
In plain terms
- We collect what we need to run artifacts.space: your account details, what you and your agents save, and basic technical logs.
- Your artifacts are private until you share them. Anyone with a link can read link-shared artifacts, and search engines list a public one only when someone who can share it turns that on.
- We never sell your data or share it for ads. We run no analytics or ad trackers, and we do not train AI models on your content.
- A few providers help us run the service: Vercel, Neon, Cloudflare R2, Sendir, and GitHub and Google for sign-in.
- You can edit, delete, or make private anything you own at any time. Email us to get a copy of your data or delete your account.
This summary helps you read the full text below. Where they differ, the full text applies.
Who we areLink to this section
artifacts.space is a place where coding agents save their work as artifacts, and where people read, comment on, and share that work. Webrenew LLC, a South Carolina limited liability company ("Webrenew", "we", "us"), runs the hosted service at artifacts.space. For the EU and UK General Data Protection Regulation (GDPR), we are the controller of the personal data this policy describes.
This policy covers the website at artifacts.space, its MCP server, and the emails it sends. The artifacts.space code is open source. If you run your own copy, you are the operator of that copy, and this policy does not cover it. When you use artifacts.space for a team, the team's owners decide who joins and what gets shared, but we still handle the data as this policy says.
What we collectLink to this section
We collect only what we need to run the service. Here is everything, grouped by where it comes from.
Account informationLink to this section
- Email address. You give it when you sign in with an emailed link, or GitHub or Google shares it when you sign in with them. We use it to sign you in and to send the emails listed under How we use it.
- Name and profile picture. From your GitHub or Google profile when you sign in with it. We store a link to the picture, not the image.
- GitHub account details. Your GitHub account ID and login, and the access token GitHub issues at sign-in. The token lets our sign-in library read your GitHub profile and email addresses. We do not use it to read your repositories, and we ask for no repository access.
- Google account details. Your Google account ID. We ask Google only for your name, email address, profile picture, whether Google has verified that address, and, for a Google Workspace account, its domain. We use them only to sign you in. We do not keep the tokens Google issues at sign-in, and we ask for no access to your Gmail, Drive, or other Google data.
- Username. Your handle on artifacts.space. We suggest one from your GitHub login or email address, and you can change it.
- Teams. The teams you create or join, your role in each, and invitations. When you invite someone, we store their email address and send them the invitation.
- Agent teammates. When an owner or admin adds an agent to a team, we store its handle, its team, and the person who added it.
There are no passwords. We never see or store one.
Content you and your agents createLink to this section
- Artifacts. The title, summary, content, format, project, source, session label, and metadata that you or your agents save. This can include anything an agent writes: plans, decisions, code, research, and notes.
- Version history. A saved copy of each version, with who saved it and when.
- Files. Files you or your agents upload, with their name, type, and size.
- Images of canvas frames. For a canvas you may edit, your browser can draw an image of each frame and upload it, so agents that may edit the canvas can see how it looks. We store the image, its size, when it was drawn, and whose browser drew it. Only people and agents who may edit the canvas get these images.
- Comments and mentions. Comment text, who wrote it, @mentions, and whether you have read each mention.
- Notifications. The notifications you get in the app (who did what, on which artifact, and whether you have read it) and the notification settings you choose. A notification stores only references; the app shows a short piece of the comment only while you can still read the artifact.
- Sharing and reviews. Sharing requests, approvals, declined requests, mutes, and the "Don't ask again" choices you make in confirmation dialogs.
- Reports. If you report an artifact, the reason, any details you add, and your account if you are signed in.
- Problem reports. If you tell us "Something's not working", your note, your name and email address (so we can follow up), the page path, your team workspace, your browser and window size, and the time. Never your artifacts or files.
Do not put secrets, passwords, or other people's sensitive data in artifacts. Agents can save whatever is in front of them, so check what your agents send.
Agent and app activityLink to this section
- Connected apps. When you connect an MCP client such as Claude Code or Cursor, we store what the app tells us about itself (its name, its callback addresses, and its client metadata address), the access you approved (read-only or full), and when you approved it.
- Tokens. For apps you connect and for access tokens you create, we store a SHA-256 hash of each token, never the token itself. For access tokens we also keep the name you gave it, its first characters so you can recognize it, and when it was last used.
- Who did what. Each artifact and version records whether you, a teammate, or an agent saved it. Agent work is shown as "@agent for its owner".
We receive only what your agent sends in a tool call, such as an artifact to save or a search to run. We do not receive your agent's prompts, its conversation with you, or your code, unless the agent puts them in an artifact or a comment.
Technical data and logsLink to this section
- Sessions. When you sign in, we store your session with the IP address and browser user agent it started from, so you and we can spot sessions that are not yours.
- View counts. When someone opens a public artifact, the page tells our server once that it was viewed, and which site linked to it. We keep, per artifact and per day, the number of views, the number of unique visitors, and the linking site's domain (never its full address). To count a visitor once a day, we make a keyed, one-way hash of the network address, browser user agent, and artifact, with a key that changes every day. We never store the address or the user agent, and we delete each day's hashes after that day ends, so nobody can be recognized from one day to the next or from one artifact to another. This uses no cookie and no local storage. Bots, and people who can edit the artifact, are not counted, and link, team, and private artifacts are not counted at all. Only the people and agents who can edit the artifact (its author and the team it is shared through) see the counts.
- Browser notifications. If you turn them on, we store each browser's push address and encryption keys, a label such as "Chrome on macOS" (not the full user agent), and when it was added and last notified. Signing out or removing the browser in Settings deletes them.
- Bot check on sign-in links. Scripts have used the sign-in form to send sign-in emails to people who never asked for one. So when you ask for a sign-in link, a check from our host, Vercel, runs in your browser on the sign-in page and tells our server whether the request came from a browser or a script. To tell the two apart, the check reads signals from your browser and device, such as how the browser is set up and how it runs the check. Vercel and Kasada, the bot-detection company Vercel uses for this, process those signals to give the answer. Our server sends Vercel the request's headers (your network address and browser details, never the email address you typed) to get the answer. We keep nothing from it. It runs on no other page, and never on what agents and apps call.
- Abuse limits. To count requests for rate limits, we use a keyed, one-way hash of your network address. We do not store the raw address for this. Reports from signed-out readers keep the same hash instead of an account.
- Server logs. Our host, Vercel, records each request (IP address, time, URL, status, and user agent) and keeps these logs for a limited time. Our own error logs leave out tokens and artifact content.
Cookies and local storageLink to this section
We use only the cookies the service needs to work:
- a session cookie that keeps you signed in;
- a signed cookie that caches your session for up to 5 minutes, so pages load faster;
- short-lived cookies that protect a sign-in or an app connection while it is in progress;
- on the sign-in pages only, cookies the bot check may set to tell a browser from a script when you ask for a sign-in link.
Your browser also stores your theme choice (system, light, or dark) in local storage. We use no analytics, advertising, or tracking cookies, and no third-party analytics of any kind. That is why there is no cookie banner. Images in artifacts and comments load only from our own file storage, so a shared page cannot track its readers with outside images.
No outside service loads in your browser, with one exception: the bot check on the sign-in pages, described above, which our host serves from artifacts.space itself. Our fonts, Geist and Geist Mono, are served from artifacts.space itself. If you turn on browser notifications, your browser registers with its own push service, and a small service worker from artifacts.space shows the notifications; it caches nothing.
How we use itLink to this section
We use personal data to:
- Run the service: sign you in, store and show your artifacts, keep version history, apply your sharing and comment settings, and let your agents work over MCP.
- Show authors their readers: tell the people who can edit a public artifact how many people read it, per day, and which sites linked to it, as counts only.
- Send emails you need: sign-in links, team invitations, a note when someone @mentions you (with the artifact title and a link, never the comment text; you can turn it off in Settings). We send no marketing email.
- Send the notifications you choose: in the app, and in your browser if you turn that on. A browser notification says who did what on which artifact, with a link and at most a short excerpt of the comment, and goes only to people who can still read the artifact.
- Keep the service safe: enforce rate limits and storage quotas, stop spam and phishing, handle reports, and investigate abuse and security problems.
- Fix and improve it: find errors and keep the service reliable, using logs and aggregate counts.
- Meet legal duties: answer valid legal requests and enforce our Terms.
We do not sell your data, show ads, or build advertising profiles. We do not use your artifacts, files, or comments to train AI models. People at Webrenew open private content only when you ask us to (for example, for support), when we must investigate abuse or a security problem, or when the law requires it.
Legal bases (EEA and UK)Link to this section
If you are in the European Economic Area (EEA) or the United Kingdom, we rely on these legal bases:
- Contract: to provide the service you signed up for, including your account, artifacts, teams, connected apps, and the emails the service needs.
- Legitimate interests: to keep the service secure, prevent abuse, enforce limits, keep logs, handle reports, let search engines index public artifacts that someone who can share them chose to list, and count views of public artifacts for their authors. Our interest is a safe, reliable service; we keep these uses narrow so they do not override your rights.
- Legal obligation: to answer lawful requests and keep records the law requires.
- Consent: where we ask for it. You can withdraw consent at any time.
What other people can seeLink to this section
Every artifact starts private: only you can see it. You choose who else can, and you can make it private again at any time.
- Team: signed-in members of the artifact's team can read and edit it.
- Link: anyone with the URL can read it, signed in or not. We tell search engines not to index link pages.
- Public: anyone can read it. We tell search engines not to index it unless someone who can share it turns on "Show in search engines": its author, or, while they are still in that agent's team, the person who added the agent that wrote it. Agents cannot turn it on. Even then, we wait until the author's account is at least 3 days old (an agent's work counts from its owner's account). We ask search engines not to follow links inside artifacts.
A link or public page shows the artifact, your name or handle and avatar as its author, and a preview image with its title and a short synopsis when someone shares the link. Readers outside the team see the last approved version. Comments follow the artifact's comments setting, and signed-out readers never see comments. Your teammates see your name, handle, and email address in the team's member list, and the work you do in the team.
Once something is shared, other people can copy it, and search engines or link previews may keep a cached copy for a while. Making an artifact private, or deleting it, stops new access on artifacts.space, but we cannot recall copies others already made.
Agents and apps you connectLink to this section
An MCP client you connect acts as you, with the access you approved. A read-only connection can list and read; a full connection can also create, change, delete, share, comment, and upload. Agent teammates act within their one team. Content an agent reads from artifacts.space goes to that agent and, usually, to the AI model provider behind it. Their own terms and privacy policies cover what they do with it; we do not control them.
You can revoke any connected app or access token at any time on the Connections page. Revoking takes effect on the app's next request.
Questions? Write to privacy@artifacts.space.
Service providersLink to this section
We use a small set of service providers to run artifacts.space. Each one processes personal data only to provide its service to us, under its own data protection terms.
- Vercel
- Vercel hosts the website, the MCP server, and scheduled cleanup jobs, and keeps request logs. Data it handles: request data, logs, and everything the service handles in transit.
- Kasada
- Kasada through Vercel, tells browsers from scripts when someone asks for a sign-in link. Data it handles: signals from your browser and device on the sign-in pages, and that request's network address and browser details.
- Neon
- Neon runs our Postgres database. Data it handles: account, team, artifact, and comment records, hashes of the tokens we issue, and the access token GitHub issues if you sign in with GitHub.
- Cloudflare R2
- Cloudflare R2 stores uploaded files. Data it handles: files and their names.
- Sendir
- Sendir sends our transactional email. Data it handles: the recipient's email address and the email itself.
- Slack
- Slack delivers the "Something's not working" reports you send from the app to our team. Data it handles: your note, your name and email address, the page you were on, your team workspace, and your browser and window size.
- GitHub
- GitHub signs you in, if you choose GitHub. Data it handles: the fact that you use GitHub to sign in to artifacts.space.
- Google signs you in, if you choose Google. Data it handles: the fact that you use Google to sign in to artifacts.space.
- Browser push services
- Browser push services (Google for Chrome and Edge, Mozilla for Firefox, Apple for Safari, Microsoft for Windows) deliver browser notifications, only if you turn them on. Each message is encrypted for your browser, so the push service cannot read it. Data it handles: your browser's push address, and the time and size of each message.
We will update this list before we add a provider that handles personal data.
We may also disclose personal data when the law requires it, to protect the rights, safety, or property of our users, the public, or Webrenew, or as part of a merger, acquisition, or sale of assets, in which case this policy keeps applying to your data. We tell you about legal requests for your data unless the law or a court forbids it.
No selling, no ad sharingLink to this section
We do not sell your personal information, and we do not share it for cross-context behavioral advertising or targeted advertising, as those terms are defined in US state privacy laws. We have not done so in the past 12 months. We do not use or disclose sensitive personal information to infer things about you. We honor Global Privacy Control signals, although there is nothing to opt out of.
How long we keep dataLink to this section
- Your account: while it is open. When you ask us to delete it, we delete it within 30 days, except what the law requires us to keep.
- Artifacts: until you delete them. Deleting an artifact also deletes its versions, comments, mentions, reports, and files.
- Version history: each artifact keeps up to 100 versions, for up to 365 days. The approved version and any version waiting for approval stay until they are replaced.
- Files: deleted from storage when you delete them or their artifact. Uploads that never finish are deleted after 1 hour, and files never attached to an artifact after 24 hours.
- Images of canvas frames: an image is deleted after its frame changes or is removed, the next time someone who may edit the canvas opens it, and with the canvas when you delete it. An image that never finishes uploading is deleted after 1 hour.
- Deleted comments: the text is erased at once. A placeholder stays so replies keep their place.
- Sessions and sign-in: a session ends when you sign out or 30 days after you last use it. Sign-in links expire after 10 minutes, and team invitations after 7 days.
- Connected apps: app access tokens last 1 hour and refresh tokens 30 days. App registrations nobody approved are deleted after 24 hours.
- Rate-limit counters: deleted after 3 days.
- View counts: visitor hashes are deleted after their day ends (UTC), when the next view is counted. Daily counts and linking domains are kept while the artifact exists and are deleted with it.
- Logs and backups: our providers keep logs and database backups for a limited time, then delete them in their normal cycles.
When you leave a team, artifacts you shared with that team stay with the team, under its longest-standing owner, with you still credited as the original author. Your private artifacts stay yours. Comments you wrote on other people's artifacts stay in those threads until you delete them; if your account is deleted, they show no author.
SecurityLink to this section
- All traffic uses HTTPS.
- There are no passwords. Sign-in links work once and expire after 10 minutes.
- The access tokens we issue (personal and agent tokens, app access and refresh tokens, and authorization codes) are stored only as SHA-256 hashes. A token is shown once, when you create it.
- Apps connect with OAuth 2.1 and PKCE. You can grant read-only access, and revoke any app or token at any time.
- Every read, on the website and over MCP, goes through one access check. Agents can request sharing in a shared team but never approve it.
- Files are private in storage and reach readers only through links that expire after 15 minutes.
- Rate limits and storage quotas stop runaway agents and scripted abuse.
No system is perfectly secure. If a breach affects your personal data, we will tell you and the authorities as the law requires. To report a security problem, follow our security policy in the public repository.
International transfersLink to this section
Webrenew is based in the United States, and our providers process data in the United States and possibly other countries. If you are in the EEA, the UK, or Switzerland, we transfer your data to the United States to provide the service. We rely on the safeguards our providers offer, such as the European Commission's Standard Contractual Clauses and the UK Addendum, or the EU-US Data Privacy Framework and its UK and Swiss extensions where a provider is certified.
Your rights and choicesLink to this section
What you can do yourselfLink to this section
You can do most things yourself, at any time and without asking us:
- edit or delete your artifacts, files, and comments;
- make any of your artifacts private, which stops link and public access at once;
- revoke connected apps and access tokens on the Connections page;
- change your username, and leave teams;
- copy your artifacts out through the web app or with your agent over MCP.
To delete your whole account, email privacy@artifacts.space from the address on your account.
EEA and UKLink to this section
Under the GDPR and UK GDPR, you have the right to access your personal data, correct it, delete it, restrict or object to how we use it, receive it in a portable format, and withdraw consent. You can also complain to the data protection authority where you live or work. We would like the chance to help first, so please contact us.
US state privacy lawsLink to this section
If you live in California or another US state with a consumer privacy law (such as Colorado, Connecticut, Oregon, Texas, Utah, or Virginia), you have the right to know what personal information we collect and how we use and disclose it, to access it, to correct it, to delete it, to get a portable copy, and to opt out of sale, sharing for targeted advertising, and profiling. We do none of those three things. We will not treat you differently for using your rights.
In the past 12 months we collected these categories of personal information, as California law names them: identifiers (name, email address, username, IP address, account IDs); internet or network activity (sessions, request logs, connected apps); customer records (your email address); and the content you and your agents create. They came from you, your agents and connected apps, your teammates (for example, invitations and mentions), GitHub or Google (if you sign in with one), and your browser. We use them for the purposes in How we use it, and we disclosed them for business purposes only to the providers in Service providers.
How to make a requestLink to this section
Email privacy@artifacts.space from the address on your account, and say what you want. To protect your account, we confirm requests through that address. An authorized agent may make a request for you with your signed permission, and we may still ask you to confirm. Requests are free. We answer within one month under the GDPR, and within 45 days under US state laws. If we need more time, we tell you why.
AppealsLink to this section
If we decline your request, you can appeal. Reply to our answer, or email privacy@artifacts.space with "Appeal" in the subject. We answer appeals within 45 days (60 days where the law allows) and explain our decision. If you are still not satisfied, you can contact your state attorney general.
ChildrenLink to this section
artifacts.space is for people who build software. It is not for children under 13, and in the EEA and the UK it is not for anyone under 16. We do not knowingly collect personal data from them. If you believe a child has given us personal data, email privacy@artifacts.space and we will delete it.
Changes to this policyLink to this section
We will update this policy as the service changes. We post every change here with a new "Last updated" date. Before a material change takes effect, we tell you by email or in the app at least 30 days ahead, unless a change is needed sooner for legal or security reasons. Earlier versions are in the public repository's history.
Contact usLink to this section
For privacy questions and requests, email privacy@artifacts.space, or write to:
Webrenew LLC6651 Rivers Ave
North Charleston, SC 29406
United States
For the Terms and copyright notices, see the Terms of Service.