Privacy Policy

Last updated:

This Privacy Policy describes how Atlas Disaster Management Solutions ("Atlas", "we", "us") collects, uses, and protects information when you use the atlasdisastermanagement.com platform, the Atlas DMS mobile applications (iOS and Android), and related services (the "Services").

1. Information we collect

We collect information you provide directly when you request a demo, register a tenant, create a user, or use the platform during debris operations — including names, contact information, organization affiliation, and role. The platform also captures operational records (load tickets, photos, GPS points, audit logs) on behalf of tenants who use Atlas to document debris work.

1a. Information the Atlas DMS mobile app collects

The Atlas DMS mobile applications collect the following data only while the app is in use by an authenticated, on-shift field user, and only to perform the documented debris-monitoring function. Nothing is collected in the background after the user clocks out.

• Precise location (GPS). Captured at debris pile locations, disposal site arrivals, hazard tree assessments, and at clock-in / clock-out events. Used to (a) write the location onto the ticket so it survives as audit-trail evidence, (b) evaluate geofence rules (auto-flag tickets logged outside a project boundary, allow remote clock-in only inside an authorized zone), and (c) display the user's current location to their on-shift supervisor for safety monitoring. Not used for advertising or behavioral profiling. Not shared with any third party.
• Camera + Photos. Used to capture the placard, load, measurement, and disposal photos that FEMA Public Assistance reimbursement requires. Photos are tied to the ticket they were captured for and visible only to authorized users in the same tenant. Not used for facial recognition or other biometric processing.
• Account identifiers. A user ID, session token, and device identifier are sent with every API request so the server can authenticate the caller and link activity to the audit trail. We do not collect advertising IDs (IDFA / AAID).
• Bluetooth. Used only when two on-site monitors need to pair phones at a disposal site to co-sign a ticket without cell coverage. Not used to scan for nearby devices, beacons, or personal accessories.
• Crash + diagnostic logs. Operational logs (sync queue state, error messages) are kept locally on the device to support troubleshooting. They do not contain photos or location coordinates beyond what's already in the affected ticket.

The mobile app does not include third-party advertising SDKs, behavioral analytics SDKs, or marketing trackers. We do not sell or rent personal information.

2. How we use information

We use information to operate the platform, respond to demo requests, support customers, ensure security of the Services, comply with legal obligations, and improve the product. Operational data captured during debris operations belongs to the tenant and is processed on their behalf.

3. Multi-tenant isolation

Atlas is multi-tenant. Each tenant's operational data is logically isolated; users from one tenant cannot read or modify another tenant's data. Atlas personnel access tenant data only as necessary for support, security incident response, or as required by law.

4. Data retention

We retain demo request information for 24 months unless you ask us to delete it sooner. Tenant operational data retention follows the tenant's contract; default retention is 7 years to align with FEMA Public Assistance closeout audit windows.

5. Subprocessors

We use third-party service providers ("subprocessors") to operate the platform — including infrastructure (AWS), email transport (AWS SES), DNS and edge security (Cloudflare), and productivity tooling. A current list is available on request.

6. Your rights

Depending on where you live, you may have rights to access, correct, delete, or port your personal information, and to object to or restrict certain processing. To exercise these rights, email [email protected].

7. Security

We use technical and organizational safeguards consistent with industry practices for SaaS platforms supporting government work, including encryption in transit, access logging, and role-based access control. Atlas is being designed with StateRAMP requirements in mind.

8. Changes to this policy

We may update this policy from time to time. Material changes will be communicated to active tenants and posted at the top of this page with a new effective date.

9. Contact

Atlas Disaster Management Solutions
Privacy questions: [email protected]
General contact: [email protected]