Google login and profiles
When you choose Google login, Codepad receives your Google account identifier, email address, name, and profile picture, when available. Supabase processes sign-in and stores your account and profile. Codepad uses this information to recognize your account, suggest a display name, and make your pads, private notes, and pins available across devices.
Codepad requests basic identity, email, and profile permissions. It does not request access to your Gmail messages, Google Drive files, or contacts. Your chosen display name and cursor color are visible to collaborators. Your account email is not included in collaboration presence or public pad views.
Signing in imports the current browser identity’s owned pads, notes, and pins. Conflicting private notes are kept as separate imported copies. Google account information is not included in Codepad’s product activity counts.
Code, notes, and service providers
Supabase stores shared pad snapshots, pad metadata, private notes, and account information. PartyKit processes shared code and live presence to synchronize editing. Vercel hosts the website and API and provides usage and performance measurement. These services process information needed to deliver their part of Codepad.
Anyone with an edit link can read and change its shared code. Read-only links and embeds expose the saved code they display. Private notes, including imported copies, are associated with their owner and are not included in shared views. See About and data access for more detail.
Cookies and browser storage
Codepad uses cookies for guest identity, account sessions, and completing login and pad imports. Browser storage holds editor preferences, guest pins, and recoverable unsent note drafts. Clearing browser storage can remove guest access and local drafts. Logging out ends the current account session; it does not delete saved account data.
Usage, performance, and support
Vercel Web Analytics measures visits to public information pages, and Speed Insights measures performance. Codepad also counts events such as successful pad creation, copied links, collaboration, and failures. These product counts exclude code, private notes, names, email addresses, and share links. Hosting services may process request information, including IP addresses, for operation and security.
If you contact support or send feedback, Codepad stores the details you submit, including any reply email. The maintainer uses these messages to respond and investigate the issue.
Access, retention, and deletion
Saved account data remains available until it is deleted or otherwise removed through operation of the service. Codepad does not promise permanent storage. You can change your display name in settings and delete pads you own from the dashboard. Deleting a pad also removes its saved snapshot and associated notes.
To request access to, correction of, or deletion of account information, contact the maintainer using the form below. Account deletion requests are handled by the maintainer. Codepad retains a record that a guest identity was claimed so an old guest cookie cannot be reused; that record no longer links to the deleted account.
You can also remove Codepad’s access from your Google account’s connected apps settings. This does not itself delete data already saved in Codepad.
Changes to this policy
Codepad will update this page when its data practices change. If a change introduces a new use of Google account information, Codepad will disclose it and seek consent before that new use.