Skip to content

Privacy policy

Last updated 3 November 2026

Terms of service

Working wording, pending review by legal counsel. It describes what the platform does today.

DecyfoGate Estates is a community access platform operated by DecyfoTech. This page says what personal data the platform handles, on what basis, why, who can see it, how long it is kept, and what a person can ask us to do about it. It is written for the Nigeria Data Protection Act 2023. The community on the platform is the data controller of its own records and its own policy applies to what it does with them; this page covers what the platform itself does.

Who is responsible for what

A community decides what to record about its residents, households and visitors, and why. That makes the community the data controller for its records, and DecyfoTech the data processor: we handle them on the community instruction, for the community, and for no purpose of our own. For the platform account itself, the sign-in details and the technical records of a request, DecyfoTech is the controller, because those exist to run and protect the service rather than to run the community.

What we hold

The platform handles the data a community needs to run its gates:

  • Account details for the people who sign in: a name, an email address or phone number, a role, and a password or a one-time code. A guard may also have a staff number.
  • For each resident: the unit they hold or live in, the household people and personnel they add, and the invitations and claims that connect them to a unit.
  • For a visitor pass: the visitor names the resident supplies, an optional phone number and vehicle registration, the gate and the expected window, and the arrival and departure times the guard records.
  • For a gate record: the event, the gate, the time, the host and unit, the visitor name and the vehicle plate where one was given. A guard sees the host and the unit, and not the visitor contact details.
  • What the server sees when a request arrives: an IP address, a timestamp, and the action taken. Privileged and gate actions are recorded in an audit log with the account that took them.

Why we handle it, and on what basis

Under the Nigeria Data Protection Act 2023 we need a lawful basis for each purpose, and these are ours. Account details are handled to perform the agreement with the community and with the person signing in. Community records are handled on the community instruction as processor, which rests on the community own basis with its residents. Security records, the audit log and the technical request log, are handled for our legitimate interest in keeping the platform working and answering for what happens on it, and we keep that to what the purpose needs. The measurement on the public pages, our own visitor count and, where this deployment is configured with one, the Meta pixel, is handled for our legitimate interest in measuring our advertising and understanding which public pages are read; it carries no account or visitor record and never runs on a signed-in screen. A one-time sign-in code is handled with the consent of the person it is sent to, and is spent the moment it is used.

Visitors at the gate

A visitor does not hold an account. The resident creates the pass and supplies the visitor name, and optionally a phone number and vehicle registration. The visitor can open the pass link to see the window and a six digit PIN, which the guard asks for at the gate. The guard sees the host, the apartment or block, the expected party size and the window, and not the visitor phone number or plate, except for a walk-up the guard logged. The pass link and the PIN stop working when the pass is revoked, expires or is checked out.

Who can see it

A community sees its own records and nothing belonging to another community; the platform enforces that boundary on every request rather than only in the interface. A resident sees the units they are connected to, their household and their own gate history. A guard sees the expected list, the inside list and the log for the gates they cover. A Community Admin sees the community. A member of DecyfoTech staff can reach platform-level records, and that access is limited to the work in hand, and a privileged action carries the name of the person who took it.

Who we share it with

We share data with the service providers the platform runs on, and each receives only what its job needs: the hosting providers that run the application and the database, the storage provider that holds an uploaded logo, the messaging providers that deliver an SMS, an email or a push notification, and the measurement providers described below. A provider that handles data on our behalf is bound by a written agreement to handle it only on our instructions and to protect it. The list of providers, and where each one processes data, is available on request. We do not sell personal data and we do not share it for advertising.

Data leaving Nigeria

Some of the providers above process data outside Nigeria. Where that happens we rely on the provider contractual protections and on the transfer conditions in the Nigeria Data Protection Act 2023, and we choose providers that can meet them. A community that needs its records kept in a particular place should tell us, because it is a question about how the platform is hosted rather than about the software.

How long we keep it

Community records are kept while the community is a customer. A community that leaves can ask DecyfoTech to export or close its records; we verify the request with the community and complete it within 90 days, except what a law requires us to keep. A visitor record is kept for the retention window the community sets, which defaults to 365 days and is a setting rather than a promise while the legal position is being settled. A closed account or community has its records deleted within 90 days, except the audit entry described below. An audit row is never edited or deleted, because it is the record that a change happened, and it is kept for the life of the platform. A sign-in code expires within minutes, and a code that has been used or replaced stops working at once. A signed-in session lasts 30 days unless the account signs out or changes its password.

Your rights

Under the Nigeria Data Protection Act 2023 a person can ask for a copy of their data, ask for it to be corrected, ask for it to be deleted, ask for its handling to be restricted, object to a particular handling, ask for it in a portable form, and withdraw a consent they gave. We answer a request within 30 days and usually sooner. A resident should contact their community first, because the community holds those records and is the controller of them; anything the community cannot resolve comes to us, and we will take it up rather than send it back. A resident can delete their own account from the account screen, and anybody can use the public deletion page.

If you are not satisfied

A person who is not satisfied with our answer can complain to the Nigeria Data Protection Commission, the regulator established by the Nigeria Data Protection Act 2023, through ndpc.gov.ng. We would rather settle a matter with you first, and nothing here takes that route away from you. Our route for a data question is the privacy address below, and it reaches the person responsible for data protection at DecyfoTech.

If something goes wrong

If personal data is lost or exposed, we tell the Nigeria Data Protection Commission within 72 hours of becoming aware of it, and we tell the communities affected without waiting: what happened, what data was involved, what we have done, and what the community should tell its residents.

How it is protected

Traffic is encrypted in transit. Passwords and sign-in codes are stored as one-way hashes, never in a form that can be read back. A visitor PIN is derived from the pass and a server key, never stored, so a database dump carries no usable PIN. Every request that changes something is validated on the server and checked against the community and the role it belongs to. Sensitive actions are written to an audit log in the same transaction as the action itself, so the record and the change cannot disagree. Access to production systems is limited to the people who need it.

Cookies, local storage, and measurement

The platform itself uses browser storage for four things: keeping you signed in, remembering the theme you chose, a campaign note that records the source of the link that brought you, and counting visits on the public pages. The sign-in storage is strictly necessary, because without it there is no signed-in session. The visit count sets a first-party cookie that lasts 365 days and records a random visitor identifier, the first source and referring host, an approximate country derived from the network, and the public pages read with a session identifier. It sends no name, address, account identifier, query string or form content, and it is never joined to an account. Where this deployment is configured with a Meta pixel, the public marketing pages load it so we can measure our advertising. Meta receives the public page you visited, your browser and device information, and an approximate location derived from your network address, and it may store its own cookies in your browser as part of that. Neither the pixel nor the count runs inside the signed-in resident, guard or admin screens. The hosting network may also count requests at its edge, which receives the address the request came from and the page, and is not linked to an account.

The messages we send

Every message the platform sends is transactional: a sign-in code, a visitor pass link, an arrival notice, or a message a Community Admin wrote. We do not send marketing to residents, and a message from the platform always names the community it came from.

Changes to this policy

When this policy changes in a way that matters, communities are told before it takes effect, with what changed and why, and the date at the top of this page moves with it. A signed-in person is asked to accept the new version before continuing.

Contact

A question about this policy, a request about your data, or a complaint goes to the contact card at the end of this page. A security issue goes to the security address there.

Where to write

A question about your data, or a request to see, correct, or delete it: info@decyfotech.com

A security issue, which we would rather hear about from you than read about elsewhere: info@decyfotech.com

A notice under these terms, or anything about the agreement itself: info@decyfotech.com