Data retention
and deletion policy

This Data Retention and Deletion Policy explains how Vezio retains and disposes of personal information used to provide its financial tracking service. It applies to information in Vezio’s control, including account records, Plaid-sourced data, other connected financial data, provider credentials, financial history, operational logs, and recovery copies. It supplements our Privacy Policy. Vezio’s operator is responsible for administering this policy and handling retention exceptions and deletion requests.

Vezio retains personal information for the purposes for which it was collected: operating user accounts, maintaining authorized connections, displaying financial information and history, providing support, protecting the service, and meeting applicable legal requirements. Information must not be kept merely because storage is available. When the service purpose ends, Vezio must delete the information or document a specific legal, security, or dispute-resolution reason for continued retention. Removing a connection starts permanent erasure of that connection’s stored data and history. Account deletion retains the limited former-user record described below.

The following schedule distinguishes current technical settings from retention decisions requiring manual administration. Earlier deletion may apply following a verified request or where required by law.

Website waitlist

The submitted email address, signup time, and signup source are kept in a private encrypted AWS DynamoDB table while needed for the requested Vezio availability update. There is no automatic expiry of active entries. Removal requests sent to business@meshapi.app are handled manually, and the operator must remove entries once they are no longer needed. Protected recovery copies expire within seven days after removal; completed removal requests must be reapplied after restoration. The signup function’s operational logs have 14-day retention and do not intentionally log submitted addresses or request bodies.

Account and profile records

Email address, account identifiers, preferences, and user-entered information are retained while needed to provide the account. On verified account deletion, the deletion procedure below applies. There is currently no automatic deletion solely because an account has been inactive for a set period.

Former-user identity log

After account deletion, Vezio retains only name, email address, a separate random record ID, and deletion date in a separate encrypted database, indefinitely until manually deleted, for compliance recordkeeping and tracking former users. This is an operator retention decision, not a claim that indefinite retention is legally required. The log is excluded from signup, login, account linking, provider refreshes, and account recovery. It has no email uniqueness constraint; a new account with the same email receives an independent account identity. Only authorized operators may access or manually delete log entries. Applicable privacy rights and legal requirements still apply.

Connected financial data

Balances, accounts, transactions, holdings, liabilities, recurring-payment information, wallet addresses, and market positions are retained while needed for the user’s authorized tracking and history features. These records do not all have a fixed automatic age limit. Removing a connection erases its financial data, historical chart contributions, and credentials. Other sources and separately entered credit scores remain until separately removed or the Vezio account is deleted.

Investment chart readings

The current history-compaction process keeps hourly readings for approximately eight days, then generally one reading per day, with additional account-start readings where needed for comparisons, within a 400-day window. Compaction runs when history is processed, rather than as an independent deletion timer. These limits apply to current chart history, not all transactions or historical storage versions.

Provider access tokens and API credentials

Kept in a separate encrypted credential store while needed for an authorized connection. This store has no configured versioning, recovery backups, or change streams. Removing a connection erases its credentials and explicitly removes old financial-storage versions that may contain legacy credentials. All accounts sharing a bank link, or the Kalshi key, are disconnected together. Plaid access is revoked; users should also revoke self-created exchange API keys in the provider’s settings. Vezio’s backend can decrypt credentials to perform authorized requests; encryption does not mean they are inaccessible to the service.

Operational and authentication logs

The main backend application log group is currently configured for 14-day retention. Other logs, including authentication-link logs, do not all have automatic expiry. The operator must review these logs for continuing operational or security need and manually remove unnecessary records or apply an appropriate expiry setting. A documented incident or legal requirement may justify preserving relevant records longer.

Recovery copies and historical versions

Metadata recovery uses a rolling 35-day point-in-time recovery window. Successful financial-state writes explicitly purge older user object versions; connection and full-account deletion verify their version cleanup before completing. A one-day noncurrent-version lifecycle rule provides an additional, asynchronous backstop; it is not an immediate-erasure guarantee. Existing legacy state migrates on a successful save or scheduled refresh. Connection deletion markers contain only opaque request identifiers after completion and prevent serving restored data that predates deletion. The separate credentials and former-user databases have no configured recovery backups.

Support and privacy-request records

Retained for the time needed to resolve a request and, where necessary, maintain limited evidence of its handling or address a dispute. The operator must remove unnecessary attachments and financial details and document any continuing need to retain a request record.

The Remove and delete action stops collection and permanently erases a connection’s saved balances, transactions, holdings, credentials, and historical contributions, including old storage versions. A bank link and its accounts are removed together because they share access; both Kalshi views are also removed together. Charts are recalculated from the remaining sources. The app explains this scope before confirmation. Provider accounts remain open. Users should revoke self-created exchange API keys at the provider. If cleanup fails, a durable job retries and financial syncing and access are paused until erasure finishes. The app does not report completion before cleanup succeeds. Cached financial displays and card preferences are cleared or reconciled when a device next contacts the service; Vezio cannot remotely erase an offline device, independently saved export, screenshot, or user-controlled device backup.

You can start full-account deletion in Settings → Account → Delete account. Confirm the request and freshly verify that you control the same account. The app shows progress and the result of the deletion process. Some provider cleanup may require an additional action; follow any instructions shown.

You can also email business@meshapi.app with the email address used for Vezio and whether you want the whole account or a specific source’s data deleted. Do not send passwords, API secrets, wallet seed phrases, or identity documents unless a secure verification process has been agreed. We may verify account control. Requests that need manual handling are addressed without undue delay and within applicable legal deadlines. If an exception or permitted extension applies, we explain it as required by law.

For a verified full-account deletion, Vezio’s automated process and any necessary operator follow-up perform these steps:

1. Identify the correct user and the scope of the request, and check for a specific retention exception.
2. Stop future collection, remove the user from scheduled refresh processing, and allow or cancel in-flight work safely so that it cannot recreate deleted records.
3. Revoke applicable provider connections and sign-in sessions where supported, and remove the user’s authentication account and stored connection credentials.
4. Delete the user’s active financial records, other profile details and service metadata, and identifiable historical storage versions. Retain only the disclosed name, email, separate record ID, and deletion date in the restricted former-user log. A delete marker or removal of the latest version alone is insufficient for versioned storage.
5. Address relevant logs, support files, working copies, and recovery data. Restrict any retained exception records to their documented purpose.
6. Verify completion, record the outcome using only the minimum necessary information, and respond to the requester.

Deletion uses the storage and service providers’ supported deletion mechanisms. Vezio does not claim to physically overwrite individual sectors on shared cloud hardware. Removing server-side information does not necessarily erase a user’s independently saved screenshots, exports, or device backups.

Recovery data must be used only for recovery, security, or another documented permitted purpose. Where individual records cannot be selectively removed from a rolling recovery backup, they remain protected until that recovery window expires. For the current metadata recovery system, that window is up to 35 days. Separately stored object versions are explicitly purged during deletion, with the noncurrent-version lifecycle rule as a backstop. Do not enable independent backups, exports, replication, or change streams for the credentials or former-user databases without updating the deletion design and this policy. If a backup is restored, completed deletion requests must be reapplied before the restored data is returned to normal service. The current deletion journal must never be rolled back with an older financial snapshot. Its opaque epoch must match before a restored snapshot can be served. Recovery copies must not be used to reactivate a deleted user’s account or resume collection without new authorization.

A legal obligation, valid preservation request, security investigation, fraud prevention need, or active dispute may require limited retention beyond the normal service purpose. For each exception, the operator must record the reason, the affected data, the access restrictions, and a review date or event that ends the exception. Only necessary information may be retained, and it must be deleted when the exception ends. Exceptions do not permit indefinite retention for an unspecified future use.

Vezio’s deletion process applies to information under Vezio’s control. Disconnecting an Item or deleting data in Vezio does not automatically erase information held independently by Plaid, a bank, an exchange, or another provider. Users can manage eligible Plaid connections or submit requests through Plaid Portal; Plaid’s own practices are described in its End User Privacy Policy. Public blockchain records cannot be removed by Vezio. Applicable provider agreements and legal requirements govern any additional obligations.

The Vezio operator must review this policy and relevant retention settings at least annually and when material storage, provider, or product changes occur. Reviews must identify records without automatic expiry and arrange manual cleanup where needed. Changes to retention periods or exceptions must be documented. Retained personal information remains subject to Vezio’s access controls and encryption protections; access must be limited to authorized systems and personnel with a service, security, support, or legal need. This policy specifies both existing automated settings and procedures requiring manual execution; publication alone does not establish that a review or deletion has been completed.

For retention questions or deletion requests, contact business@meshapi.app. Read the Vezio Privacy Policy for information about collection, use, sharing, and privacy choices. Applicable law takes precedence if it requires a different retention or response period.