Data Requests

Data Requests and Deletion

This page explains how Atlas handles privacy requests, including access, correction, deletion, objection, restriction, and similar rights requests. Because Atlas is a B2B service, the correct request path depends on whether the request concerns public-website data or customer workspace data.

Back

Last updated: March 13, 2026

If your request concerns the public website or direct contact with Atlas

Send the request to support@iatlas.cc with the subject line "Atlas privacy request" and include your name, email address, organization, the country or state whose privacy law you are relying on if relevant, and the action you want Atlas to take.

If your request concerns an Atlas account provided by your employer or another Atlas customer

Contact your employer, customer administrator, or other authorized customer contact first. That customer organization usually acts as the controller for service data and must instruct Atlas on deletion, correction, export, or other action concerning workforce and operational records.

How Atlas verifies and processes requests

Atlas may ask for additional information to verify identity or authority before taking action.
If Atlas receives a request for data that Atlas processes for a customer, Atlas may redirect the request to that customer or confirm the request with the customer before acting.
Atlas keeps records of requests and responses where required for compliance, security, and audit purposes.

Deletion of business-user accounts

Atlas does not currently operate as a consumer self-signup product. Business-user accounts are generally provisioned, deactivated, or deleted by customer administrators or Atlas administrators acting on behalf of the customer. Backend administration APIs support deletion and deactivation of user accounts, but those actions should follow the customer governance process.

Deletion of operational records and photos

Operational records, audit evidence, and uploaded media may be subject to customer retention, regulatory retention, dispute preservation, or audit requirements. Atlas will not automatically erase customer-controlled records merely because an individual business user leaves a customer organization unless the customer instructs Atlas to do so and the deletion is lawful and technically appropriate.

Response timing

Atlas aims to acknowledge direct requests promptly and will respond within the period required by applicable law once identity and authority are confirmed. Timing may depend on whether Atlas is acting as controller or processing the data under customer instructions.

Atlas does not require a separate consumer account-deletion flow for the Android app based on the current product design, because the app does not provide open self-service account creation. If Atlas later enables in-app self-service account creation, Atlas should also publish a direct account-deletion URL and in-app deletion path that meet Google Play requirements.