How ATLO handles account, project, customer, and device information.

Last updated: August 6, 2026. This page is based on the current ATLO app codebase and its internal privacy and permissions documentation.

Summary

ATLO collects the information needed to run shop workflows.

That includes account details, customer and project data, messages, optional uploaded photos, notifications, and limited analytics or diagnostic information used to keep the app working.

1. Information ATLO collects

Based on the current app implementation, ATLO may collect and store:

Account data such as email address, display name, optional phone number, photo URL, shop ID, role, and account timestamps.
Customer data entered into projects, including customer names, phone numbers, email addresses, and email opt-in preferences.
Project data such as titles, descriptions, statuses, start dates, due dates, end dates, updates, and related image URLs.
Messaging data such as message text, sender ID and name, timestamps, image URLs, and project or thread associations.
Notifications and operational logs used to support shop activity and system events.
Locally cached project and user data stored on the device for performance and offline resilience.

2. How ATLO uses information

To create and secure user accounts.
To associate users with a shop and role.
To organize projects, updates, messages, and customer records.
To store and display uploaded photos and avatars.
To send notifications and maintain app operations.
To improve reliability, troubleshoot issues, and monitor usage through analytics and diagnostics described in the app documentation.

3. Permissions and device access

ATLO currently documents these permissions and access patterns:

Camera access when a user chooses to take a project or message photo.
Photo library access when a user chooses to upload an existing image.
Phone calling support when a user taps a phone action such as calling a client.

These permissions are intended to appear only when the related feature is used, not automatically on app launch.

4. Services used to run the app

The current repo documents use of the following services:

Firebase Authentication for sign-in and account management.
Cloud Firestore for application data storage.
Firebase Storage for images and other uploaded media.
Firebase Functions for backend processing.
Firebase Dynamic Links for deep linking.
Firebase Analytics and Crashlytics, as documented in the app privacy summary, for usage and reliability information.
SendGrid or similar mail delivery tooling when email delivery is configured.

5. Storage and security

Remote data is stored in Firebase services used by the app.
Some project and profile data may be cached locally on the device using the app sandbox.
The codebase documents shop-based access controls, user-based storage rules, image validation, file size limits, and input validation.

6. Tracking and advertising

The internal permissions documentation states there is no evidence of advertising SDKs, attribution SDKs, or cross-app tracking using IDFA in the current app implementation. If that changes in the future, this page should be updated.

7. Your choices

You choose whether to upload project photos, avatars, or message images.
You choose whether to use camera, photo library, or phone call features.
Account creation currently requires accepting the Privacy Policy and Terms and Conditions in the app sign-up flow.
If you have questions about your information or account, use the Contact page on this site.