Privacy Policy

1. Text the extension accesses

CkretGuard reads the current prompt in recognized text inputs when you try to send it on supported ChatGPT, Claude, Gemini, DeepSeek, Grok, Meta AI, Microsoft Copilot, Perplexity, and Mistral websites. It checks that text for credential patterns, labeled values, and configured custom field names. Prompts may contain authentication information, personal communications, or other information you type or paste.

Scanning happens on your device. CkretGuard does not send text to a remote scanner, an AI model, Orenthic, or an analytics service. The extension does not scan your files, images, voice input, other applications, or existing chat conversations.

2. What your choices do

• Send: activates the chat website’s send control for the original prompt. If detected secrets remain, CkretGuard records that unmasked send attempt in local History.
• Edit: returns to the draft without sending it or adding it to History.
• Mask: replaces detected values with xxxxxxxxxx, validates the masked draft, and activates the website’s send control. Masked prompts are not added to History.

These actions use the chat website you selected. The website’s handling of submitted text is governed by its own privacy policy. Detection may miss secrets. A website can also read text entered into its page before you press Send; CkretGuard does not prevent that access.

3. Information stored locally

• Settings: your protection mode, client-ID preference, and up to 50 custom field names. Custom fields store names, not a separate collection of secret values.
• Activity totals: numeric counts of detected occurrences, masked prompt sends, and unmasked prompt sends.
• Unmasked-send History: the complete original prompt, detected count, time, chat provider, and a supported conversation URL where available. URL query strings and fragments are removed.

History only records an attempted submission after you select Send in a secret warning and the website’s send control is activated. It does not confirm delivery. Ordinary messages, masked messages, edited drafts, cancellations, and failed send activation are not saved in History.

Settings and totals use Chrome local storage. History uses an extension-local IndexedDB database. CkretGuard does not sync this information to other devices or upload it. Production builds do not include diagnostic prompt logging, advertising, tracking cookies, or remote analytics.

4. Retention, access, and deletion

You can view and delete individual History entries, or clear all History, in the extension’s full mode. Entries older than 90 days are deleted during History operations, when the extension worker starts, and during hourly cleanup while Chrome is running. Cleanup resumes when Chrome runs again. Browser storage limits or your own deletion may remove data earlier.

Settings and activity totals remain until you change or remove them, clear extension data, or uninstall the extension. Deleting History does not reset those totals or delete messages already sent to a chat provider. Removing the extension removes its local extension data through Chrome.

5. Security and permissions

CkretGuard does not add its own encryption to local History. Anyone who can access your unlocked browser profile or a copy of its data may be able to read saved prompts and credentials. Rotate exposed credentials and delete entries you no longer need.

Site access is restricted to the supported chat origins. It enables input recognition, local scanning, secret review, masking, and the selected submission. The storage permission saves local preferences and totals; scripting reconnects protection in supported open tabs after an extension update; alarms perform local retention cleanup. CkretGuard does not request access to all websites, your clipboard, or Chrome’s general browsing-history database.

6. Sharing and limited use

Orenthic does not sell prompt data, use it for advertising or creditworthiness decisions, or transfer it to data brokers. Extension data is used only for credential protection and its related user-facing settings, totals, and History. Orenthic limits data use to these features and does not allow employees to read your extension-local data. These restrictions implement the Limited Use requirements of the Chrome Web Store User Data Policy.

Orenthic cannot remotely read or delete your extension-local History. The extension does not provide a backend account, cloud backup, or automatic error-report upload.

7. Contacting us

If you choose to email support, your email provider and ours process the message, address, and any attachments you send. We use the information you voluntarily provide to respond to your request. Do not include real passwords, API keys, or unredacted prompts. We do not automatically attach extension data to email.

Contact: connect.orenthic@gmail.com

8. Visiting this website

This static website uses no analytics scripts, forms, or advertising cookies. It is hosted on Firebase Hosting. Google processes network information needed to serve and secure the website. Visiting this page does not grant it access to extension storage or your prompts. See Firebase privacy information and Google’s Privacy Policy.

9. Policy changes

We will update this page when relevant practices change and revise the date above. Review the policy alongside the extension’s current version and Chrome Web Store listing.