Back to home

Legal

Data Retention and Deletion

Last reviewed: October 18, 2026. Next review: on or before October 18, 2027.

This policy states how long ParseMania keeps personal data and consumer financial data, how we delete it, and how often we review these rules. It covers parsemania.com and the accounts-payable service, including data received from customers, Google, and Plaid. It is the schedule referred to in our Privacy Policy.

Controller: ParseMania, Switzerland. Requests: privacy@parsemania.com. This policy is written to meet the EU/UK GDPR storage-limitation and erasure rules, the Swiss Federal Act on Data Protection, U.S. state deletion rights including the CCPA/CPRA, and the Swiss ten-year duty to keep accounting records.

1. Rule

We keep data only for the purpose it was collected, for a period in the schedule below, or for a legal duty named in this policy. When that period ends, we delete the data or irreversibly anonymize it. We do not sell consumer data received from Plaid.

2. Schedule

DataHow longHow it is deleted
Account identity (name, email, firm membership)Life of the account, then 24 monthsDeleted or anonymized at the end of that period, or sooner on a verified erasure request
Sign-in secrets (password hash, authenticator secret, recovery codes)While the account or the authenticator is activeRemoved when MFA is turned off, the password is replaced, or the account is deleted
Billing and tax records (subscription, invoices we issue)10 yearsKept for the Swiss accounting duty, then deleted
Customer bookkeeping records (invoices, vendor bills, exports, journals, reconciliations)While the workspace is active. After closure, 10 years when the record is an accounting document; otherwise 24 monthsA workspace admin can delete a record in the product. The rest is deleted when its period ends
Plaid access tokensWhile that bank connection is activeDeleted when the customer disconnects the bank or the account is deleted. The Item is also removed at Plaid
Plaid consumer data (institution, account name and mask, transactions, payee, merchant, category, time, location, counterparty)While that bank connection and the workspace are active, so the customer can keep their books. After account closure, 10 years only for lines that are part of an accounting record; otherwise 30 daysDisconnecting the bank deletes that connection’s accounts and transactions. Account deletion removes the rest, subject to the accounting-record exception
Google OAuth tokens and mailbox or Drive watch stateWhile the Google connection is activeDeleted when the customer disconnects Google, revokes ParseMania in their Google Account, or the token is invalid
Files and messages ingested from Gmail or DriveWhile the workspace is active, unless the customer deletes them. After closure, the bookkeeping-record rule above appliesRevoking Google stops new reads. Copies already in the workspace follow the bookkeeping schedule
Server and security logs30 to 90 days, or longer if needed for an open security incidentRotated off when the period ends
Database backupsRolling 90 daysOverwritten as the window moves. A live-database deletion is complete in backups when that backup expires
Support and privacy correspondence24 months after the request is closedDeleted at the end of that period unless a legal claim is open
Cookie and marketing choices24 months, or until the visitor changes the choiceNon-essential tags stay off until the visitor opts in again

3. How deletion is enforced

  • Disconnecting a bank in the product removes that Plaid Item and deletes the stored accounts and transactions for that connection.
  • Disconnecting Google stops mailbox and Drive watches and deletes the stored refresh token for that connection.
  • A verified erasure or account-closure request to privacy@parsemania.com is completed within 30 days. Permanent account deletion removes the user and the firm, clients, invoices, and bank data that belong to that account.
  • Workspace users can delete individual bills, exports, and similar records in the product while the account is open.
  • Logs and backups expire on the periods in the schedule. We do not restore a deleted record from backup except to recover from an incident, and a restored copy is deleted again when the incident is closed.

4. When we keep data longer

We keep a record past its schedule only when we must: to comply with tax or accounting law, including the ten-year Swiss duty for accounting documents; to establish, exercise, or defend a legal claim; to comply with a lawful request from a court or authority; or to investigate a security incident that is still open. The hold covers only the records the duty requires, and it ends when the duty ends.

A deletion request under the GDPR, Swiss FADP, or CCPA/CPRA is honored inside 30 days except for data covered by one of those duties. Where a bookkeeping customer is the controller of invoice content about their own vendors, we direct the request to that customer when the law requires it.

5. Bank data from Plaid

Account and transaction data retrieved from the Plaid API is consumer financial data. We use it to show the customer their bank activity and to match it to bills. We keep it only as described in the schedule. Disconnecting the bank deletes it. Closing the account deletes it, except lines that have become part of the customer’s accounting record, which follow the ten-year accounting duty. Plaid access tokens are stored encrypted and are deleted with the connection.

6. Review

ParseMania reviews this policy at least once every 12 months, and sooner when the product, a connected provider such as Plaid or Google, or an applicable privacy or accounting law changes. The review checks that the schedule still matches the product and the law, and that deletion in section 3 still works. The date at the top of this page is the last review. The next review is due on or before the date stated there. A material change is posted on this page and, where the law requires it, sent by email or shown in the product.

7. Contact

To request deletion, access, or a correction, email privacy@parsemania.com. We may need to confirm that you control the account. EU and UK users may also complain to their supervisory authority. Swiss users may contact the Federal Data Protection and Information Commissioner (FDPIC).