Your recurring spending is not a product.

Browser bundles and optional accounts

Without an account save, your working bundle stays in this browser's local storage. Sample discovery is no longer offered. Signing in uses ChatGPT authentication; Dehaze does not collect your password. Only choosing and confirming Save uploads your bundle to Dehaze's server database.

One account record contains a site-specific authenticated user identifier, your saved services, plans, amounts, billing frequencies, decisions and replacement choices, plus a revision and save time. Dehaze does not persist your sign-in email in this record. These records are not added to affiliate records, advertising profiles, or product-measurement aggregates.

In My saved bundle, load your account copy to access it, edit and save to correct it, or choose Delete saved bundle to remove that bundle from active storage. This does not disconnect financial test connections or delete their consent records. Loading replaces the browser copy only after confirmation. Signing out leaves the browser copy in place; clear it separately on a shared device using the controls above. Deleting Dehaze data does not delete your ChatGPT account.

Financial connections

Production financial connectivity is disabled. Restricted Plaid Sandbox testing uses simulated institution data, requires sign-in and explicit versioned consent, and loads Plaid’s interface only when a tester chooses to connect. With consent, Dehaze retrieves recurring-charge summaries and retries processing results up to twice while the review page stays open. On-demand discovery results remain in page memory unless you separately choose to save reviewed test costs. No real bank connection is available.

Optional background Sandbox monitoring requires separate consent for each connection and must first be enabled by the operator. When its scheduler runs, it checks no more than once every six hours per enrolled connection and stores an encrypted temporary summary, site-specific account identifier, hashed tester identifier, consent and job-status timestamps. Summaries become unavailable after 24 hours and are removed on later maintenance runs; scheduling outages can delay physical deletion. Monitoring never changes either saved bundle. On Connect accounts, you can view or download monitoring records, or stop monitoring and delete them. Disconnecting also removes the active monitor and temporary summary, including when provider removal needs a retry. Downloaded copies and provider logs/backups are separate. No affiliate, advertising or marketplace use is permitted.

Explicit test-saving consent stores one encrypted test snapshot per signed-in account, separate from the real bundle. It contains selected costs, service labels, source-check references and its consent receipt until you replace or delete it. You can view, download or delete it on the review page; disconnecting a bank does not automatically delete a separately saved test snapshot. Deleting removes the active record, not downloaded copies or provider logs/backups. Test snapshots are excluded from affiliate, advertising and product-measurement systems. Do not enter real financial information into Sandbox tests.

For a Sandbox connection, Dehaze stores your site-specific account identifier, an encrypted connection token, institution name, account names/types, masked last digits, and consent/status timestamps. It does not store balances or bank passwords. These records are separate from affiliate, advertising and product-measurement systems.

Use Connect accounts to download your connection records or disconnect. After Plaid confirms removal, Dehaze clears the stored token and account labels. If removal fails, the connection is locally revoked and the encrypted token is retained for retry; the interface does not report a successful disconnect. Consent/status records remain until you separately confirm Delete connection record. Unresolved disconnects and uncertain exchanges cannot be deleted through that control.

Confirmed record deletion removes the connection details and consent receipt from active Dehaze storage. A minimal internal attempt identifier, site-specific user identifier and original attempt time may remain to enforce the original rolling 24-hour attempt limit. Expired attempt-limit records are removed on your next connection attempt, confirmed record deletion, or an operator-configured maintenance run. Automated removal depends on an active scheduler and available hosting; a fixed removal deadline is not guaranteed. Your saved bundle, downloaded copies and provider logs/backups are separate. Contact us for correction or broader deletion requests; these controls do not guarantee erasure of provider-held copies.

Bank-derived information is prohibited from commercial use in V1. No future commercial use is permitted without specific informed affirmative consent, strict data separation, qualified legal review, and confirmation that the proposed use is lawful under then-current financial and privacy rules. Future permission is not assumed.

Affiliate attribution

Affiliate tracking remains disabled unless a program has specific approval evidence and an approved tracked destination. When an approved, clearly disclosed tracked link is active, the system may store a random pseudonymous click identifier in a 30-day cookie together with the placement, provider, program, page context, commercial status, and time. That record is separated from financial and manual recurring-spending data.

Catalog and provenance data

Official provider URLs, plan conditions, verification dates, price observations, and source evidence are product records rather than personal records. New price observations are appended so a later verification does not silently erase earlier evidence.

Privacy-safe product measurement

The site counts broad page types, coarse traffic-source categories, and a small set of product actions in daily aggregates. It does not create visitor histories or store full URLs, referral URLs, IP addresses, device identifiers, user-agent strings, cookies, merchant names, entered amounts, ZIP codes, plan choices, financial records, or recurring-spending bundle contents for product measurement.

To understand whether broad sources such as search or AI assistants lead to useful actions, the tab keeps only that source category for the visit. It does not keep the original referral address or assign a visitor or session identifier. Aggregate rows older than 400 days are removed when a new measured event is recorded; removal is not currently scheduled during inactivity.

Global Privacy Control and Do Not Track signals disable this measurement in supporting browsers. Measurement failures never block the consumer experience.

Product measurement does not require a Dehaze account, create analytics cookies, or attach recorded counts to a person. The protected owner report is separate from the public consumer experience and aggregate records.

Retention and removal limits

Saved recurring-spending entries remain on this device until you remove them or clear browser site data. The controls above clear saved entries, not server-side records or previously recorded aggregate counts. Aggregate counts have no visitor identifier for locating one person’s contribution.

An account bundle remains until you replace it or delete account data; there is no automatic inactivity deletion currently. Dehaze does not keep an application-level version history of bundles. Provider logs or backup copies may have separate retention. A verified bundle backup or restore service is not currently available; keep a personal copy of information you cannot afford to lose.

Consent receipts and any future affiliate click or conversion records are separate server records. Their approved retention periods and deletion procedures remain launch or activation gates; cookie expiration is not deletion of a server record. Hosting access logs and backups have separate platform controls and cannot be erased by these browser buttons.

For data controlled by OpenAI, its published privacy policy states that Personal Data selected for deletion is removed from its systems within 30 days unless a stated legal, security, fraud, financial-record, or other permitted exception applies, or the data was already de-identified and disassociated. Requests can be submitted through OpenAI's Privacy Portal. This provider-level baseline does not establish a specific active-site log lifetime, backup window, or restoration process for Dehaze.

Public-beta boundary

Before public-beta indexing is enabled, Developer Studio Tampa LLC will confirm the operational contact, deployed security controls, and any qualified legal review appropriate to the release. Production financial connectivity will remain disabled through this launch step.

Contact

For access, correction, deletion, revocation, or another privacy inquiry, email devstudiotampa@gmail.com.

Include only the request type, the relevant Dehaze page or browser, and a safe reply address. Do not send bank credentials, full transaction histories, bundle exports, passwords, or identity documents unless specifically requested through a verified follow-up.