TryCode
HomePublic postsAPI
HomePublic postsAPI
Sign in with GitHub
Back to home
TRYCODE DOCUMENTS

Privacy policy

Updated November 19, 2026

About the service

TryCode lets you create, edit, and publish code posts, collaborate on them, and use an API. This policy describes how the application processes data. The operator of each deployment must identify themselves and provide a contact for data requests before public launch.

Data we process

  • Post contents, titles, selected language, access settings, creation and modification dates, and view counts.
  • When signing in with GitHub: your ID, username, name, email address, profile photo, profile link, and some public profile details, if GitHub provides them.
  • Technical identifiers for guests, sessions, protected-post access, and API keys. Post passwords and access tokens are stored as hashes.
  • Data you put in public posts or share with others through collaborative editing.

Why we use data

We process this data to create and save posts, enable collaboration, manage access, sign users in, operate the API, and protect the service. GitHub sign-in is optional: you can use the editor as a guest. The application does not use data for advertising profiles.

Who can see posts

Public posts appear in the catalog and are available to other users. A post shared by link is available to people with the link and required access; the author sets its password, view limit, and expiration. When collaborative editing is enabled, people with access can change its contents. Do not include secrets or personal data you do not want to disclose.

Third parties

GitHub handles sign-in: your browser goes to GitHub for authorization, and the app receives the profile data you approve. Hosting providers and network intermediaries chosen by the deployment operator may process technical request data to provide infrastructure. The app has no built-in advertising or analytics integration.

Storage and deletion

Posts remain until the owner deletes them or their expiration or view limit is reached. Your GitHub account data stays in the service database until the deployment operator deletes it on request; there is currently no account deletion button. A sign-in session lasts up to 30 days unless you sign out sooner. The deployment operator determines retention for backups and hosting logs.

Your choices

You can edit or delete your posts, turn off public access, sign out, and clear site data in your browser. Contact the deployment operator to request access to, correction of, or deletion of your account data. Deleting the guest cookie may break the link between your browser and your guest posts.

Cookies and policy changes

The purpose and lifetime of technical cookies are described in the cookie policy. We will update this page when service features change; the update date is shown above.

Cookie policyHome