Legal

This page displays legal, agreements, disclosures, policies and added documentation.

Horizon Eye Privacy Policy & State Privacy Supplement

Effective 2026/09/17

Controller / business: HORIZON EYE INC, doing business as Horizon Eye Security (“Horizon Eye”).

Privacy contact: privacypolicyandagreements@horizoneyesecurity.com | Support: support@horizoneyesecurity.com

1. Scope and notice

This Privacy Policy explains how Horizon Eye collects, uses, discloses, retains, and protects personal information through the Horizon Eye resident application, management portals, websites, customer support, integrations, and related services. It does not govern a property-management company’s independent privacy practices, except where Horizon Eye processes information on that company’s documented instructions as a service provider or processor.

Horizon Eye is designed for authorized community operations and safety information. It is not designed to collect information unrelated to the Services. We ask users and management companies not to submit Social Security numbers, payment-card numbers, government IDs, biometric templates, health records, credentials, or other highly sensitive information unless Horizon Eye has expressly enabled a lawful, secured, and documented feature for that information.

2. Information we collect - Format Below

*
*
CATEGORY

Examples

Sources

Primary Purposes

Account and profile information

Name, email, phone, account ID, community, unit/lease-linked status, date of birth were provided and permitted, role, login status.

You, property manager, authorized roster/PMS import, account provider.

Account creation, authentication, community eligibility, support, fraud prevention, and administration.

Community and management information

Community identifiers, property details, roster records, lease start/end, manager/operator roles, access-code records, approvals, and audit events.

Management company, authorized administrator, PMS/API/CSV import.

Community configuration, resident access, operational governance, reporting, and audit.

Emergency-contact information

Contact name, relationship, and telephone number entered by a resident where enabled.

Resident.

Resident-selected emergency-contact feature and service delivery.

Vehicle, item, and related profile information

Vehicle make, model, color, plate or token where enabled, garage information, and personal-inventory records.

Resident or authorized management source.

Safety-related matching, inventory/garage features, verification, reporting, and exports requested by the user.

Incident and community-safety content

Incident type, narrative, images, time/date, approximate or precise location, vehicle/item descriptors, status, moderation results, resolution evidence, and audit history.

Residents, managers, administrators, or authorized data sources.

Report submission, moderation, authorized display, safety analysis, resolution workflows, audit, and service security.

Location and device information

Device location when permission is granted, location precision, IP-derived coarse location, device/app version, operating system, language, push token, diagnostic logs, and interaction data.

Device, application, network, authorized SDKs.

Location-based features, map display, security, notification delivery, troubleshooting, quality, and aggregation.

Communications and requests

Support tickets, account-change requests, deletion requests, feedback, correspondence, and call/email metadata.

You or your authorized representative.

Responding, service administration, audit, security, and legal compliance.

Analytics and inferred information

Aggregated usage, service performance, fraud/abuse signals, community safety scores, risk trends, and non-decisive operational recommendations.

Our systems and lawful source data.

Service reliability, analytics, feature improvement, abuse prevention, and community operations.

3. How we use information

We use personal information to provide and secure the Services; authenticate and administer accounts; associate authorized residents with communities; process reports and community operations; deliver requested notifications; support users; maintain records; detect security, fraud, content, and manipulation risks; improve reliability; comply with law; establish or defend legal claims; and produce de-identified or aggregated analytics. We do not use safety scores, incident patterns, or automated analytics as the sole basis for a decision that produces legal or similarly significant effects about an individual.

Where required, we obtain consent or provide just-in-time notice before accessing device capabilities such as precise location, camera/photos, motion data, or notifications. You may decline or revoke a device permission through device settings, although some features may not work without it. We do not intentionally use precise location for targeted advertising.

4. How and with whom we disclose information

We disclose information only as needed for the purposes described here, including to authorized users within your community and role permissions; the applicable management company; service providers that host, secure, analyze, communicate, or support the Services; professional advisers and insurers; government, law-enforcement, or other parties when required by law or when a valid legal process applies; and counterparties in a corporate transaction. We may disclose de-identified, aggregated information that does not reasonably identify you.

Horizon Eye does not sell personal information and does not share personal information for cross-context behavioral advertising as those terms are defined by the CCPA, based on the current confirmed product design. This statement must be revised before release if Horizon Eye introduces advertising, ad-tech SDKs, cross-context behavioral advertising, or another practice that changes the legal analysis. We do not disclose resident incident content publicly by default; authorized visibility depends on the feature, account role, community settings, moderation, and applicable law.

5. AI/ML and analytics processing

Horizon Eye may use rule-based systems, statistical analysis, or AI-assisted tools to help identify prohibited content, deduplicate reports, surface patterns, calculate safety or operational metrics, classify incident attributes, or support human review. These outputs can be incomplete, incorrect, biased, or unsuitable for high-stakes decisions. Human review is required for enforcement, resident access restrictions beyond automated security safeguards, community-management actions, and material report-resolution decisions. We do not authorize users or management companies to use AI-derived outputs to make housing, employment, insurance, credit, law-enforcement, or discriminatory decisions.

We may use service providers to process information for an approved AI/analytics function under contract, access restrictions, and documented processing instructions. We do not permit providers to use Horizon Eye customer content to train a general model unless we expressly disclose and obtain any required authorization. See the AI Governance & Transparency Policy for more detail.

6. Retention, deletion, and account closure

We retain personal information only for as long as reasonably necessary for the purposes described in this policy, the applicable customer agreement, a user request, service security, dispute resolution, legal compliance, or a documented legal hold. The current target retention schedule appears in the Data Retention, Deletion & Community-Code Policy and must be technically implemented before the policy becomes effective.

Users may initiate account deletion in the application and through the public deletion-request page at [INSERT URL]. We may require reasonable identity verification and may retain limited information where law permits or requires it, including security logs, fraud-abuse records, tax/transaction records, audit evidence, or information subject to a legal hold. If deletion takes time, we will explain the expected period and confirm completion. A management company’s lease administration does not eliminate an individual’s right to initiate a deletion request where applicable law or app-store rules require it.

7. Security and incident handling

We use administrative, technical, and organizational measures designed to protect information, including access controls, least-privilege permissions, authentication, logging, input validation, encryption in transit, vendor controls, and incident-response processes. No system is completely secure. If we determine that a breach requires notice under applicable law or contract, we will investigate, contain, and provide legally required notifications. The Security Incident Response, SLA & Continuity Terms describe customer-facing operational roles and must be aligned with the production incident plan.

8. Your privacy choices and rights

Depending on where you live and applicable law, you may have rights to request access, correction, deletion, portability, restriction, appeal, or information about our processing. You may also have a right to opt out of certain targeted advertising, sale/sharing, profiling, or sensitive information uses. Submit a request at [INSERT PRIVACY REQUEST URL] or [INSERT PRIVACY EMAIL]. We may verify your identity and authority, request information necessary to process the request, and deny or limit a request were permitted by law. We will not discriminate against you for exercising applicable privacy rights.

9. California notice

For California residents, the categories in Section 2 describe the categories of personal information Horizon Eye may collect. They may include identifiers, customer records, protected classification information where voluntarily provided and lawful, commercial/service information, internet/network activity, approximate or precise geolocation, audio/visual information where submitted, professional information for administrators, and inferences. Precise geolocation, account credentials, and any other information defined by law as sensitive personal information are treated as sensitive information. We use sensitive information only as reasonably necessary to provide requested services, ensure security/integrity, comply with legal obligations, and for other permitted purposes.

California residents may request to know/access, correct, delete, and receive information about disclosures; may limit certain sensitive information uses; and may opt out of sale/sharing if Horizon Eye ever engages in those practices. Horizon Eye’s current statement is that it does not sell or share personal information for cross-context behavioral advertising. We honor applicable Global Privacy Control signals if our web properties conduct data practices to which such signals apply. Authorized agents may submit requests subject to reasonable verification. See the California Department of Justice’s CCPA resource for a current overview of covered rights and definitions. 1

10. Children, international data, and changes

The Services are not directed to children under 13, and Horizon Eye does not knowingly collect personal information from children under 13 without legally required parental consent. Management companies must not enroll a minor or provide minor information through the Services unless the feature, customer agreement, and law expressly permit it and the required authorization has been obtained. If we learn that we collected covered children’s information unlawfully, we will take appropriate deletion or remediation action.

Horizon Eye may process information in the United States and other locations where we or our providers operate. When international transfer rules apply, we will use a recognized transfer mechanism and supplementary safeguards as appropriate. If Horizon Eye participates in a recognized cross-border framework, it will say so clearly and only after becoming certified or otherwise eligible.

We may update this policy to reflect product, legal, or operational changes. We will post the revised version, change the effective date, and provide additional notice or consent where legally required. Material changes will not be applied retroactively in a way prohibited by law.

11. Biometric and precise-location supplemental notice

Horizon Eye does not intentionally collect biometric identifiers or biometric templates for identification, such as face geometry, fingerprints, voiceprints, iris scans, or gait templates, unless it separately provides the notices, consent, retention policy, security controls, and contractual terms required by applicable law. A photograph is not treated by Horizon Eye as biometric data unless it is processed to identify a person. No feature may activate biometric identification without a counsel-reviewed supplement and a documented release gate.

Precise location may be collected only when a user enables a feature that needs it and grants device permission. Horizon Eye uses location to provide requested map, incident, safety, or motion-related features; it does not promise continuous monitoring, emergency dispatch, or location accuracy. Location access can be disabled at device level. Product owners must update this notice if background location, continuous tracking, or new location sharing is enabled.

Horizon Eye End User License Agreement

Effective 2026/09/17

Controller / business: HORIZON EYE INC, doing business as Horizon Eye Security (“Horizon Eye”).

Privacy contact: privacypolicyandagreements@horizoneyesecurity.com | Support: support@horizoneyesecurity.com

1. Acceptance and eligibility

By downloading, installing, accessing, or using the Horizon Eye application, you agree to this EULA and the Horizon Eye Terms of Service, Privacy Policy, and Acceptable Use, Community Safety & Abuse Prevention Policy. You represent that you are legally able to enter into these terms and, if you use Horizon Eye in connection with a residential community, that your access is authorized by the applicable community or property-management company. If you do not agree, do not install or use the application.

2. Limited license

Subject to your continued compliance, Horizon Eye grants you a limited, revocable, non-exclusive, non-transferable, non-sublicensable license to install and use one copy of the application on devices you own or control solely for your personal, lawful use within authorized Horizon Eye services. The application is licensed, not sold. Horizon Eye and its licensors retain all rights, title, and interest not expressly granted in this EULA, including all software, designs, interfaces, documentation, analytics methods, trademarks, and intellectual-property rights.

3. Your device, account, and responsibilities

You are responsible for obtaining compatible devices, connectivity, permissions, and backups; keeping your device and account credentials secure; promptly reporting suspected unauthorized access; and complying with applicable law, community rules, and these agreements. You must use accurate account information, protect temporary passwords or access codes, and notify Horizon Eye or your property manager if your community residency or access authorization changes.

You are responsible for all activity conducted through your authenticated account unless caused by Horizon Eye’s breach of its security obligations. You may not share credentials, allow another person to use your account, bypass access controls, reverse engineer the application, interfere with the service, use automated extraction tools without written permission, or use the application for commercial, unlawful, retaliatory, discriminatory, or harmful purposes.

4. Safety and emergency limitation

Horizon Eye is a community-information and operational-support tool. It is not an alarm-monitoring service, emergency-response service, security guard service, insurance product, crime-prevention guarantee, legal advice service, or substitute for responsible personal safety practices. Safety scores, maps, notifications, predictions, recommendations, incident information, and analytics may be delayed, incomplete, inaccurate, unavailable, or based on user-submitted or third-party information. You remain responsible for your own safety decisions.

If there is an emergency, imminent threat, fire, medical need, crime in progress, or other urgent danger, call 911 or the applicable local emergency number first. Do not rely on Horizon Eye to contact emergency responders, dispatch assistance, verify an incident, preserve evidence, or provide a real-time warning. Do not use the application while driving or in a manner that distracts you from surroundings or lawful duties.

5. Content and reporting integrity

You retain ownership of content you lawfully submit, including incident details, photographs, and descriptions, subject to the license below. You grant Horizon Eye a worldwide, non-exclusive, royalty-free license to host, reproduce, format, secure, display to authorized audiences, moderate, analyze, de-identify, aggregate, and otherwise process submitted content solely to operate, protect, improve, and comply with legal obligations related to the service. This license ends when content is deleted, except to the extent a copy must be retained for legal compliance, dispute defense, audit, security, or backup-cycle purposes.

You must submit only information you reasonably believe is accurate and necessary. You may not knowingly submit false, misleading, defamatory, discriminatory, threatening, sexually explicit, exploitative, private, or unlawful content. You may not include a person’s full name, unit number, contact details, precise personal whereabouts, financial data, credentials, medical information, or other identifying information unless you have a lawful basis and Horizon Eye expressly permits it for the intended feature. Do not upload malware, executable code, secrets, or content designed to compromise the service.

6. Prohibited conduct and enforcement

The prohibited conduct in the Acceptable Use Policy is incorporated into this EULA. Horizon Eye may use automated screening, manual review, access controls, rate limits, content removal, account restrictions, suspension, termination, reporting to authorities where legally appropriate, and evidence preservation to enforce the policy and protect people, property, systems, and records. We may remove content or limit access without advance notice where we reasonably believe urgent action is necessary.

7. Updates and third-party platforms

Horizon Eye may update, modify, suspend, or discontinue functions, content, or compatibility. Some updates may be required to continue using the application. Apple, Google, mobile carriers, device manufacturers, mapping providers, notification services, and other third parties may impose separate terms. Apple and Google are not parties to this EULA and have no obligation to provide maintenance or support, except as their terms require. To the maximum extent permitted by law, third-party providers are third-party beneficiaries of the applicable platform provisions.

8. Disclaimers and limitation of liability

THE APPLICATION AND RELATED SERVICES ARE PROVIDED “AS IS” AND “AS AVAILABLE.” TO THE MAXIMUM EXTENT PERMITTED BY LAW, HORIZON EYE DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE, INCLUDING WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, ACCURACY, AVAILABILITY, SECURITY, OR THAT THE SERVICE WILL PREVENT OR DETECT HARM, CRIME, LOSS, OR PROPERTY DAMAGE.

TO THE MAXIMUM EXTENT PERMITTED BY LAW, HORIZON EYE AND ITS AFFILIATES, LICENSORS, PROPERTY-MANAGEMENT CUSTOMERS, DIRECTORS, OFFICERS, EMPLOYEES, CONTRACTORS, AND AGENTS WILL NOT BE LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES, OR FOR LOSS OF DATA, PROFITS, GOODWILL, USE, PERSONAL SAFETY, PROPERTY, OR BUSINESS OPPORTUNITY, ARISING FROM OR RELATED TO THE SERVICE. HORIZON EYE’S AGGREGATE LIABILITY ARISING FROM YOUR USE OF THE SERVICE WILL NOT EXCEED THE GREATER OF US $100 OR THE AMOUNT YOU PAID HORIZON EYE FOR THE SERVICE IN THE 12 MONTHS BEFORE THE EVENT GIVING RISE TO LIABILITY. These limits do not exclude liability that cannot lawfully be excluded.

9. Indemnification

To the maximum extent permitted by law, you will defend, indemnify, and hold harmless Horizon Eye and the parties listed above from claims, losses, damages, liabilities, costs, and reasonable attorneys’ fees arising from your content, use of the service, violation of these terms, violation of law or another person’s rights, or misuse of an access code, device, or credential under your control.

10. Suspension, termination, and survivability

This license ends automatically if you violate this EULA, lose authorization to access an affiliated community, request account deletion, or if Horizon Eye terminates the service or your account under the Terms. Upon termination, you must stop using and delete local copies of the application, except that platform-managed copies or legally required records may persist. Sections concerning ownership, content license, disclaimers, limitations, indemnification, dispute resolution, and general provisions survive termination.

11. Governing law, disputes, and general terms

This EULA is governed by the law selected in the Terms of Service. Any required consumer-rights protection or non-waivable statutory right remains unaffected. If counsel approves a binding arbitration and class-action waiver, it must appear in the Terms and satisfy applicable notice, opt-out, and enforceability requirements. If no enforceable arbitration agreement applies, courts located in the selected venue will have exclusive jurisdiction, subject to applicable law.

If any provision is unenforceable, it will be enforced to the maximum lawful extent and the remaining provisions remain in effect. Horizon Eye may amend this EULA prospectively by posting an updated version and providing notice when legally required; continued use after an effective amendment constitutes acceptance where permitted. You may not assign this EULA without our written approval; Horizon Eye may assign it in connection with a merger, acquisition, financing, corporate reorganization, or asset sale.

Horizon Eye Terms of Service

Effective 2026/09/17

Controller / business: HORIZON EYE INC, doing business as Horizon Eye Security (“Horizon Eye”).

Privacy contact: privacypolicyandagreements@horizoneyesecurity.com | Support: support@horizoneyesecurity.com

1. Agreement and service role

By creating an account, accessing the Services, accepting an invitation or community code, or clicking acceptance, you enter into these Terms with Horizon Eye. The Services provide tools for authorized residents, property-management personnel, and Horizon Eye operators to document community information, manage access, review reported safety concerns, deliver configured notifications, and evaluate operational analytics. The Services do not create a duty to protect any person, property, or community and do not guarantee safety, prevention, detection, emergency response, reporting accuracy, property value, insurance outcome, or security outcome.

An affiliated management company may control community membership, lease-linked eligibility, and certain resident record corrections. Its authority does not permit it to make unlawful, discriminatory, retaliatory, or privacy-invasive use of the Services. Horizon Eye may restrict management access or override a management request where necessary to comply with law, protect platform integrity, meet a valid legal obligation, or prevent material harm.

2. Accounts, access, and community authorization

You must provide and maintain accurate information, preserve credential confidentiality, and use only an account assigned to you. Horizon Eye may require identity, email, device, or residency verification; temporary-password replacement; multi-factor authentication; or reauthentication for sensitive actions. Community codes, resident roster access, and manager invitations are personal, limited, revocable access methods—not transferable property rights.

You may access a community only while authorized by Horizon Eye and, where applicable, the management company. The Services may limit, deactivate, pause, or end access when a lease ends, a community code is disabled, an access record is invalidated, an administrator removes access, a security issue is detected, or you breach the Terms. Horizon Eye will provide notice where reasonably practical and legally required but may act immediately for safety, security, fraud, or abuse prevention.

3. Resident and user responsibilities

You agree to use reasonable judgment, follow posted safety instructions and applicable law, maintain your own emergency plan, and refrain from relying on the Services in an emergency. You are responsible for reviewing notifications and information independently, correcting inaccuracies you identify, and obtaining appropriate permissions before uploading content about property, vehicles, or other persons.

Do not use reports, scores, maps, or analytics to harass, discriminate against, retaliate against, evict, deny housing, make employment or insurance decisions, accuse a person of a crime, or take vigilante action. Only qualified and authorized decision makers may take actions based on independently verified facts and applicable law. Horizon Eye reports and analytics are informational aids—not proof, legal findings, or a substitute for professional security, law-enforcement, housing, insurance, medical, or legal judgment.

4. User content, moderation, and reporting integrity

You are responsible for submitted content and must comply with the Acceptable Use, Community Safety & Abuse Prevention Policy. Horizon Eye may screen, filter, delay, redact, remove, preserve, restrict, review, or disclose content as allowed by law and these Terms. Automated tools may identify prohibited material, personally identifying information, malicious files, repetitive reports, fraud patterns, or manipulation attempts; automation may make errors and does not replace the user’s responsibility for accurate content.

You may report content or account behavior you reasonably believe violates our policies through the in-app reporting function or by contacting

support@horizoneyesecurity.com. Horizon Eye will review reports using risk-based triage. We may restrict a user’s ability to submit, view, or interact with content to prevent abuse. We do not guarantee any particular outcome, response time, or removal decision, except where applicable law requires one.

5. Emergency-services disclaimer

THE SERVICES DO NOT CONTACT 911, DISPATCH POLICE, FIRE, EMS, OR SECURITY PERSONNEL, OR GUARANTEE THAT A PROPERTY MANAGER WILL ACT. IF YOU BELIEVE THERE IS AN EMERGENCY OR IMMEDIATE RISK OF HARM, CALL 911 OR THE APPLICABLE EMERGENCY NUMBER AND FOLLOW OFFICIAL INSTRUCTIONS. Do not wait for an alert, map update, score adjustment, moderator response, or manager review. Horizon Eye may provide guidance or resources, but it does not assume emergency-response duties.

6. Fees, third-party services, and communications

Residents may receive access through a management company, a community plan, or another authorized arrangement. Any paid terms, renewals, taxes, refunds, and billing conditions are stated in the applicable order form, store purchase flow, or commercial agreement. You authorize Horizon Eye to send service, security, account, policy, and transactional notices through the application, email, or other permitted channels. Marketing communications remain subject to applicable consent and opt-out requirements.

Third-party services, including app stores, mapping/location services, cloud services, push-notification services, and property-management integrations, may experience outages or apply separate terms. Horizon Eye is not responsible for their availability or acts, except to the extent caused by Horizon Eye’s breach of a non-waivable legal obligation.

7. Intellectual property and feedback

Horizon Eye owns the Services and all related intellectual property. Subject to your rights in your content, you grant Horizon Eye the limited content-processing license described in the EULA. If you provide suggestions, feedback, feature requests, or ideas, you grant Horizon Eye a perpetual, irrevocable, worldwide, royalty-free right to use them without restriction or compensation, provided we do not identify you publicly without permission.

8. Disclaimer; limitation of liability; release

THE SERVICES ARE PROVIDED “AS IS” AND “AS AVAILABLE.” TO THE MAXIMUM EXTENT PERMITTED BY LAW, HORIZON EYE DISCLAIMS ALL WARRANTIES, INCLUDING ANY WARRANTY THAT THE SERVICES WILL BE ERROR-FREE, UNINTERRUPTED, SECURE, ACCURATE, CURRENT, COMPLETE, OR EFFECTIVE IN PREVENTING, DETECTING, OR RESPONDING TO HARM.

TO THE MAXIMUM EXTENT PERMITTED BY LAW, HORIZON EYE AND ITS AFFILIATES, LICENSORS, MANAGEMENT-COMPANY CUSTOMERS, PERSONNEL, AND AGENTS ARE NOT LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES, OR FOR LOST DATA, PROFITS, BUSINESS, USE, GOODWILL, PERSONAL SAFETY, PROPERTY, OR OPPORTUNITY. HORIZON EYE’S TOTAL LIABILITY FOR CLAIMS ARISING FROM THE SERVICES WILL NOT EXCEED THE GREATER OF US $100 OR THE AMOUNT YOU PAID HORIZON EYE FOR THE SERVICES IN THE 12 MONTHS BEFORE THE CLAIM AROSE. Nothing limits liability that cannot lawfully be limited.

To the maximum extent permitted by law, you release Horizon Eye from claims arising from your interactions with another user, management company, community, or third party; from user-submitted content; or from your independent decisions based on the Services, except to the extent directly caused by Horizon Eye’s willful misconduct or liability that cannot legally be released.

9. Indemnification

You will defend, indemnify, and hold harmless Horizon Eye and its affiliates, licensors, management-company customers, personnel, and agents from claims, losses, liabilities, damages, penalties, costs, and reasonable attorneys’ fees arising from your content, use of the Services, breach of these Terms, violation of law, or infringement of another person’s rights.

10. Suspension and termination

Horizon Eye may suspend or terminate any account, community connection, access code, report, integration, or Service feature where we reasonably determine that an actual or suspected violation, security issue, unlawful conduct, manipulation, excessive risk, nonpayment, inaccurate source data, or legal requirement warrants action. We may preserve records needed for security, audit, dispute, legal-hold, or compliance purposes. We will not be liable for reasonable protective action taken under this section.

You may stop using the Services at any time. If the application provides account deletion, you may initiate deletion there and through the website deletion-request page. Deactivation or lease termination is not a substitute for an available account-deletion request. Deletion and retention are governed by the Privacy Policy and Data Retention, Deletion & Community-Code Policy.

11. Disputes, arbitration, and governing law

Counsel must choose and confirm this section before publication. Except where prohibited by law or an executed commercial agreement provides otherwise, these Terms are governed by the laws of the State of Georgia, without regard to conflict-of-laws principles. Before bringing a claim, the parties will provide written notice and attempt to resolve the dispute informally for 30 days.

Optional arbitration clause — include only after counsel review: If a dispute is not resolved informally, either party may elect final and binding individual arbitration administered by [ADMINISTRATOR] under its applicable rules. The arbitration will occur in [COUNTY, GEORGIA] or remotely if permitted. The parties waive jury trial and class, collective, representative, and private-attorney-general proceedings to the maximum extent permitted by law. Either party may bring an eligible individual claim in small-claims court. You may opt out of arbitration by sending a written notice within 30 days of first acceptance to [LEGAL NOTICE ADDRESS].

If the arbitration clause is not adopted or is unenforceable, exclusive venue lies in the state or federal courts located in [COUNTY, GEORGIA], subject to mandatory consumer-protection venue rules. Nothing prevents either party from seeking injunctive or equitable relief for intellectual-property, security, confidentiality, fraud, or abuse matters.

12. General

These Terms, the EULA, Privacy Policy, Acceptable Use Policy, and any applicable commercial agreement form the entire agreement for the Services. If a provision is invalid, it will be modified to the minimum extent necessary and the rest remains effective. Horizon Eye may modify the Terms prospectively by posting an update and giving notice when required; material changes apply on the stated effective date. You may not assign these Terms without written consent. Horizon Eye may assign them in connection with a corporate transaction. Notices to Horizon Eye must be sent to [INSERT LEGAL NOTICE ADDRESS] with a copy to support@horizoneyesecurity.com.

Horizon Eye Acceptable Use, Community Safety & Abuse Prevention Policy

Effective 2026/09/17

Controller / business: HORIZON EYE INC, doing business as Horizon Eye Security (“Horizon Eye”).

Privacy contact: privacypolicyandagreements@horizoneyesecurity.com | Support: support@horizoneyesecurity.com

Applies to: Residents, occupants, guests, property-management companies, staff, administrators, API/integration users, and any person accessing Horizon Eye Services.

1. Purpose and baseline rule

Horizon Eye is intended to support lawful, privacy-conscious community information, safety awareness, authorized access administration, and human-reviewed operational coordination. You must use the Services lawfully, accurately, proportionately, and with respect for the rights, safety, privacy, and dignity of other people. Do not use Horizon Eye to create fear, target individuals, facilitate harm, evade law enforcement, manipulate business outcomes, or make unlawful housing or surveillance decisions.

2. Content, safety, and violence restrictions

You may not submit, request, share, use, or facilitate content or conduct that: threatens, glorifies, promotes, plans, or coordinates violence; enables criminal activity or evasion; targets a person for harassment, bullying, discrimination, intimidation, retaliation, or property damage; contains child sexual abuse material, non-consensual intimate imagery, sexual exploitation, explicit sexual material, or pornography; or encourages self-harm, dangerous conduct, weapon misuse, or illegal drug activity.

Horizon Eye may immediately restrict access, preserve evidence, remove content, notify affected users when appropriate, and report credible threats or legally reportable material to law enforcement, the National Center for Missing & Exploited Children where required, or another competent authority. Nothing in this policy requires Horizon Eye to monitor every submission or guarantees immediate detection.

3. Stalking, doxxing, and unlawful surveillance

You may not use Horizon Eye to stalk, track, monitor, profile, intimidate, expose, or surveil an identifiable person without a lawful basis. You may not post a person’s full name, apartment/unit number, phone, email, address, precise real-time location, face/identity details, vehicle plate, family details, employment information, or other identifying information unless the feature expressly allows it, you have a lawful basis, and disclosure is necessary and proportionate.

Management companies and operators may not use the Services to conduct unlawful surveillance, record or analyze private spaces, monitor residents beyond authorized property operations, identify individuals from images using biometric methods, or circumvent consent, notice, labor, tenant, wiretap, privacy, or housing laws. Management users must not activate, request, or upload surveillance data without documented authority, required notices and consents, and a legitimate operational purpose.

4. Reporting integrity and evidence integrity

Report only facts you reasonably believe to be true. Clearly distinguish observed facts from inferences. Do not fabricate, exaggerate, suppress, backdate, duplicate, or coordinate reports to influence a safety score, target a person, retaliate, affect lease/community status, manipulate property value, obtain insurance leverage, create a false police record, or gain an unfair commercial advantage.

Do not alter, crop misleadingly, mislabel, forge, stage, destroy, or improperly disclose photos, screenshots, location data, inventory information, vehicles, records, or other evidence. Do not claim a vehicle, item, or property connection unless the service’s verification workflow confirms a legitimate pre-existing relationship. Managers must retain an objective audit trail for material moderation, removal, resolution, or access decisions and must not pressure residents or staff to submit, remove, or change reports for business purposes.

5. Security, technical, and credential misuse

You may not upload malware, malicious code, executables, credential-harvesting content, deceptive files, or content designed to disrupt or exploit the Services. You may not probe, scan, attack, reverse engineer, scrape, bypass rate limits, defeat authentication, access another person’s account, inject code or commands, impersonate a user, or use bots except through a Horizon Eye-approved API. You must promptly report suspected account compromise, data exposure, or vulnerability through the published security channel.

6. Management abuse and data manipulation

Management companies and administrators may not manipulate community, resident, incident, safety-score, analytic, integration, notification, or audit information for deceptive marketing, property-value manipulation, insurance negotiation, discrimination, retaliation, tenant screening, lease enforcement without lawful process, or any improper business purpose. They may not conceal material known security incidents, knowingly ingest inaccurate resident data, override audit controls, grant access beyond a person’s role, or use Horizon Eye data for unrelated advertising or resale.

Horizon Eye may require corrections, suspend a record, restrict a workflow, independently preserve evidence, disclose audit information to an affected customer or regulator where permitted, or sever a management connection immediately when it reasonably believes management abuse, unlawful surveillance, evidence tampering, security compromise, or material data manipulation has occurred.

7. Enforcement, appeal, and cooperation

Horizon Eye may apply warnings, temporary feature limits, report removal, visibility reduction, access-code disablement, account suspension, administrator termination, community/integration severance, audit, and permanent termination. We may take immediate action where delay creates a safety, security, privacy, legal, or platform-integrity risk. We will consider good-faith reports and may provide a reasonable appeal path for non-emergency decisions, but we are not required to restore access or content where doing so would create risk or violate law.

Users and management companies must cooperate with reasonable, lawful Horizon Eye investigation requests, including preserving relevant records and credentials. Cooperation does not require disclosure of privileged material, information prohibited by law, or data beyond the party’s authority. Horizon Eye will handle investigation information under its Privacy Policy and applicable agreements.

8. Reporting a violation

Use the in-app reporting mechanism for content or account concerns. For urgent safety threats, call 911 or the applicable emergency number. For technical vulnerabilities, use the Vulnerability Disclosure Policy. For privacy matters, use [INSERT PRIVACY REQUEST URL] or [INSERT PRIVACY EMAIL]. Do not include sensitive personal information in routine support requests unless essential and requested through a secure channel.

Horizon Eye Data Retention, Deletion & Community-Code Authorization Policy

Effective 2026/09/17

Controller / business: HORIZON EYE INC, doing business as Horizon Eye Security (“Horizon Eye”).

Effective date: [INSERT DATE] | Review cadence: At least annually and before each material product, vendor, or legal change.

1. Policy principles

Horizon Eye retains information only for a documented purpose, applies access controls during the retention period, and deletes or de-identifies information when the purpose and lawful retention basis end. We use data minimization, role-based access, scoped exports, audit records, and legal holds to protect residents, management companies, and platform integrity. No record may be retained indefinitely merely because it might be useful.

This policy covers Horizon Eye-controlled data, including information in application databases, portals, support systems, audit logs, storage, exports, backups, integrations, and security records. It does not supersede a valid legal hold, applicable law, a signed customer agreement, a documented security investigation, or a data subject’s rights where a shorter deletion period is required.

2. Target Schedule - format below

Record Category

Target Retention Period

Deletion or Review Action

Notes

Active account and profile data

While account is active

Delete/anonymize on verified deletion request or end of authorized access, subject to exceptions.

Minimal fields only; user may request correction where applicable.

Emergency contacts

While feature is enabled and account is active

Delete on feature removal, account deletion, or verified request unless retained for a documented incident.

Do not use for marketing or unrelated operations.

Community membership, lease eligibility, and community codes

Active authorization period plus 90 days

Disable promptly at termination; purge or de-identify after post-termination reconciliation.

Preserve only what is needed for dispute/audit/legal purposes.

Incident reports and approved resolution records

24 months after closure or last material activity

Review; delete, aggregate, or de-identify unless active/legal retention basis exists.

Counsel must validate against state claims, premises-liability, and customer requirements.

Moderation, abuse, and security-enforcement records

36 months after final action

Delete or de-identify unless recurring abuse, legal hold, or law requires longer.

Strict access; never use for marketing.

Audit logs for privileged management/global actions

36 months

Securely purge after period unless needed for an investigation, contract, or law.

Preserve immutable event metadata; avoid unnecessary content copies.

Routine application, performance, and security logs

90 days online; 12 months archived where justified

Rotate and purge automatically.

Retain fewer fields; do not retain full request bodies or secrets.

Push tokens and notification-delivery logs

Token while active; delivery events 90 days

Delete stale token promptly; purge events on rotation or account deletion.

Respect operating-system permissions.

PMS/API synchronization and import records

12 months after sync/import, unless agreement requires less

Delete staged files after validation; retain an auditable manifest where appropriate.

Securely delete raw roster files after successful import.

Support requests and communications

24 months after closure

Delete or de-identify unless linked to security, legal, billing, or dispute matter.

Restrict visibility to support need.

Exports and generated reports

30 days in Horizon Eye-controlled temporary storage

Auto-delete; customer must control any downloaded copy.

Exports must be scoped, authorized, and logged.

Backup copies

Rolling 35 days target

Expire through normal backup rotation.

Deleted live records may persist until the backup cycle completes.

Financial/tax/order records

7 years or legally required period

Retain securely and separately.

Applies only if Horizon Eye becomes responsible for such records.

3. Account deletion and rights requests

Horizon Eye will provide a visible in-app account-deletion initiation path and a public web deletion-request path. A deletion request may require proportionate identity verification and can be paused only for a stated lawful reason. The requester receives confirmation, expected timing, and completion notice. Horizon Eye will delete, de-identify, or disassociate account data according to this policy, except where a legal hold, fraud/abuse investigation, transaction record, security obligation, dispute defense, or law requires limited retention.

Property-management customers may request termination of community access following lease end or another authorized event, but that workflow is not a substitute for Horizon Eye’s user-facing deletion process. A resident deletion request cannot be denied merely because it is inconvenient for a Customer. Where Customer and Horizon Eye both hold data, the parties will coordinate under the DPA to identify who must respond and which data is retained independently.

4. Legal holds and preservation

The legal lead may issue a written hold when litigation, regulatory inquiry, law-enforcement preservation, security investigation, insurance claim, or other legal obligation reasonably requires preservation. The hold must define scope, custodian, reason, preservation date, review date, and release authority. A hold suspends ordinary deletion only for the in-scope information. The legal lead must review holds at least every 90 days and release data promptly when the lawful need ends.

5. Community-code authorization policy

Community codes and temporary passwords are access credentials for a specific authorized individual and community. Customer must generate, issue, rotate, disable, and audit them under documented authorization rules. Codes should be unique, time-limited, non-transferable, and linked to a validated resident/occupant record. Temporary passwords must force change on first successful login and must not be stored or transmitted in plaintext.

Customer must promptly revoke or update access on lease termination, role change, suspected compromise, duplicate entry, inaccurate roster data, or a verified safety/security concern. No code may be used to monitor, retaliate against, discriminate against, or otherwise harm a person. Horizon Eye may independently rate-limit, require reauthentication, invalidate suspicious credentials, or suspend a code/community connection where there is evidence of abuse or security risk. All material code issuance, activation, deactivation, and exception actions must be auditable.

Horizon Eye Vulnerability Disclosure Policy

Effective 2026/09/17

Security contact: [INSERT security@ EMAIL OR VULNERABILITY INTAKE URL]

1. Reportable issues

Researchers may report suspected vulnerabilities affecting Horizon Eye websites, mobile applications, portals, APIs, authentication, authorization, data isolation, storage, integrations, or infrastructure. Useful reports include a clear description, affected asset/function, reproducible steps, potential impact, proof of concept limited to the minimum necessary, and a safe contact method.

Do not submit credentials, personal data, customer rosters, incident contents, or other sensitive data unless Horizon Eye asks for it through a secure method. Do not publicly disclose an issue before Horizon Eye has had a reasonable opportunity to investigate and remediate it.

2. Safe-harbor expectations

Horizon Eye will not pursue legal action against a researcher who acts in good faith, follows this policy, avoids privacy harm and service disruption, and reports promptly. Good-faith research does not include accessing, downloading, altering, deleting, or retaining data beyond what is strictly necessary to demonstrate a vulnerability; exploiting a vulnerability for competitive, financial, retaliatory, or criminal purpose; social engineering personnel; physical intrusion; denial-of-service testing; phishing; extortion; malware; or attacks against third-party services.

This policy grants no permission to test Customer-managed systems, property-management systems, mobile carriers, app stores, or other third parties. Researchers remain responsible for complying with applicable law.

3. Horizon Eye commitments

Horizon Eye will acknowledge a complete report within [INSERT 3 BUSINESS DAYS], triage it using risk-based priorities, request clarification when needed, and provide status updates for material validated issues. We aim to remediate critical vulnerabilities promptly, but do not guarantee a specific response or remediation period. We may credit researchers only with written permission and after remediation.

4. Coordinated disclosure

Horizon Eye asks researchers to coordinate publication with us and normally provide at least 90 days after validation, subject to the severity and complexity of the issue. We may request a longer period where disclosure would create a material risk to residents, Customers, or active remediation. We will not request indefinite silence. Horizon Eye may publish advisory information once a fix or mitigation is available.

Horizon Eye AI Governance & Transparency Policy

Owner: Horizon Eye Security / Horizon Eye Inc.

Effective date: 2026/09/16 | Review cadence: Quarterly and before a material model, provider, data-source, feature, or decision-impact change.

1. Purpose and scope

Horizon Eye may use rule-based, statistical, machine-learning, or AI-assisted systems to support content moderation, duplicate detection, incident categorization, safety-score calculation, trend summaries, operational signals, performance monitoring, and support workflows. These tools are intended to assist authorized people and improve service integrity; they are not a replacement for emergency services, professional security judgment, property-management decision making, legal review, or human accountability.

This policy applies to internally developed models, third-party AI services, automated scoring, prompts, model outputs, datasets, configuration rules, and human decisions informed by them. It applies even where a feature is described as “analytics,” “forecasting,” “risk,” “recommendation,” “classification,” or “automation” rather than “AI.”

2. Prohibited and restricted uses

Horizon Eye will not use AI outputs as the sole basis to make a decision about housing, eviction, tenancy, employment, credit, insurance, law-enforcement action, benefits, or another legal or similarly significant individual outcome. We will not use AI to identify an individual using biometric data, infer sensitive characteristics, perform covert surveillance, generate a crime accusation, or recommend vigilante or discriminatory action. We will not intentionally train a general-purpose model on resident/Customer content unless we provide clear disclosure and obtain any required authorization.

No management company or operator may use Horizon Eye analytics to suppress reports, manipulate safety scores, target residents, influence property value dishonestly, discriminate, or circumvent privacy/surveillance law. Any Customer request for a high-impact analytics function must undergo documented legal, privacy, security, and bias-risk review before development or activation.

3. Transparency and user communications

Where an AI-assisted function materially affects content visibility, reporting review, a score, a recommended action, or another meaningful user experience, Horizon Eye will provide a clear explanation of: the feature’s purpose; whether output is automated or human-reviewed; principal data categories used; material limitations; user controls; and available correction, appeal, or contact channel. We will not claim that an AI system is accurate, predictive, unbiased, guaranteed, or capable of preventing harm unless supported by substantiated evidence and lawful review.

Safety scores and forecasts are informational aggregates based on available data and configured methods. They do not establish that an incident occurred, prove a person’s responsibility, predict an individual’s behavior, or guarantee community safety. A score may change as reports are submitted, verified, resolved, removed, aged, or corrected. Human review is required for material enforcement and operational decisions.

4. Governance, risk assessment, and records

Before release, the feature owner must complete an AI Feature Record containing: intended use and users; whether the feature is automated, assistive, or high impact; inputs and data sources; training/processing/provider details; data minimization; security/privacy controls; known limitations; accuracy/evaluation evidence; fairness and misuse risks; human-review requirements; accessibility and safety considerations; monitoring plan; rollback owner; and approval signatures. Horizon Eye must maintain version history for material changes.

The Governance Committee—at minimum product, engineering/security, privacy/legal, and operations representatives—must approve restricted functions and review incident/abuse patterns. A feature may be suspended, rolled back, or limited if it demonstrates material error, bias, security risk, misuse, unexpected impact, or lack of sufficient documentation.

5. Data, vendor, and security controls

AI inputs must be limited to the minimum necessary; secured in transit and at rest where applicable; access-controlled; logged without retaining unnecessary content; and governed by retention/deletion rules. Vendors must be approved under procurement, security, privacy, and DPA controls. The feature owner must confirm whether a vendor stores prompts, trains on inputs, permits opt-out, supports deletion, identifies subprocessors, and provides adequate security controls.

Prompt injection, malicious uploads, unsafe instructions, data exfiltration, and content abuse must be tested before release. AI systems must not receive credentials, secrets, full access tokens, raw database dumps, or user content beyond the authorized feature scope. Output must be subject to validation before it can cause a privileged action.

6. Monitoring, review, and redress

Horizon Eye will monitor material AI features for availability, error rates, content-safety failures, drift, misuse, disproportionate impact, false positives/negatives, and override/appeal trends. Users and customers may report concerns through [INSERT AI/PRIVACY CONTACT]. Horizon Eye will document material complaints, investigate when warranted, correct confirmed data errors, and provide an appeal/review path where a user is materially affected by an automated or AI-assisted content/access

Horizon Eye Security Incident Response, Enterprise SLA & Business Continuity Terms

Owner: Horizon Eye Security / Horizon Eye Inc.

Effective date: 2026/09/16 | Review cadence: Quarterly and before a material model, provider, data-source, feature, or decision-impact change.

1. Definitions and roles

“Security Incident” means a confirmed unauthorized access, acquisition, disclosure, alteration, destruction, or loss of Customer Personal Data in Horizon Eye’s control that triggers contractual or legal investigation duties. It excludes unsuccessful attacks, routine scans, blocked events, customer-controlled systems, and incidents caused solely by Customer unless Horizon Eye’s obligations independently apply. “Service Incident” means a material unplanned disruption of the production Services. “Emergency” means an imminent threat to life, safety, or property and must be handled through 911 or the applicable emergency service—not Horizon Eye support.

Horizon Eye will designate an incident lead and communicate through the Customer security contact. Customer will designate a 24/7 security contact, an executive escalation contact, and an authorized decision maker. Each party will preserve relevant evidence, avoid speculative public statements, maintain confidentiality, and cooperate in good faith.

2. Incident-response process

Horizon Eye will use commercially reasonable measures to identify, contain, investigate, remediate, and document a confirmed Security Incident in its environment. After confirmation, Horizon Eye will notify Customer without undue delay, subject to legal restrictions and the need to protect an active investigation. The initial notice will include available information about the incident nature, known affected services/data, containment status, and a contact point. Horizon Eye will provide material updates as reasonably available.

Customer is responsible for determining whether it must notify residents, regulators, insurers, owners, or other third parties for Customer-controlled data or Customer legal obligations, unless the parties agree otherwise in writing. Neither party will admit fault or notify external parties using the other party’s name without prior consultation when legally permitted. The parties will maintain an incident record and conduct a reasonable post-incident review for material events.

3. Support and service targets

Severity

Example

Initial response target

Update target

Target restoration / workaround

S1 — Critical

Production service broadly unavailable; confirmed material security incident; no reasonable workaround.

1 hour, 24×7 for contracted enterprise tier

Every 4 hours

Commercially reasonable continuous effort; no guaranteed restoration time.

S2 — High

Major feature materially degraded for a community/customer; significant integration failure.

4 business hours

Daily business-day updates

Target workaround within 2 business days where feasible.

S3 — Standard

Non-critical defect, how-to, isolated user issue, or feature request.

2 business days

As reasonably needed

Scheduled through normal support/release process.

Targets are objectives, not guarantees, and do not apply to planned maintenance, beta features, third-party outages, internet/mobile carrier conditions, device issues, force majeure, Customer misuse, security suspensions, or events outside Horizon Eye’s reasonable control. Unless an Order Form expressly provides service credits, the targets create no financial remedy.

4. Availability, maintenance, and continuity

Any availability commitment must be expressly stated in an Order Form. Horizon Eye may perform planned maintenance with reasonable notice when feasible and may perform emergency maintenance without advance notice to protect security or integrity. Horizon Eye will maintain documented backup, recovery, access-control, incident-response, and business-continuity procedures appropriate to the service risk and maturity stage. Customer remains responsible for its own business-continuity plan, resident communication, physical security, emergency procedures, local records, source-system availability, and secure network/device operations.

Horizon Eye will periodically exercise or review recovery procedures and will reasonably update Customer after a material continuity event. The parties must set final recovery time and recovery point objectives only after technical validation; no unstated RTO/RPO is promised.

5. Exclusions, liability, and insurance

Horizon Eye does not guarantee that the Services will prevent, detect, or respond to a security or safety event; that data will never be lost; or that all incidents will be identified. The Services Agreement’s limitation of liability, warranty disclaimers, indemnities, and insurance terms apply. Customer will maintain its own appropriate property, general liability, cyber/privacy, and business-interruption coverage. Horizon Eye’s liability for a Security Incident is subject to the agreed cap and non-waivable legal obligations, unless the Order Form expressly provides otherwise.

Legal

Horizon Eye Privacy Policy & State Privacy Supplement

Effective 2026/09/17 Controller / business: HORIZON EYE INC, doing business as Horizon Eye Security (“Horizon Eye”). Privacy contact: privacypolicyandagreements@horizoneyesecurity.com | Support: support@horizoneyesecurity.com

1. Scope and notice

3. How we use information

4. How and with whom we disclose information

5. AI/ML and analytics processing

6. Retention, deletion, and account closure

7. Security and incident handling

8. Your privacy choices and rights

9. California notice

10. Children, international data, and changes

11. Biometric and precise-location supplemental notice

Effective 2026/09/17

Controller / business: HORIZON EYE INC, doing business as Horizon Eye Security (“Horizon Eye”).

Privacy contact: privacypolicyandagreements@horizoneyesecurity.com | Support: support@horizoneyesecurity.com