Legal
Effective date: September 20, 2026
This page explains how to revoke connections and request deletion of data associated with Atomic Labs services, including data received through Google, Meta, Facebook, and other connected platforms.
To request deletion of your data, email atom@atomiclabs.tech with the subject line Data Deletion Request.
Please include enough information for us to identify the relevant account or integration, such as your name, company name, connected platform, account ID, ad account ID, or the email address associated with the service.
For Google, identify the Google account or Workspace organization and whether you want to disconnect access, delete retained data, or both. Do not send passwords, verification codes, private keys, or access tokens.
Depending on your relationship with Atomic Labs and the systems involved, we may delete:
If you connected a Meta or Facebook account to Atomic Labs, you may request deletion of Meta-related data retained by Atomic Labs by following the same process above. You may also remove Atomic Labs app access from your Meta or Facebook account settings at any time. Removing app access may stop future data access, but it may not automatically delete data already retained by Atomic Labs, so send a deletion request if you want retained data removed as well.
We honor verified requests to delete Google data within our control, subject to the Google-specific exceptions below. These Google-specific commitments take precedence over the general deletion and retention language on this page.
Remove an individual Google connection: Open your Google Account's linked-app settings, select the Atomic Labs connection, review its access, and choose the option to remove that access. Google provides instructions for reviewing and removing linked apps. If you use more than one Google account or connection, review each relevant one.
Remove a Workspace administrator-delegated connection: An individual linked-app setting does not remove domain-wide delegation. Ask a Workspace super administrator to open Security > Access and data control > API controls > Manage Domain Wide Delegation, identify the Atomic Labs client, and delete its authorization or remove the relevant permissions. See Google's domain-wide delegation instructions. Contact us if you need help identifying the client; do not remove unrelated clients.
Delete retained copies: Email atom@atomiclabs.tech using the process above. Revocation stops future access under that authorization, but does not automatically erase data already copied into assistant conversations, saved context, files, reports, caches, logs, or backups. A deletion request covers the relevant Google data and derived records retained by Atomic Labs, including copies processed by providers on our behalf.
After verification, we stop the requested connection or processing, remove credentials that are no longer needed, delete the covered records from active systems under our control, and request deletion by relevant service providers. We will tell you when active-system deletion is complete and identify any remaining backup copies or specific retention exceptions. Deleting our retained copies does not delete original messages, files, or other records in your Google account unless you separately request and authorize that action.
Revocation can disable features that need Google access. The Google-data commitments in our Privacy Policy continue to apply to any retained data.
We may need to verify your identity or authority before completing a deletion request. If the request relates to a business account, client workspace, or third-party platform connection, we may ask for enough information to confirm the request is authorized.
For data other than Google data, we may retain certain information where reasonably necessary for legal compliance, accounting, fraud prevention, security investigations, dispute resolution, backup integrity, or enforcement of our agreements. Where deletion is not possible, we may retain only what is necessary for those purposes.
For Google data, we may retain the minimum information required by applicable law or for a necessary, permitted security purpose. Business and accounting records may have separate legal retention requirements; that does not justify keeping unrelated Google message or file contents. Any retained Google data remains subject to the applicable Google-data restrictions, and we will explain the specific exception and retention criteria in our response.
Backup copies of Google data, where present, may take longer to remove than active records. They are removed through the applicable backup deletion or rotation process, are not used to continue the disconnected feature, and remain subject to the deletion request if a backup is restored. We will identify the relevant backup schedule in our response. A general business preference or a claim that data has been de-identified does not override Google's Limited Use requirements.
We aim to process deletion requests within a reasonable timeframe after verification. The exact timing may depend on the systems involved, backup cycles, contractual obligations, and legal requirements.
For Google data, we process verified requests without undue delay and within applicable legal deadlines. We will explain the expected timing, any identity-verification steps, and any remaining provider or backup deletion steps. Timing depends on the systems and records involved; disconnecting an account is not a promise of immediate erasure of all retained copies. You can contact us at the same address for a status update.
If you have questions about deletion requests or data handling, contact atom@atomiclabs.tech.