Privacy policy.

1. Information the extension handles

DBXAuto processes the following information only to provide and configure its writing features:

Automatic completion uses up to 4,000 characters before the cursor and 500 characters after it. Prompted writing can also include up to 4,000 characters of selected text and a 2,000-character instruction, plus your voice preferences.

The extension does not separately access your email account, contacts, recipient list, or the rest of a webpage. Quoted messages or signatures inside the active writing field may be included within the context limits.

DBXAuto excludes password fields and other input types or attributes that identify common credential, payment, or identity fields. These checks cannot recognize every sensitive message. Ordinary writing may include names, personal communications, or other sensitive information; avoid using cloud generation for content you do not want the selected provider to receive.

2. Where writing requests go

If you explicitly select the legacy connection, the extension instead sends the request to the local bridge at 127.0.0.1:43127, which forwards it to the selected engine.

Requests include your writing context, applicable instructions, and voice preferences. DBXAuto does not silently switch providers. Provider-side retention, account logging, model improvement settings, international processing, and deletion options depend on your provider and account. DBXAuto does not control or promise a particular retention period for those services.

3. Storage, retention & security

Preferences, enabled hostnames, writing samples, API keys, and pairing tokens are stored in Chrome’s local extension storage until you change or clear them, remove the extension, or clear its data. DBXAuto does not use Chrome’s storage-sync API. It does not add its own encryption to local extension storage.

DBXAuto does not save writing requests or generated drafts as extension history, analytics, or developer logs. Transient request and draft data is held in memory while the feature is in use. The supplied Codex helper uses ephemeral requests and does not intentionally keep conversation history. Provider services, the operating system, browsers, or separately configured local applications may have their own data handling.

Text you insert remains subject to the website’s storage and privacy practices. If you choose Copy, that text enters your system clipboard and may be affected by clipboard history or synchronization settings.

Cloud requests use HTTPS. Requests to local Ollama or the optional bridge use HTTP loopback on your computer. Chrome native messaging is used for the automatic helper. Keep your computer and Chrome profile protected, and do not share provider keys or pairing tokens.

4. Browser permissions

• Active tab: identify the website and respond when you invoke the extension or its shortcuts.
• Scripting and website access: run the packaged editor integration in supported HTTP/HTTPS text fields, including reconnecting a page when requested.
• Storage: retain the preferences and credentials described above.
• Native messaging: communicate with the optional local ChatGPT helper.
• Provider host access: contact the local Ollama or bridge endpoints and Groq’s API.

Autocomplete is off for websites until you enable their hostname. You can explicitly open the writing prompt even while a site is paused. Only the packaged extension code runs in the browser; model responses are treated as text, never executable code.

5. Your choices & deletion

• Enable or pause individual websites, pause autocomplete globally, or restrict site access through Chrome’s extension settings.
• Choose your provider and model before generating text.
• Remove a website from the enabled list, clear writing samples, or edit voice preferences in DBXAuto settings.
• Clear the Groq API-key field and save to remove the saved key. Revoke the key with Groq if it may have been exposed.
• Remove the extension or clear its extension data to remove its saved local settings. Clearing a key or removing the extension does not revoke the credential at the provider.
• Manage Codex sign-in and uninstall the local helper separately if you no longer want that connection. Removing the extension does not sign you out of Codex or remove local applications.
• Use your provider’s controls or contact that provider to request deletion of data it retains.

DBXAuto’s developer cannot retrieve or delete your local extension data or provider-held request history remotely.

6. Limited use of information

DBXAuto uses information only to provide its disclosed writing-assistance features and user controls. It does not sell or rent user information, use it for personalized advertising, use it for creditworthiness or lending decisions, or transfer it for unrelated purposes.

Writing content and preferences are transferred to your selected provider only to fulfill the writing request. The extension does not send them to a developer-operated training or analytics service. The publisher’s use of information handled by DBXAuto complies with the Chrome Web Store User Data Policy, including its Limited Use requirements.

7. This privacy-policy website

This page does not include analytics scripts, advertising pixels, a contact form, or third-party fonts. Visiting it does not give this page access to your DBXAuto settings, writing content, or API keys. The hosting platform may process normal web-request metadata to deliver and secure the page. Visiting the external links on this page is subject to those websites’ own practices.

8. Publisher, contact & policy updates

Publisher: DBXLab

For privacy questions or requests, email privacy@dbxlab.pro.

If you contact DBXLab, DBXLab receives the contact information and message you choose to send and uses them to respond, resolve the request, and meet applicable obligations. Do not include API keys, passwords, or private writing content in support requests.

This policy will be updated when DBXAuto’s data practices change. The effective date at the top identifies the current version. Changes requiring additional disclosures or permissions will also be reflected in the extension and Chrome Web Store listing as applicable.