← Back to Shuttle

Data Disposal Policy

How to remove your data from Shuttle.

Updated September 17, 2026 · Shuttle Labs

This policy describes how Shuttle Labs handles deletion and disposal requests for the Shuttle waitlist and optional card-analysis service. Our Data Retention Policy explains the ordinary retention periods.

Current service status

The waitlist is operating and removal requests can be made by email. The financial-data analysis pilot is not yet open; its account controls and automated disposal processes must be verified before launch.

Choose what you want removed

How we process requests

  1. Verify the request. We use your authenticated account or confirm control of the registered email address. We will ask only for information needed to prevent someone else from deleting your data. We will never ask for your bank password.
  2. Confirm the scope. If necessary, we clarify whether you want financial-data deletion, waitlist removal, or full account removal.
  3. Remove live records and stop access. We delete the relevant application records and invalidate access where applicable. For financial-data deletion, we also request removal of the Plaid connection and delete stored connection credentials once revocation is completed or confirmed unnecessary.
  4. Check completion. We verify the affected records and pending processing. Provider outages or failed revocation may need retries and operator follow-up. We will distinguish a received request from completed disposal when responding.

We handle requests promptly and within applicable legal requirements. If verification, a provider outage or a preservation obligation delays completion, we will explain the outstanding issue when responding. No fixed provider-erasure deadline is promised on this page.

What financial-data deletion covers

For the pilot, disposal covers imported transaction records, balances and liability snapshots, imported account descriptions and masked identifiers, card selections, analysis reports, related pending report messages, and stored Plaid access credentials. A connection may remain marked for deletion while revocation is retried. We limit retained information to what is needed to complete that process.

Disconnecting a bank inside Plaid or at the bank does not necessarily remove previously imported information from Shuttle. Use Shuttle’s deletion control or contact us to request removal of that information too. Deleting information from Shuttle does not alter records held by your bank.

Disposal methods

We delete relevant live database records and revoke access credentials rather than merely hiding the information in the interface. Financial payloads are designed to be encrypted while stored. Encryption alone is not a substitute for deletion, and changing an encryption key is not our routine disposal method.

Cloudflare manages the physical storage infrastructure. We do not claim to directly overwrite its physical disks or immediately erase every underlying storage copy. Backup handling follows the boundaries described in our Data Retention Policy.

Backups, exceptions and disposal records

Data may remain temporarily in provider backups until those copies expire under the applicable retention arrangements. It must not be returned to ordinary use after a deletion request; deletion requests must be reapplied if a backup is restored. Provider backup settings for financial data must be verified before the pilot opens.

We may retain limited information when an applicable obligation requires preservation or when necessary to investigate a security incident or resolve a dispute. Access and use must be restricted to that purpose. We may keep a minimal record of the request and action taken, without copying the financial data being deleted into that record.

Contact and updates

Shuttle Labs is responsible for handling these requests. We will update this page when our disposal practices change.

For questions or a data request, contact Shuttle Labs at hello@shuttlecard.xyz. Please do not email bank passwords, full card numbers, or account access tokens.