Privacy Policy

# Privacy Policy for BrigadeMate

Effective Date: 20 January 2026

## 1. Overview
This Privacy Policy explains what data the BrigadeMate application processes and how it is used. The app supports project management, materials and tasks tracking, team collaboration, photos, and messaging.

Data Controller/Operator: Artur Carp, Causeni, Moldova 4304

By using the app, you agree to this policy.

## 2. Data We Collect
### 2.1 Account Data
- Email and password for authentication (passwords are handled by Firebase Authentication).
- Display name and user role within projects (foreman/worker).

### 2.2 User Profile
- First and last name, company name.
- Email, phone, address, tax ID (if provided by the user).
- Notification preference (notificationsEnabled).
- Subscription/access metadata (for example: plan tier, subscription status/source, expiry timestamp).
- Entitlement and feature-access flags used to apply Free/Pro limits.

### 2.3 Project and Workflow Data
- Project data: address, type, description, status, budget, deadline, currency.
- Client contact details: name, phone, email (if entered).
- Materials, tasks, tools, work logs, keys/custom fields.
- Team members: name, email, phone, role, comments.
- Project messages (text, sender, timestamps, read status).

### 2.4 Photos and Files
- Photos uploaded by users (stored in Firebase Storage).
- PDF exports generated by users, which may include project and contact data.

### 2.5 Notifications
- Expo Push Token for push notifications.
- Active chat project identifier (activeChatProjectId) to manage notification delivery.

### 2.6 Technical Data
Firebase and Expo may process technical data such as IP address, device information, app version, and error logs to provide and secure the service.

### 2.7 Billing and Plan Data
To provide subscription access and enforce Free/Pro limits, we may process:
- subscription identifiers (internal and store-side);
- billing event records (for example purchase, renewal, cancellation, expiration, refund);
- entitlement status and period dates;
- product identifiers and platform source (web / app store / google play).

For App Store / Google Play purchases, payment card data is processed by the store provider, not by BrigadeMate servers.

## 3. Data Sources
- Data you enter directly (profile, projects, contacts, notes).
- Data generated during app use (messages, logs, project activity).
- Data automatically provided by Firebase and Expo (technical data, push tokens).

## 4. Purposes and Legal Basis
We use data to:
- register and authenticate users;
- provide project management and collaboration features;
- store and display project content (tasks, materials, photos, logs);
- send push notifications;
- maintain security and reliability.

Legal basis: performance of a contract (service delivery) and user consent where required.

## 5. Storage and Security
Data is stored within Firebase infrastructure (Firestore, Storage, Authentication, Cloud Functions). Access is restricted through Firebase security rules and authentication.

Deleting a project removes related records and files (including photos in Storage). Account deletion is available in the app (Menu > Security > Delete Account) or by contacting the operator if you cannot access the app.

## 6. Sharing With Third Parties
We use third-party providers to run the service:
- **Google Firebase**: authentication, database, file storage, cloud functions.
- **Expo**: push notification delivery.

These providers process data under their own policies as service processors.

## 7. International Transfers
Firebase and Expo may process data on servers located outside your country, which can involve cross-border transfers.

## 8. Your Rights
You can request access, correction, or deletion of your data. Contact the operator using the details below.

## 9. Cookies and Analytics
The app records product usage and operational events in Firestore (for example: task/material/worklog/finance events) to monitor reliability and improve product decisions.
For BI reporting, analytics events may be exported to BigQuery.
Mobile builds do not use browser cookies.

## 10. Marketing and Communications
Marketing emails are not implemented. Notifications are limited to in-app events (for example, messages and reminders).

## 11. Children
Age restrictions are 16+.

## 12. Changes to This Policy
We may update this policy. The new version becomes effective on the publication date.

## 13. Contact
Privacy contact: brigademate@gmail.com