Privacy Policy

Records your organization imports or enters, such as tenant names, contact details, rent and balance figures, lease dates, notes, photos and documents. Sign-in details for each user, including the time and IP address of sign-in attempts and of accepting these terms. A history of changes made in the app.

[COUNSEL] Legal basis and roles (controller / processor) for each kind of record.

AtlasPM's code uses these services today:

• Supabase (PostgreSQL) — The database that holds AtlasPM's records, and storage for uploaded photos and files.
• Vercel — Hosts and runs the AtlasPM application.
• Anthropic — The AI model behind AtlasPM's AI features. Text from your records is sent to it when someone uses one of those features.
• Google (Gmail API) — Reads the mailbox your organization connects for email intake, when that is set up.
• Resend — Sends AtlasPM's outgoing email: account invitations, password resets, and messages staff send from AtlasPM.
• Sentry — Error monitoring. Receives technical details when something in AtlasPM fails.
• Upstash — Limits how often the public repair-request form can be sent, when it is configured.
• OpenStreetMap tile servers — Supply the map images on the portfolio map; your browser requests them directly.

[COUNSEL] Which of these are subprocessors, where data is stored, and the agreements in place.

[COUNSEL] Retention and deletion schedule.

Each organization sees only its own records, and staff other than administrators see only the buildings assigned to them. Passwords are stored as one-way hashes, not as text. [COUNSEL] Security commitments and breach notification.

[COUNSEL] Access, correction and deletion requests, and who to send them to.

[COUNSEL] Privacy contact.