Privacy
This page covers the Aphelion website, workspace accounts, license purchases and the Aphelion Editor desktop application. The website now uses accounts, payment processing and limited analytics; the desktop editor remains local and does not send telemetry.
Summary
- Accounts use Firebase Authentication for email/password and Google sign-in.
- PayPal processes payment details; Aphelion does not receive or store card numbers.
- License records contain account, purchase and product-redemption information.
- Firebase Analytics may collect website usage and device information for measurement.
- The website reads public GitHub data on the server, not from your browser.
- The editor runs locally, ships no telemetry and keeps your files on your machine.
Accounts and authentication
- When you create an account or sign in, Firebase Authentication processes your email address and authentication credentials. Google sign-in is handled by Google according to Google's own privacy terms.
- The site uses your Firebase account identifier to associate purchases and license records with your workspace. You can sign out from Account settings.
- Authentication session data is stored by Firebase in your browser so the site can keep you signed in. You can clear it by signing out or clearing site data.
Payments and licenses
- Checkout takes place through PayPal. PayPal handles payment credentials and returns payment status to the site; Aphelion does not store your full payment details.
- To fulfill a purchase, the site stores a PayPal order or capture reference, your Firebase account identifier, the purchase amount and currency, and the date of fulfillment.
- License keys are generated by the server. The raw key is shown once after a verified payment; the licensing service stores a protected representation and safe metadata rather than displaying the full key in Account settings.
- When a product redeems a key, the service records the product identifier, account binding, product version when supplied, and redemption time. Each license can be redeemed once per product.
Analytics and hosting
- Firebase Analytics is loaded in the browser when supported. It may process page views, browser or device information and approximate usage events. Analytics is not used by the desktop editor.
- The site is hosted on Vercel. Vercel keeps standard request logs for every deployment, which can include an IP address, a user agent and the requested path. Those logs are used for operations, capacity and abuse prevention. Vercel's handling of them is described in the Vercel privacy policy.
This website
- The site does not use advertising or session-recording code. Firebase Authentication may store session state in browser storage, and Firebase Analytics may use its own measurement storage where supported.
- Release lists and documentation are read from the public GitHub API when a page is rendered. Those requests are made by the server, so your IP address and browser are not sent to GitHub by visiting a page.
- Builds and documentation links point at github.com. Once you follow one of those links, GitHub's own practices apply. See the GitHub privacy statement.
The desktop application
- The editor runs entirely on your computer. Projects, media references, preferences, logs and plugins are written to the locations you choose and are never uploaded.
- There is no telemetry, crash reporting, usage counting or update check. The editor does not contact a server on its own.
- Media decoding, the video encoder and the plugin runtime are bundled with the application. Nothing needs to be downloaded at run time.
- If you install a plugin written by someone else, that plugin runs in the same process and can do whatever its author wrote. Install plugins from sources you trust.
Changes and contact
If any of the above changes, this page will be updated before the change ships. Questions about this policy can go in the issue tracker for aphelion-engine/aphelion-editor.
Last updated 21 September 2026.