Privacy Policy

Effective 8 November 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.

When you sign in with X, Phext Edit asks for the tweet.read and users.read scopes. X sends your account ID and your username. Phext Edit never posts for you, and it does not read your timeline.

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:

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

Phext Edit uses no third-party analytics, advertising or tracking scripts. There are no ads, ever. An optional donation opens a Stripe Payment Link in a new tab. Phext Edit does not embed a payment form, and it does not add a tracking pixel for an ad campaign.

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

Changes

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