Privacy Policy

Effective 30 October 2026

This policy covers Phext Edit, the web editor for phext files. It explains what Phext Edit learns when you sign in, how that information is used, and what happens to it.

What we receive

When you sign in with Google, Phext Edit asks for the openid, email and profile scopes. Google sends your account ID, your name, and your email address with whether Google has verified it.

When you sign in with GitHub, Phext Edit asks for the read:user scope. GitHub sends your account ID, username, display name, and your public email address if you have one.

Phext Edit asks for nothing else. It cannot see your Gmail, Drive, contacts, calendar or repositories.

How it is used

Your sign-in details are used only to:

• check whether your account may use the editor, by comparing your account ID or verified email with the server's list of editors
• show your name or username in the editor so you can see who is signed in

They are not used for advertising, profiling or analytics, and they are not sold or shared with anyone.

What is stored, and for how long

• Sign-in cookie. After you sign in, your account ID, username, name and verified email go into a signed, HttpOnly cookie in your own browser. It expires after 14 days, or when you sign out. The server keeps no account database.
• Provider tokens. The access token Google or GitHub returns is used once to read your profile, then thrown away. It is never saved, and Phext Edit never acts on your account.
• Your edits. Text you save is written into the phext files on the server. Those files belong to the server's owner and are not tied to your account.
• Server logs. The web server keeps standard access logs (IP address, time, page requested and browser) to keep the service running and secure. These logs do not include your account details.

Phext Edit uses no third-party analytics, advertising or tracking scripts.

Google user data

Phext Edit's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Your choices

• Sign out at any time from the status bar. This deletes the sign-in cookie.
• Remove Phext Edit's access from your Google account or your GitHub settings.
• Email questions or requests about your data to will+support@phext.io.

Changes

If this policy changes, the new version will be posted on this page with a new effective date.