Legal
How we handle resident, visitor and website data.
What we collect, what we never do, and who it is shared with — covering the platform and our public website, and saying clearly where the two differ.
Privacy Policy
Effective date: October 30, 2026
Maximum.Community is operated by CMJPEJ, LLC. We provide visitor management and security software to residential communities and the security companies that serve them.
Your community — its board, its property manager, or its security provider — decides how the service is used and who sees what. This policy covers both the platform itself and our public website at maximum.community, and says clearly where the two differ.
What we collect
- Your account: name, email, phone number and unit, given either by you or by your community when your account is created.
- Visitors you invite: the name, phone number and vehicle details you enter, and the passes you create for them.
- Gate activity: pass scans and check-ins, with the time, the entrance, and who or what processed them. The guard app on iPhone may attach the phone’s location (the coordinates and how accurate they are) to a scan for the community’s audit trail, if the guard has allowed it. That location is for the record only. It never decides whether someone gets in.
- License plates, at communities that use camera-based entry.
- What you send us: messages to your community office, work orders, and incident reports.
- Support requests you send us from the app, with any photos you attach. Only you and our platform administrators can see those photos, and they have no public link.
- Membership photos, where your community uses membership cards: a photo of your face, taken by a member of staff. Staff see it when your card is scanned, to check the card is yours. It is deleted when you are removed from the community or delete your account.
- Photos: the membership photo above; photos of packages that staff log; and pictures taken at a gate for the community’s records, such as the still pictures a gate tablet saves and the image of a plate at camera-based entry.
- Intercom and phone call records: the time, the door, who answered and whether the gate opened, with the caller’s phone number and any note or summary added to the call. Recordings are covered under Intercom and phone calls below.
- Notification delivery: a push token (the address Apple or Google gives your phone so alerts can reach it), your phone’s model and operating system version, and the app version, so alerts you asked for can reach your phone.
- App install ID: the first time the app runs, it makes a random number for that installation. It is not made from your phone’s hardware, your account or any advertising ID. The app sends it when you sign in, and we keep it with that sign-in. It lets us tell whether sign-ins came from the same installation, and lets our security staff block a lost or stolen phone. We do not use it to send notifications, to advertise, or to follow you between apps. On iPhone it stays on the phone if you delete and reinstall the app. It is not copied to a new phone.
- Sign-in with Google or Apple, if you choose it: we receive an account identifier and email address from that provider to match you to the account your community created. We receive nothing else and never post or share anything back.
What the apps ask your phone for
The apps ask your phone for permission first. You can say no, or switch a permission off later in your phone’s settings. Each one is used only for the reason given here.
- Location, for your mobile key. If your community uses mobile keys and has given you one, you can allow location so the gate or door can open as you arrive. On iPhone, you can choose “Always”, which lets this work while the app is in the background. We use your location only for that. When you open a door this way, your location is also sent to your community’s access-control provider, as described under Who sees your information below. If you do not allow location, unlocking on arrival will not work.
- Location, for guards. The guard app on iPhone asks for location while it is in use, so it can attach it to gate scans for the community’s audit trail, as described under What we collect. A guard who says no can still scan. Nothing is blocked.
- Camera. Only on the screens used by community staff and security guards, and only when they start the action. It is used to scan a visitor’s QR pass or a resident’s membership card, to read the barcode on the back of a visitor’s driver’s license, and to take a resident’s membership photo. From the license barcode the app takes the first and last name and nothing else. The rest of the barcode is thrown away on the phone. It is never saved, logged or sent to us. The name is used for the visitor’s entry, and the entry is marked as ID-checked. Residents’ screens never use the camera.
- Bluetooth. Used only for your mobile key, so your phone can talk to the reader at the door or gate.
- Microphone and camera, on gate intercom calls. The microphone is used only while you are on an intercom call in the app, so the visitor can hear you. The picture you see of the visitor comes from the gate’s camera. Your own camera is never sent.
- Photos. In the apps, photos are taken only through the staff camera use described above, such as a membership photo. The apps do not read your phone’s photo library.
What we do not do
We do not sell or rent personal information. We do not track you across other companies’ apps or websites. There are no ads in the apps or the platform, we do not run advertising networks inside them, we never use resident or visitor information to advertise anything, and nothing we use follows you to other websites. We do count visits to our public website, which is described under Our public website below.
Our public website
This part applies to maximum.community, the pages describing our services.
- We count visits with Clicky, a third-party web-analytics service. When you open a page, your browser sends the visit to Clicky and it records it for us. This is a change from our previous approach, where the counting software ran on a server we own; what Clicky collects and how long it keeps it is set out in Clicky’s own privacy policy, which applies alongside ours.
- A visit records the pages you open and when, the site or search that sent you, links you follow away from the site and files you download from it, your browser, device and screen size, your language, your IP address, and the approximate location — country, and often region and city — worked out from that address. A cookie set by this site lets us tell a returning reader from a new one.
- We use this only to understand how the site is used. We do not sell it and we do not use it to advertise to you. Because Clicky records it for us, it is held by Clicky under their terms as well as ours; we do not add it to the resident, guard or visitor records the rest of this policy describes.
- If you send us an enquiry, we get the name, community, state, email and phone number you typed, and we use them to reply and to follow up about our services. A form submission does not put you on a marketing list — we ask separately for that.
None of this touches any community’s records. Reading these pages does not identify you as a resident of anywhere, and we make no attempt to connect website visits to resident accounts.
If you are in the EU, the EEA or the UK, we ask first. Nothing is loaded and nothing is recorded until you accept, accepting and declining are one click each, and closing the notice without answering is not an answer, so nothing is counted and you will be asked again next time. If you decline, the site behaves exactly as it does for everyone else; nothing on it depends on being counted.
Your choice about being counted
Anyone can change this at any time, wherever they are and whatever they chose before. The choice is stored in this browser, so it applies to the browser you make it in.
You can also clear this site’s stored data in your browser, which erases the choice entirely and makes us ask again, or write to [email protected].
Analytics inside the apps
The mobile resident and guard apps do not count which screens you use. Our web platform at app.maximum.community counts page visits with Clicky, the same third-party service used on this website, and the limit we set ourselves holds: counting, never content. Pages that carry something private in their address — a resident or incident id, or an access token in a pass, guest-list or entry-panel link — are stripped of it before the visit is counted, so a message, an incident report, a plate read, a visitor record or an access credential is never sent to an analytics system.
That is a statement about analytics and not about everything the apps do. They still send technical information to the companies that run parts of the service for us, including hosting, push notification delivery, and crash and error reporting when something goes wrong. Those are covered under Who sees your information below.
Text messages
Where your community has switched texting on, we send texts about visitor passes and your community’s notices from the community’s number. Message frequency varies, and message and data rates may apply. Reply STOP to stop, START to start again, or HELP for help. We do not share mobile information with third parties or affiliates for their marketing or promotional purposes, and we never share text-messaging opt-in data or consent with anyone.
Intercom and phone calls
A visitor at a gate can call a resident from a door station or a gate tablet, and some calls are answered by a guard instead, or by Guardina, our AI guard assistant. These calls run through your community’s phone system. We keep a record of each call: the time, the door, the unit dialed, who answered, whether the gate was opened and how, and the caller’s phone number. A guard who answers can add a wrap-up note. Calls handled by Guardina also carry its summary and any photos from the gate.
Calls can also be recorded, for the community’s security records. Recording at a door station is on only where the community has switched it on for that door, and communities that record post signs at the door station. Calls answered by a remote guard through the community’s guard line may also be recorded. A recording is audio only, so it includes the visitor’s voice as well as the resident’s or the guard’s. We do not record video on any call.
We turn a recorded call into a written transcript and a one-line summary. To do that, we send the audio to a speech-to-text service: OpenRouter, which passes it to Google’s Gemini model. This is done only under zero-retention terms, which means the provider does not keep the audio. If we cannot confirm zero retention, nothing is sent and the call is not transcribed. Transcripts are made by software and can contain mistakes.
Who sees call records depends on who they are for:
- The community’s management (its administrators and property managers) sees call statistics only: when calls happened, how many, and whether the gate was opened. It does not see caller phone numbers, recordings, transcripts, guards’ wrap-up notes, or Guardina’s summaries or photos.
- The security company that has an active contract for the community sees call records in full. Its administrators can play recordings and read transcripts. Its other staff see call lists and caller phone numbers only.
- Guards see the caller’s phone number on a call. They cannot replay recordings.
- Platform administrators at Maximum.Community can access call content when that is needed to operate and support the service.
The community sets how long recordings are kept. When that time is up, the audio and the transcript are deleted together, and the caller’s phone number and the wrap-up notes are cleared from the call record. The record of the call itself stays, so the community’s statistics still count it. If a community has set no limit, recordings are kept until they are deleted. Deletion is paused if a legal hold requires the records to be kept.
A video call from a gate tablet is live, and we do not record the video. If the call is recorded at all, it is the audio only, under the rules above. The tablet may also save a single still picture from its camera at certain moments, such as when a call starts or when a pass or code is accepted or declined, for the community’s security records. These pictures follow the same limit as recordings: they are deleted when the community’s recording limit passes.
Where a community uses Guardina at a gate tablet, Guardina may ask a visitor to hold up their driver’s license. It reads the name and the expiration date from the card and can compare the photo on the card with one picture of the visitor’s face taken at that moment. The result is only a hint for the guard and the resident; it never decides on its own whether someone gets in. The license image and the face picture are used for that check only and are not stored. They are sent through OpenRouter only to zero-retention services, which do not keep them: Google’s Gemini model reads the card, and a Qwen vision model, hosted in the United States by DeepInfra, Parasail or Venice, compares the two photos.
Video from the community’s cameras
At a guard booth, licensed security guards and the community’s administrators can look at the community’s own gate cameras: a near-live picture, and a rewind of 30 seconds, 2 minutes or 10 minutes. This is the community’s own camera system. The video is passed through to the screen and we do not store it. Each rewind is logged: who looked, at which gate, and at which moment.
Who sees your information
- Your community: entry records are visible to its authorized staff and its contracted security provider, according to their role.
- The locked security archive, if you delete your account: the security records that stay, with your name, unit and address, move-in date, household role, email and phone as they were recorded (see Deleting your account below). Only our platform administrators, and the administrators of the security company that currently holds an active contract for your community, can see whose they are; some records are visible to even fewer people. Everyone else sees “Deleted Account”, apart from any text that people typed into a record, which is kept as written. Every look at the archive is logged.
- Companies that run parts of the service for us — hosting, push notifications, email, SMS where a community has switched it on, AI services, where a community uses the features that need them (OpenRouter, which routes our AI requests; Google, whose model transcribes recorded intercom calls and powers the guard-assistant features; and DeepInfra, Parasail and Venice, which host the model Guardina uses to compare a license photo with a visitor’s face), and crash and error reporting. They handle the data only to provide the service.
- Your community’s access-control provider, where the community uses a phone as a key. When you open a door that way, your location is sent to them to confirm you are actually at the door — a check that stops a copied key being used from somewhere else. Your name and email are sent when your key is first issued. The mobile-key credentials themselves are provided by UniKey.
- Anyone we are legally required to give it to, in response to a valid legal request.
Communities and security companies
Your community, and any security company working for it, decides who it gives access to and what it does with the records it can see in the service, such as an entry record or a recording. For records kept for a community, we act on that community’s instructions as its service provider. When a community, its management company, or a security company we do not control uses information for its own purposes, its own policies and the laws that apply to it govern that use, and to the maximum extent permitted by law we are not responsible for it. Questions about that use are best sent to your community office.
Keeping it safe
Data is encrypted in transit. Sign-in credentials are held in the phone’s own secure storage. Access follows your role, sensitive records are access-logged, and our apps check that requests come from a genuine, unmodified app rather than a script pretending to be one.
No method of sending or storing information is completely secure. We use safeguards we believe are reasonable for the information we hold, including those described above, but we cannot guarantee that information will never be accessed, disclosed, changed or lost without authorization, and to the maximum extent permitted by law we are not responsible for that happening despite those safeguards. Keep your password, sign-in codes and phone secure, and if you think your account has been compromised, tell your community office and us at [email protected] promptly.
How long we keep it
Sign-in history, security logs and access-control records are kept for 24 months and then deleted automatically. We chose that period deliberately, and it is the same one we apply to website visit records.
Call recordings and transcripts follow the limit your community sets, as described under Intercom and phone calls above. So do the still pictures saved by gate tablets, and the caller phone numbers and wrap-up notes in call records.
Photos attached to a support request are deleted automatically one year after the request is closed. If it is reopened, the year starts again when it closes. Deleting your account removes them sooner, and a legal hold keeps them until it is released.
Gate and visitor activity is kept as long as your community’s record-keeping needs it. We are extending the same automatic 24-month limit to cover these records, and this page will say so plainly once that is in place rather than describing it in advance. Some communities arrange a different period for their own records; yours can tell you which applies to it. If you ask us to remove specific records sooner, we do that with your community by hand.
Records that stay in the locked security archive after an account is deleted (see Deleting your account below) follow the same limits as everyone else’s records. Deleting an account neither shortens those limits nor extends them. When the last record that refers to a person is gone, their archived name and contact details are deleted too. A legal hold keeps everything it covers until it is released.
Deleting something removes it from the live service. Backups are taken regularly and age out on their own schedule, so a deleted record can persist in backup media for a period after it is gone from the service. We do not restore individual records from a backup once they have been deleted. Website visit records are the exception with a fixed limit: 24 months, then deleted automatically, as described above.
Your choices
Notification preferences are in the app. To see, correct or delete your information, contact your community office or write to [email protected]. Where a deletion request touches community security records, we work with your community, which may be required to keep some of them.
Deleting your account
In the app, use Delete account: on iPhone it is in the Profile tab, and on Android it is at the bottom of the Home screen. This starts a 7-day waiting period. When it ends, your account is erased: your profile and sign-in, your membership photo, your signed-in devices, your door-key credentials and your posts and replies on the community board are removed, and nobody can sign in to it again. The security records stay, in a locked security archive: gate and door records, visitors and guest passes you created, your vehicles and license plates (switched off), call records and recordings, incident reports and the security log, kept with your name, unit and address, move-in date, household role, community, email and phone as they were recorded. Only our platform administrators, and the administrators of the security company that currently holds an active contract for your community, can see whose they are; to everyone else you show as “Deleted Account”, apart from any text that people typed into a record, which is kept as written and can include a name; and every look at the archive is logged. These records follow the same time limits as everyone else’s, as described under How long we keep it, and nothing in the archive can open a gate, a door or a pass, or ring an intercom. Records that the law requires us to keep are kept as well, and so are the record that you accepted our terms (the version and the time, not your network address or device) and the delivery logs of emails and texts sent to you. You are signed out straight away, and we email you a confirmation with a link to cancel. During the 7 days you can cancel from the link in that email, or from the cancel button the app shows.
Without the app, email [email protected] from the email address on your account. A platform administrator then files the same 7-day deletion, and you get the same confirmation email with a cancel link.
If your community had already turned your account off (for example after a move-out), cancelling the deletion stops the erasure but does not turn your account back on. To get access, contact your community office or our support.
The page how to delete your account has the steps, and says what is deleted, what is kept in the locked security archive and who can see it.
Children
The service is not aimed at children under 13. Accounts are issued only by communities, to their residents and staff.
Under our Terms of Service, account holders must be at least 18. We do not knowingly collect personal information from children under 13, except information that a community or an adult resident enters for household, guest or membership purposes (for example, a household member’s or guest’s name, or a membership photo taken by staff) and pictures or recordings in which a child happens to appear at a gate or on a call. If you believe a child under 13 has given us personal information some other way, write to [email protected] and we will work with the community to delete it.
Your consent
By using the service, you consent to the collection, use and sharing of information described in this policy, including, where your community uses them, the recording of calls, the still pictures gate tablets save, license-plate capture, the transcription of recorded calls, and Guardina’s license reading and face comparison when you choose to hold up your license. This is in addition to any notice your community gives, such as the signs at a door station that records. If you do not agree, do not use the service or those features.
Changes
If we change this policy materially, we will update this page and the date at the top.
Changes take effect when they are posted. If you keep using the service after a change takes effect, you accept the updated policy, to the maximum extent permitted by law. Where the law requires more notice of a change, or your consent to it, we will give that notice or ask for that consent.
What this policy is, and is not
To the maximum extent permitted by law, this policy describes our practices; it does not create contractual rights or obligations. Our Terms of Service — including their limitation of liability and their dispute-resolution section, which requires binding individual arbitration and waives class actions and jury trials — apply to any dispute about this policy or about your information, to the maximum extent permitted by law.
Contact
CMJPEJ, LLC — [email protected]