A shared place to work through code.

Contact and maintenance

The Codepad maintainer handles support and feedback through the site’s contact form. Report a problem, ask about a workflow, or suggest an improvement. The form asks for an email address so a reply is possible.

Codepad provides editing and sharing, including syntax highlighting, multiple files, live cursors, and private notes. It does not execute code or provide a full development environment.

Guest access and accounts

A cookie identifies your browser without an account. Your dashboard lists pads created with that identity, and private notes are associated with it. The cookie is configured to last up to one year, but your browser can remove it earlier.

Clearing cookies, using private browsing, switching devices, or moving between browser profiles can make your owned pads and notes unavailable under that identity. A saved edit link still opens the shared code, but it does not restore ownership or private notes. Keep a separate copy of work you need to retain.

When Google login is available, signing in brings this browser’s pads, private notes, and pins into your account. Sign in with the same Google account to access them on another device. If the account already has notes on a pad, the incoming guest notes are kept as imported copies.

If you choose Google login, Supabase stores your account identity and profile information, including your email, display name, and optional profile picture. Your email is not shared with collaborators.

Read the privacy policy for details about account information, service providers, and deletion requests.

If you previously used www.codepad.pro as a guest, use that host to reach or import its existing pads and notes. Its guest identity is separate from codepad.pro.

What is saved

The homepage editor stays in the current tab until you create or share a pad. Shared pad contents are synchronized through PartyKit and periodically saved as snapshots in Supabase. Private notes are stored separately from the shared document.

Keep the editor open and connected while changes save. A lost connection, an interrupted save, or a cleared browser session can affect what is available later. Codepad does not promise permanent retention or provide a version-history interface.

Use your own files or version control for durable storage. The collaboration guide explains how to handle an interrupted connection.

Who can see and change a pad?

• Edit link: people who have the link can read and edit the shared files.
• Read-only link: people who have it can view and copy the saved code. The edit link remains active.
• Private notes: notes belong to your guest identity or signed-in account and are not included in shared views.

Share links only with the intended people. Codepad keeps pad and dashboard pages out of search indexing, but a search exclusion is not an access restriction. Read the link-sharing guide for concrete examples.

Usage measurement

Codepad uses Vercel Web Analytics on public information pages and Vercel Speed Insights for performance. It also counts successful pad creations, copied links, observed collaboration, and action failures to understand whether the product works for visitors.

These product counts group activity by day, public landing page, and broad referral category. They do not include code, notes, names, email addresses, or share links. The service uses hashed receipts to avoid counting the same pad twice; browser-reported activity can be incomplete.

Support messages contain the details you choose to send, including the reply email. Avoid including credentials or sensitive code in a support request.