Privacy policy

Who we are and what role we play

ResiSecure is a platform for managing gated residential communities (access control, guard post, fees and communication with residents). It is operated by Kevin Ivan Cruz Medina, an individual based in Tela, Atlántida, Honduras (“ResiSecure”, “we”).

There are two distinct roles:

• Your residential community is the controller of the data about its residents, households, visitors, access events and fees. It decides who it registers and what for. ResiSecure processes that data on the community’s behalf, to provide the service, and following its instructions.
• ResiSecure is the controller of your account data and its security (credentials, security logs), of what you send us through our website forms, and of the information needed to contract with each community.

What data we process

• Account and household: name, email, phone, ID type and number, profile photo if you upload one, and the composition of your household. The head of household may register other members, including minors, who do not get their own account.
• Visitors: name, ID and vehicle plate where the community requires it, the reason for the visit and the pass with its QR code. The inviting resident enters them; the visitor has no account.
• Access log: date, time, direction (entry or exit), visitor and the guard who validated it.
• Payments and fees: amounts, fee status and the receipts you upload (photo or PDF), with whatever they contain, such as the bank, reference, date and amount. We do not process card payments: we only receive the receipt of a transfer or a payment made outside the app.
• Notifications: your device token and a random identifier the app creates when it is installed, to send push notifications, and your phone number, to send codes and notices through WhatsApp. Firebase, the Google service that delivers push notifications, also assigns its own identifier to the app installation.
• Technical and security data: IP address, device type and sign-in and error logs, to protect accounts and diagnose faults.
• Data stored on your phone: the session (in the system’s secure keychain), a recent copy of your payments and, at the guard post, the access database that allows validation without a connection. That database is excluded from phone backups.
• Camera and photos: the camera reads QR codes on the phone itself and the image is not sent anywhere. A photo only leaves the phone when you pick a receipt and send it.

We do not sell data, show ads, or profile or track you across apps.

What we use it for, and on what basis

• Providing the service to the community and its residents: access control, guard post, fees, notices. Basis: performance of the service your community contracts.
• Protecting accounts and detecting abuse. Basis: our legitimate interest in the security of the service.
• Sending push notifications and WhatsApp messages. Basis: your consent, which you can withdraw in your phone settings or by asking us.
• Reading the amount, date and reference from a receipt so you do not have to type them. Basis: the service you request by uploading it.
• Answering your questions and demo requests. Basis: your request.
• Measuring use of our website, only if you accept it in the cookie notice.

Who we share it with

We use providers that process data on our behalf, under the safeguards in their terms:

• Render, Vercel and Cloudflare, for hosting and for delivering the website, the portal and the API, and Neon, which hosts the database.
• Meta (WhatsApp Business), for codes and notices through WhatsApp and for receiving receipts sent that way.
• Google: Firebase Cloud Messaging for push notifications, whose text (for example, the name of the visitor who arrived or the status of a payment) passes through Google to reach your phone, and the Gemini API for reading receipts. Google processes the image to return the result.
• The email provider that sends account messages.

We also share data with your community (its administration and guards see what their role allows) and where a competent authority legally requires it.

Some providers are outside Honduras, so your data may be processed in other countries, including the United States. We choose providers that offer contractual and technical protections.

How long we keep it

• Access logs: 365 days by default. Each community can change the period, and once it passes they are deleted automatically.
• Account: while it is active. When you delete it, your personal data is anonymised.
• Billing, fees and receipts of recorded payments: as long as the community’s accounting obligation requires. A receipt for a payment that is cancelled or rejected is deleted with it.
• Backups: are managed by our hosting provider and deleted on its rotation schedule; a deleted record can remain in them until that rotation overwrites it.
• Visitor and pass data: while the pass is valid and the access-log period requires it.

How to delete your account

In the app: Account, Privacy and data, Delete my account. You can also request it on the delete-account page of this site or by writing to us. When you delete it, your personal data is anonymised, and the household’s access and billing records are kept, unlinked from you, until their retention period passes. A community administrator cannot delete their own account from the app: another administrator does it.

Your rights

You can ask for access, correction, updating, deletion or objection to the processing of your data, and withdraw your consent where processing is based on it. Where your community is the controller of your data, you can contact its administration, and we will help it to respond. For anything else write to privacidad@resisecure.com. We answer within 30 days. If you are not satisfied, you may go to the competent authorities in Honduras.

Security

Communications are encrypted, passwords are stored hashed, each community’s information is isolated from the others, and each person’s permissions depend on their role. No system is infallible: if a breach affects you, we will notify you and tell your community.

Minors

The app and the portal are not aimed at people under 18 and we do not create accounts for them. The data of minors that the head of household registers as household members is processed by the community as controller.

Changes to this policy

If we change this policy in a material way, we will tell you in the app or by email before it applies. The date of the last update appears above.