Privacy
What WriteCode keeps, for how long, and who else sees it.
Last updated 30 October 2026
No account to write code
Writing, running and sharing code needs no sign-up and no account: there is no profile, password or email address to keep. Only companies that run online assessments sign in (see below).
Your projects stay in your browser
Projects, files, settings, run history and interviews you set up are saved in this browser (its local storage), not on our servers. Clearing the site's data in your browser deletes them. “Move to another device” sends a copy only when you ask it to.
The browser also keeps a random id that is sent with your runs, so that run limits apply to each person even when many share one network. It is not linked to anything about you.
When you run, debug or visualize a program
Your code and its input are sent to our server, run in an isolated sandbox and then thrown away with the sandbox. A record of the run (the language, timings, exit code and the program's output) is kept for 30 days to run the service and find faults, together with a one-way hash of your network address used for rate limits. Your network address itself is not stored with it.
Share links and moving projects
A share link stores a copy of the code you chose to share, for 90 days after it was last opened. Anyone with the link can read that copy. A code to move projects to another device holds a copy of those projects for 12 hours, then it is deleted.
Files sent with Send files are kept until the time you chose (at most 7 days), or until you delete them, and then removed from the server. Anyone with the name you sent them under (writecode.in/drop/<name>) can download them, and needs the password too if you kept them private. Files sent earlier with a code open by their link until they expire. Your password never leaves your browser: the server keeps only a key derived from it.
A Codepad text is kept under the name you chose (writecode.in/pad/<name>) until it is deleted, or until nobody has opened it for 60 days, and then removed from the server. Anyone who knows the name can read and change a pad that is not private; a private pad needs its password, and is encrypted in your browser, so the server cannot read it. Its password never leaves your browser: the server keeps only a key derived from it, which is why a forgotten password cannot be reset. Texts sent earlier with a 6-character code are kept until the time chosen then (at most 7 days).
Live sessions and interviews
In a live session, the code, cursors, runs and names of the people in it are passed between them through our server and kept while the session is active, then removed within a day.
In an interview with the camera on, the video goes directly between the two browsers, or through our relay server when a network blocks direct connections. It is not recorded. Invitations you choose to email are sent through our email provider (Resend).
The assistant
When you ask the assistant, the files of the open project, its last output and your question are sent to Google's Gemini service to write the answer. We do not store what you send. You can turn the assistant off in Settings → Coding help; nothing is sent to it then.
Companies running online assessments
A recruiter signs in with a link sent to their email address. We keep that address, their name if they give one, the organization they belong to and its team, and the assessments they write. Normal recruiter sign-in has no password; the sign-in link works once, and the session is kept in a cookie that only our server can read. A separately provisioned app-review account uses a reusable password to access an isolated demo organization. For that account we store only a salted password hash, never the password itself.
Students taking an online assessment
The company that invites you gives us your name and email address, and we email you your link (through Resend). When you take the assessment we keep, for that company: the code you write and submit, your test results and score, when you started and finished, and what your browser reports during the test (leaving the window or full screen, the first 300 characters of anything you try to paste, the camera turning off).
If the company requires the camera, a still photo is taken every 30 seconds and whenever you leave the test window, and kept with your report. Photos are not used for anything else: no face recognition, and they are never shared outside that company's team. Nothing is recorded as video or sound.
Only the people in the company's team can see your results. Everything about an assessment (results, code and photos) is deleted 180 days after it closes, or earlier when the company deletes it. To ask about your data, write to the company that invited you, or to us.
No advertising, no tracking
WriteCode shows no adverts, uses no tracking cookies and no third-party analytics, and does not sell or share data.
Deletion requests and content reports
Use Request account deletion in Settings or visit writecode.in/account-deletion to request removal of your account and associated personal data. We verify ownership before acting. For a shared organization, we arrange ownership transfer where needed and preserve other members’ work while removing or anonymizing your personal account references. Candidate data requests are reviewed with the organization responsible for the assessment.
Use Report below an assistant response to flag it without leaving the app, or visit writecode.in/report for shared content. We keep the form details, an optional contact email, the response excerpt you choose to include, and a one-way network hash for abuse prevention in a private support queue. Your project and the rest of your chat are not attached. Open requests remain until handled; resolved reports are removed within 90 days. Account-deletion request details are cleared when deletion is fulfilled. Restricted recovery backups normally expire within 30 days.
Contact
Questions, requests or a problem to report: write to [email protected].