Your information

Privacy policy

Encrydle Development Bootstrap

Last updated: September 13, 2026

This policy covers the Encrydle Development Bootstrap native Windows utility and its public information website. The utility is maintained by its developer for personal prototyping and initial Development Console setup. For support and privacy requests, contact teloverge@gmail.com.

Google data we access

The utility requests the OpenID identity scope. It processes a Google-issued identity token containing an account identifier (the subject), issuer, intended client, authentication time and other fields needed to verify that the response belongs to the current sign-in attempt. It does not request access to Gmail messages, Drive files or Contacts.

Authorization codes and tokens are processed temporarily to complete and verify sign-in. The utility does not receive your Google password, request offline access or retain Google refresh tokens.

Why we use it

Identity evidence is used to discover a candidate owner identity for private review, or to authenticate an already designated owner during initial bootstrap-key enrollment and permitted key replacement. Google sign-in alone does not approve an owner designation, enroll a Console origin, or grant ordinary Encrydle application access.

Local storage and retention

Account discovery can save the verified issuer, client identifier and account subject in an access-controlled local candidate file. An approved identity policy and its review records can retain those identifiers; a separately approved private bootstrap executable pins the policy. These records are not published on this website.

The enrollment utility also maintains local security-key public credential information, revocations and the recorded origin-enrollment outcome. Protected bootstrap history must survive restarts so a completed enrollment cannot silently become a fresh attempt.

Candidate files and review material are retained locally until the developer removes material no longer needed for review or operation. Approved policy and security-history records are retained while needed to establish prior authorization and prevent repeated bootstrap. There is no automatic deletion schedule. Requests to delete records are reviewed against these security requirements; deleting a record does not authorize another enrollment.

Sharing and use restrictions

Google identity data is not sold, used for advertising, used to train AI models, or published on this website. It is used only for the identity-verification and bootstrap purposes described here. The utility exchanges sign-in requests directly with Google. Private candidate and policy records are available to the developer and any reviewers the developer explicitly authorizes; they are not uploaded to the website host by the utility.

Visiting this website

The public pages contain no sign-in form, analytics script, advertising or application cookies. Cloudflare Pages hosts the website and processes network request information to deliver and protect it, which can include IP addresses and request metadata. Cloudflare describes its processing in its privacy policy. Google’s handling of Google sign-in is described in Google’s privacy policy.

Your choices and requests

You can decline or cancel Google sign-in, close the utility, or remove the app’s connection through your Google Account’s third-party connections settings. Removing the Google connection does not erase locally retained records or undo a completed origin enrollment.

To ask about access, correction or deletion of information, email teloverge@gmail.com. If you contact the developer, your email address and message are used to respond and handle the request. Do not send passwords, tokens, client secrets, security-key PINs or recovery material.

Changes to this policy

Changes will be published on this page with an updated date. The policy will be updated before introducing materially different uses of Google identity data.