Privacy

What EditAtlas keeps, what it never sees, and what happens when you sign in to the studio with Google.

Last updated 19 November 2026. EditAtlas is run by the EditAtlas team at edit.trysometh.ing.

In short

  • EditAtlas has no ads and no tracking cookies. An account is optional: it is made when you sign in with Google, in the studio or on the Animation styles page.
  • Your footage, sound and pictures are never uploaded to EditAtlas. Your agent edits on your computer, and the studio edits in your browser.
  • If you keep a project in Google Drive, its files go from your browser straight to your own Drive. EditAtlas's servers never receive your files. Signed in, they keep Google's lasting permission for the studio only locked with your key, so it cannot be used without your browser.
  • With an account, EditAtlas keeps your Google account's ID and email address, and your list of projects encrypted with a key that only your Drive and your browser hold.

The library, the MCP server and the API

EditAtlas answers lookups. Technique, template, style and sound lookups come from its own library. Music, photo and video searches go to a search service run by the EditAtlas team, which asks Pixabay or Pexels; only the search words and filters are sent, and results link straight to their files.

The home page shows how many tool calls and agent sessions EditAtlas has served. A session is counted at its first tool call, with a random ID made by the server and the name of the agent app. Calls and sound downloads are also counted per day.

To find searches that fail, EditAtlas keeps what agents type into its search tools for 60 days: the search words, the filters, the ids of the results and which result was opened next, under a hashed session ID and the agent app's name. Write search words about the effect, not about people.

When you tell your agent whether something from EditAtlas worked, it can send that answer with send_feedback: the verdict, the item's id and short notes. EditAtlas keeps these to improve the library and, for answers sent from 18 November 2026 on, may use them to train or test AI models, as the terms say.

Links to EditAtlas that we post elsewhere can end in ?ref= and the name of the place, such as ?ref=threads. A page opened from such a link adds one to that place's count for the day. EditAtlas keeps only those daily totals per place, not your address, your browser or the page you opened, counts each network once a day, and deletes the totals after 180 days. The EditAtlas address we give in MCP directories, for connecting an agent app, can end in ?ref= in the same way. When a session from it is counted, at its first tool call, EditAtlas notes the place's name with that session, and nothing else; a later request cannot change it.

The install commands on the home page end in a random code made in your browser when the page loads, such as ?i=k3f9x2m7qa. If you install from there, your agent sends that code with its requests, and EditAtlas reads it when a new session starts, to count how many installs are used again on later days. The code is not tied to you, an account or a browser. EditAtlas keeps only a salted hash of it, the days a session started with it and from how many networks, and deletes these after 120 days. To leave it out, remove ?i= and the code from the address.

IP addresses are not stored. To limit abuse, each network's requests are counted under a salted hash that changes every day, and those counts are deleted after two days.

Skills

When an EditAtlas skill's main script finishes on your computer, it sends EditAtlas four things: the skill's name, its version, whether it finished or failed, and how many seconds it took. Nothing else: no ID, no file names or paths, no text and no media. EditAtlas keeps only daily totals per skill, version and result, and deletes them after 180 days. To turn it off, set EDITATLAS_TELEMETRY=0; it is also off when CI is set.

The studio

The studio runs in your browser. It opens the project folder you choose and saves back into it. These stay in your browser and are never sent: the folders you opened on this computer, changes not saved yet, and the copies of projects you keep in Google Drive (in this site's own storage in your browser). The × next to a project and Forget all on the first screen clear that list; clearing this site's data in your browser clears everything.

To show how many people are editing and count Useful, your browser keeps a random ID; the server keeps only a salted hash of it. Records of who is editing are deleted after 35 days.

The Feedback form sends your message, an email address if you give one for a reply, your browser's name, language and screen size, and recent errors on the page. If you tick the box to attach the project, it also sends the project's text, timings, styles and file names, never the files themselves. The EditAtlas team reads these reports. An attached project is deleted after 90 days. Your message may also be used to train or test AI models if you send it from 18 November 2026 on, as the terms say; your email address and an attached project are not.

A studio link is made only when you keep a project in your Google Drive from the studio. It holds your project's versions (text, timings and styles, never media), encrypted in your browser or by your agent before they leave. The key is the part of the link after the #, which browsers never send, so EditAtlas stores data it cannot read. Anyone who has the whole link can open the project and add versions, so share it as you would a password. Links have no end date for now. To have one deleted, send us the part between the # and the first dot, never the whole link.

Your account

Signing in is optional; the studio works without it. When you press Sign in with Google, Google tells EditAtlas who signed in, with a signed token that EditAtlas checks with Google. EditAtlas then keeps:

  • your Google account's ID and its email address, and when the account was made and last used;
  • your list of projects: the projects you kept in Google Drive, with their title, studio link and Drive folder. Your browser encrypts the list before it is sent, with a key kept only in your Drive's hidden app folder and in your browser, so EditAtlas stores data it cannot read. The list holds your studio links, and their keys stay unreadable to EditAtlas too;
  • a session for each browser you sign in on: a cookie with a random value, of which the server keeps only a hash. It is used only to keep you signed in, for 30 days at most.

On the Animation styles page, Sign in with Google asks Google only for your account and email address (openid, email), not for your Drive. EditAtlas keeps the same account as above, without a list of projects until you keep a project in Google Drive from the studio, which then asks Google for Drive access. An account without a list of projects is deleted, with its sessions, after 24 months in which it was not used: no sign-in and no pack download.

Sign out on the first screen ends the session in that browser. Delete account deletes your account, your list and every session on EditAtlas at once, and the key in your Drive when the studio can reach it; your project folders, links and files in Drive stay. To have an account deleted without signing in, use Feedback with the email address of the account.

Animation styles packs

A pack is free and needs an account. When you get one, EditAtlas makes a download link that works for 15 minutes and at most three times, and keeps it only until the next daily clean-up. EditAtlas counts downloads per pack and per day, and the place you came from when the address you opened ended in ?ref=, as totals that name no account. A skill from a pack sends the same run signal as the other EditAtlas skills (its name, version, whether it worked, and how long it took), which you can turn off with EDITATLAS_TELEMETRY=0.

EditAtlas does not send you marketing email. If it ever offers news by email, it will ask with its own box, off until you tick it.

Google sign-in and Google Drive

The studio asks Google only when you press Sign in with Google or Google Drive, and the Animation styles page only when you press Sign in with Google, for the first item below alone. Google shows you what it asks for:

  • Your Google account and email address (openid, email), to make your EditAtlas account and show which account you are signed in with, as described above.
  • Files the studio makes in your Drive (drive.file), to create the folder EditAtlas in your Drive, copy into it the project folders you choose, and update them when you save. The studio cannot see or change any other file in your Drive.
  • Its own hidden app data (drive.appdata), for two small files in your Drive's hidden app folder: the list of projects you kept there (their folder, name, title and studio link if they have one), and the key that opens your list of projects on EditAtlas.

The studio uses this access only to sign you in, keep the projects you choose in your Drive, copy your later saves there, list them, and copy one back into your browser when you open it. Your browser talks to Drive directly: no file or list from your Drive is ever sent to EditAtlas. Google's access token for Drive lasts one hour and is kept in that browser tab. Signed out, it is never sent to EditAtlas. Signed in, the studio keeps Drive connected so you do not have to sign in to Google again every hour: when you sign in, Google gives EditAtlas's server a lasting permission (a refresh token) for the access above, which the server hands to your browser without keeping it. Your browser locks it with the same key as your list of projects and EditAtlas keeps only the locked copy. When an hour runs out, your browser unlocks it and sends it to EditAtlas's server, which asks Google for the next hour's access token, passes it to your browser and forgets both. EditAtlas's servers never use your Drive themselves. Of Google user data, they keep only your Google account's ID and email address, and that locked permission, for your account. They are not sold, shared or transferred to anyone, not used for ads, not used to write to you except to answer you, and not used to train AI or machine learning models.

EditAtlas's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

To stop: press Delete account on the studio's first screen, which also takes the studio's permission back at Google, or Sign out on a computer you no longer use, or remove EditAtlas at myaccount.google.com/permissions, which takes back the studio's access to your Drive. The files in the EditAtlas folder of your Drive are yours: delete them in Drive when you like. To delete the hidden list, open Drive's Settings, then Manage apps, and choose Delete hidden app data next to EditAtlas. To delete the copies in your browser, clear this site's data.

Other services

  • Cloudflare hosts EditAtlas and carries every request under its own privacy policy.
  • The website's pages, but not the studio, use Cloudflare Web Analytics to count page views. It sets no cookies and does not store your IP address. Cloudflare receives the address of the page you view, which can include search words you typed into the site, and how long the page took to load. Visitors in the European Union are not counted.
  • The website's pages load the Inter font from Google Fonts, so your browser asks Google for it. The studio uses its own copy.
  • Sound downloads can come from the public GitHub repository EditAtlas/sfx, and music, photo and video links lead to Pixabay or Pexels.

Children

EditAtlas is not meant for children under 13 and does not knowingly collect anything from them.

Changes and contact

When this policy changes, the new version is posted here with a new date. For a question, or to have something deleted, use Feedback in the studio (with your email address for a reply) or open an issue at github.com/EditAtlas/skills.