Privacy Policy

This policy explains how Global GLA Enterprise, a company registered in Colombia trading as “AlarmSight” (“we”, “us”, “our”), collects, uses, shares and protects information in connection with the AlarmSight platform (the “Service”).

1. Our role

AlarmSight is sold to fire alarm companies, dealers and integrators (“Partners”), who may make it available to their own building clients.

• For the account data of the Partner and its users, we act as the controller.
• For building, device and signal data that a Partner connects or uploads, we act as a processor on that Partner’s behalf. The Partner decides what data enters the Service and who may see it.

If you are a property manager or building user, your relationship is with your fire alarm company. Direct requests about your data to them in the first instance.

2. Information we collect

Account information. Name, work email address, role, the organization you belong to, and the credentials used to sign in. Passwords are stored only as salted hashes; we never see your plaintext password.

Business and building data. Building names and addresses, floor plans you upload, device inventories and their positions on the plan, inspection records, customer records, and related notes.

Central station credentials and signal data. Where a Partner enables an integration, we store the credentials needed to connect to that central station and we retrieve alarm, trouble, supervisory and related event records for the accounts the Partner has authorized. Credentials are stored encrypted and are used only to fetch that Partner’s data.

Usage and technical data. Log records such as IP address, browser and device type, pages accessed, timestamps and error diagnostics, used to operate and secure the Service.

Payment data. Purchases are handled by Paddle, our merchant of record. Paddle collects and processes your payment details directly. We do not receive or store full card numbers. We receive the subscription status, billing contact and invoice records needed to run your account.

3. How we use information

• To provide, operate, secure and support the Service.
• To authenticate users and enforce access rules between organizations.
• To display live status, event history, inspections and reports to authorized users.
• To process subscriptions, invoices and renewals through Paddle.
• To send transactional messages such as invitations, password resets and service notices.
• To diagnose faults, prevent abuse, and improve reliability and performance.
• To comply with legal obligations.

We do not sell personal information, and we do not use your building or signal data to train third-party models or to market to your clients.

4. Service providers we rely on

We use a small number of infrastructure providers to run the Service:

These providers process data on our instructions and are bound by their own confidentiality and security obligations.

5. Sharing

We share information only: with the service providers listed above; between users within the same organization, according to the roles and permissions configured by that organization; with a Partner’s building clients where the Partner has granted them access; where you instruct us to; and where required by law, legal process, or to protect the rights, safety or property of any person. If the business is transferred as part of a merger, acquisition or sale of assets, data may transfer with it, subject to this policy.

6. International transfers

We operate from Colombia and our infrastructure providers process and store data in the United States and other countries. By using the Service you acknowledge that your data may be transferred to and processed in countries other than your own, with appropriate contractual protections in place with our providers.

7. Retention

We keep account and business data for as long as the account is active. Event and signal history is retained so that it remains available for compliance and reporting. After an account is closed you may request an export within thirty (30) days; after that period we delete or anonymize data, except where we must retain records for legal, tax or accounting purposes. Backups are cycled out on a rolling basis.

8. Security

We use encryption in transit (HTTPS/TLS), encryption at rest for stored files and credentials, row-level access controls that isolate each organization’s data, role-based permissions, hashed passwords, and private storage for floor plans served through expiring signed links. No system is perfectly secure; you are responsible for keeping your credentials confidential and for removing users who should no longer have access.

9. Your rights

Depending on where you live, you may have the right to access, correct, export, or delete your personal information, to object to or restrict certain processing, and to withdraw consent. Colombian users have rights under Law 1581 of 2012; users in the EEA/UK and certain US states have comparable rights. To exercise them, contact us at the address below. If we process the data on behalf of a Partner, we will refer your request to that Partner and assist them in responding.

10. Cookies

The application uses cookies and similar browser storage that are strictly necessary to keep you signed in, maintain your session, and remember interface preferences such as theme. We do not use advertising cookies or third-party tracking for advertising purposes. Blocking necessary cookies will prevent the application from working.

11. Children

The Service is a business tool and is not directed to children. We do not knowingly collect personal information from anyone under 18.

12. Changes to this policy

We may update this policy. When we make material changes we will update the effective date above and, where appropriate, notify account administrators.

13. Contact

Privacy questions and requests can be sent to contact@alarmsight.io.