Who can see my visitor log, footage and personal data?
Each community is a separate tenant. Residents see their own flat's records, security personnel see what the gate needs, and Vision footage stays on site.
Who can see my visitor log?
Three groups, and no one else. You and the other residents of your flat see your flat's full entry history. Security personnel see what the gate needs for the shift in front of them. Your community admin and community manager see community-wide records, because running the gate requires it.
Records are scoped to your flat, not to you personally. If your spouse pre-approves a visitor, you see that entry too. A parcel is addressed to the flat, so any resident of the flat can collect it. This is deliberate — it is how a household actually works — but it does mean privacy is scoped to the flat, not to your individual account.
| Role | What they see |
|---|---|
| Resident (owner, tenant, family member) | Their own flat's visitors, deliveries, gate passes, bookings, invoices and complaints |
| Security personnel at the gate | Visitor and vehicle details needed to verify entry now, plus the tower or flat to route to |
| Security manager | Gate activity across the community, incidents, guard shifts |
| Community manager and community admin | Community-wide records across every flat, including finance and complaints |
| AKCS staff | Not part of your community's roles. Ask your committee what your support agreement says about access |
Every role in AKCS is a combination of a person, a space and a role, and it is date-bounded. When a tenant moves out, the membership ends and the access ends with it. An unaccepted invitation to join a community expires after 7 days.
Is my community's data mixed with other communities?
No. Each community is its own tenant, kept separate at the database layer and at the file storage layer. A query made inside one community cannot return another community's flats, residents, visitors or invoices. This is structural, not a filter applied at the screen.
Data is held in data centres in Mumbai and Hyderabad. For builders who require it, an on-premise deployment on the builder's own infrastructure is available.
AKCS holds no third-party security certification — no SOC 2, no ISO 27001. We would rather say that plainly than imply an audit we are not in. If your committee needs a certified vendor, weigh that seriously. If you want to know how a specific control works, ask and we will describe it exactly.
What does the guard at the gate deliberately not see?
Two things are hidden from security personnel on purpose, and they are worth knowing about because most gate systems do not do this.
- The delivery collection code. When a parcel is logged for your flat, AKCS generates a 6-digit collection code, valid for 48 hours. It goes to you, not to the gate. The code is stripped out of the payloads sent to the guard app and the admin app, so nobody at the gate can quote it back and collect on your behalf.
- Your flat number on cab pickups. Turn on Safe Pickup Mode and a pre-approved cab is matched on the vehicle number only. Security personnel see your tower or block, never the flat. Cab pre-approval matches the last 4 characters of the number plate. There is no QR and no OTP on this flow.
There is one thing the guard may see that surprises residents, and we would rather you heard it here.
flag_at_gate — which is on by default — the guard app shows a "dues pending" flag against your flat. Your amount is not shown, but the flag is. Your committee can turn this off. Ask them to, if you would rather it were not visible at the gate.Does AKCS Vision upload my building's CCTV footage to the cloud?
No. AKCS Vision processes video on an on-premise box inside your community. Footage does not leave the site. What reaches the AKCS platform is the detection event — a short record saying what type of alert fired, where and when — not the video.
Vision recognises exactly 10 detection event types: person fall, people count exceeded, crowd anomaly, motion at an unusual time, loitering, intrusion, violence, fire, smoke, and abandoned object. Cameras connect over RTSP.
Being honest about retention: AKCS does not currently hold a retention setting for clips or events in the platform. Footage lives on the recorder in your community, and how long it is kept is decided by whoever controls that recorder — your committee or your facility manager. Ask them what the setting is. Nobody can answer that from the app.
Is face recognition running on me?
Only if your community has switched it on, and it is off by default. Face matching at the gate uses Amazon Rekognition in the ap-south-1 (Mumbai) region, with a match threshold of 0.75 and a 10-minute window so a visitor is checked once per visit, not repeatedly.
| Mode | What happens |
|---|---|
| Off (default) | No face matching. No faces sent anywhere |
| Advisory | A match result is shown to security personnel as information. It does not decide entry |
| Strict | The match result is enforced at the gate |
Separately, the auto-approve rules your flat may have set are deterministic. No language model reads your visitor data to decide who gets in. If the data is incomplete or unclear, the rule engine escalates the decision to you rather than approving it.
Can I get my data out if my community leaves AKCS?
Yes. On exit, your community receives a CSV export of its records plus the original files of everything uploaded — complaint photos, documents, attachments. There are no exit fees.
Related: how to pre-approve a visitor, what security personnel see in the gate app. To ask about on-premise deployment, book a demo.
Still stuck?
Email contact@shinraidynamics.com and a human replies within the same working day.