← Home

Focus Geo-Fence — Privacy Policy

Effective date: 01.14.2026 Last updated: 07.22.2026

Ockhamlogic (“Focus,” “we,” “us”) provides the Focus Geo-Fence platform (the “Service”) to schools, districts, and learning centers (“Schools”) to help them manage school-issued and enrolled devices during the school day. This Privacy Policy explains what information the Service collects, how we use it, and the choices and rights available to Schools, parents, and students.

We built Focus to be privacy-first: it controls how devices behave on campus, during school hours, and is designed to be hands-off outside those bounds. Focus is access control for the school day — not monitoring or surveillance.

or tap a section to open it.
1. Our role: Schools decide, Focus processes

Schools use Focus to carry out their own device policies and to meet legal obligations (such as state phone-restriction laws). In privacy terms, the School is the controller of student-related data and Focus acts as a service provider / school official processing that data only on the School’s behalf and instructions, consistent with the Family Educational Rights and Privacy Act (FERPA) “school official” exception and the Children’s Online Privacy Protection Act (COPPA) school-consent model.

We do not use student data for our own purposes. Any data-processing agreement, data privacy agreement (e.g., an SDPC National Data Privacy Agreement), or contract signed with a School governs and, where it conflicts with this policy, controls.

2. Information the Service collects

a. School administrator accounts. When a School creates administrator users, we store the administrator’s email address, a hashed password, assigned role (e.g., admin, viewer), and organization. Administrators are School staff, not students.

b. Device and technical information. When a device is enrolled, the Service stores a device token and enrollment token, platform (iOS/Android), OS version, device model, push-notification tokens (Apple APNs / Google FCM), enrollment and last-seen timestamps, and device permission states (location, notifications, background refresh). Devices are identified by tokens, not by a student’s name or identity.

c. Location information (limited). To determine whether a device is inside a School-defined campus boundary (“geofence”) during the School’s bell schedule, the Service uses the device’s location and stores the device’s most recent location point (latitude, longitude, accuracy) and the time it was recorded. Location is used to switch the School’s policy on or off — not to build a location history or track a student’s movements.

d. Compliance and device events. The Service records events needed to enforce and report on the School’s policy — for example, entering or leaving a geofence, a restriction starting or ending, or a lockdown — along with the related geofence, schedule, or policy and a timestamp.

e. Enrollment and security logs. For security and troubleshooting, enrollment attempts are logged with the IP address, user agent, outcome, and any error.

f. Emergency and lockdown records. Emergency-bypass requests (reason, approver) and Emergency Lockdown actions (who activated, when, and delivery to devices) are recorded.

g. Billing and support. If your School has a paid subscription, we process billing information through our payment processor. If you contact support, we keep your communications.

3. What the Service does NOT collect or do
4. How we use information

We use the information above only to: (a) provide and operate the Service; (b) enforce the School’s device policy on campus during school hours; (c) enable Emergency Lockdown and safety features; (d) generate the compliance records and reports the School needs; (e) secure the Service, prevent abuse, and troubleshoot; and (f) provide support and administer billing. We do not use student data to train advertising systems or for any purpose unrelated to providing the Service to the School.

5. How information is shared

We share information only as needed to run the Service and as directed by the School:

We do not sell personal information and do not share it for cross-context behavioral advertising.

6. Data retention and deletion

We retain personal information only as long as needed to provide the Service and to meet the School’s legal/reporting obligations, then delete or de-identify it. Compliance-event and log data are subject to automatic time-based deletion according to configured retention periods. On a School’s request, or upon termination of the School’s agreement, we will delete or return the School’s data as directed and within the timeframe stated in the applicable agreement.

7. Security

We use administrative, technical, and physical safeguards designed to protect information, including: encryption in transit (TLS) and at rest, a signed, per-device command channel (so a leaked device token alone cannot impersonate a device), role-based administrator access, least-privilege cloud permissions, network isolation of databases, automated backups, and logging of security-relevant events. No method of transmission or storage is perfectly secure, but we work to protect your information and to improve our safeguards over time. See our Security Overview for detail.

8. Children’s privacy (COPPA)

Focus is provided to Schools for educational purposes. Where the Service is used with students under 13, the School provides consent on behalf of parents under COPPA’s school-consent model, and Focus uses the resulting information only to provide the Service to the School. Parents may exercise their rights through their School (see Section 9).

9. Rights and choices for Schools, parents, and students

Because the School controls student data, parents and eligible students should direct requests to their School. The School can, through the Service or by contacting us, review, correct, export, or delete data associated with a device. We will support Schools in responding to access, correction, and deletion requests as required by FERPA, COPPA, and applicable state student-privacy laws. Administrators may update or delete their own account information.

10. Data location

The Service is hosted in the United States. If you access it from outside the United States, you understand information is processed in the United States.

11. Data breach notification

If we become aware of a security incident affecting personal information, we will notify the affected School(s) without undue delay and cooperate with the School so it can meet its own notification obligations, as described in the applicable agreement and by law.

12. Changes to this policy

We may update this policy. Material changes will be communicated to Schools, and the “Last updated” date above will change. Continued use after an update constitutes acceptance of the revised policy, subject to any School agreement.

13. Contact us

Ockhamlogic 8001 Crestwood Court Swift Creek, NC · Contact us through our contact form.

If you are a parent or student, please contact your School first; your School administers the Service and your data.