Privacy Policy

Effective date: November 5, 2026

Offtime ("we", "our", "us") provides a companion app and this website for households that run OPNsense. This policy explains what information the app and site handle, what leaves your device, and how to contact us.

What Offtime does

Offtime connects to your OPNsense firewall on your local network to read DHCP leases and manage schedule and blocking configuration through the Offtime OPNsense plugin. Enforcement happens on your firewall, not on Offtime servers.

Information stored on your device

• OPNsense API URL, key, and secret
• Local app state such as profiles and schedule preferences

Credentials are stored using platform secure storage and are used by the app to connect directly to your firewall. The telemetry event allowlist excludes credentials, firewall addresses, device details, profile names, and arbitrary error text.

Firewall management data

The app reads DHCP leases from your firewall and sends requested schedule and blocking changes directly to it over your local network. Offtime does not operate a cloud service that enforces those rules. If you turn on the optional app functions described below, our service providers may receive interaction, diagnostic, or screen data from the app.

• DHCP lease data read from OPNsense
• Firewall aliases, schedules, and rules created or updated by the app

Optional functions in the app

The app's optional functions are separate switches in its Settings, under Privacy. The iOS and Android apps offer Analytics, Error reports, and Session replay. The web app offers Analytics, page performance, and Error reports. Each one starts off, and each choice is saved for that app installation or browser. Turning a switch on takes effect after you restart Offtime. Turning one off takes effect right away and stops further collection on that device or browser; information already sent is kept under our service providers' settings and policies. These switches are separate from the choices for this website described below: neither set changes the other.

• Analytics: when on, the app sends a limited set of product events, such as starting a firewall connection test. Those events do not include a persistent installation identifier, user email, credentials, network addresses, device names, household/profile content, or arbitrary error text. Analytics does not record sessions, and it does not carry error reports.
• Error reports: when on, and when the build has error reporting set up, the app can send sanitized app errors and, on iOS and Android, crash diagnostics. Event messages, request details, screenshots, view hierarchies, and user information are removed or disabled. Performance tracing, profiling, logs, and replay are off in this function. The public marketing website does not send error reports.
• Session replay (iOS and Android only): when on, the app may capture interactions. Capture pauses on screens that contain firewall, device, profile, schedule, or diagnostic information. The web app has no session replay.
• Page performance (web app only): when on, the web app measures page performance and visit counts. Turning it off reloads the page if it was running.

The apps and public marketing website do not send passwords, API keys, API secrets, firewall URLs, email addresses, authentication codes, household or child names, or app content as analytics event properties. Analytics event detail is limited to fixed categories and status codes. Error reports also keep the type of error and where in the code it happened. Our service providers' software may process standard technical data needed to deliver their services, such as app version, operating system, and the network address of the request.

Your choices on this website

The public marketing website offers three optional functions, each behind its own choice: Product analytics, Session replay, and Reliability and performance. All are off until you allow them, and none of them loads before you choose. On your first visit a banner offers Reject all and Accept all; Manage choices lets you allow each one separately. They run only on the home page and this policy, and not when the page address carries query data or a fragment other than a plain in-page anchor, or when your browser reports that the page that linked here had query data in its address.

If your browser sends a Global Privacy Control signal and you have not chosen yet, we treat it as rejecting every optional function and do not show the banner. You can still allow one yourself from Privacy choices. If you turn the signal on after allowing any, they stop and you are asked again.

You can change your choices at any time from the Privacy choices link at the bottom of every page. Your decision is stored in this browser's local storage, under the key rckt.consent, and other open tabs of this site follow it. We ask again when this policy changes in a way that affects your choices, when we add a service under a choice you allowed, and 12 months after you decided. Clearing browser storage removes the saved choice, and you are asked again on your next visit. A no given in this site's earlier privacy panel carries over; anything you allowed there is asked about again.

Turning a function off stops further collection in this browser, removes the cookies and storage it set, and reloads the page when a running function cannot be stopped otherwise. Information already sent cannot be recalled; it is kept as described under "How long we keep it" below.

Manage privacy choices

How this website uses data

• Necessary (always on): delivers the site.
• Product analytics (off until you allow it): shows us how the product is used so we can improve it, such as pages viewed and page speed.
• Session replay (off until you allow it): recordings of how pages are used, with what you type hidden, so we can see where people get stuck.
• Reliability and performance (off until you allow it): helps us keep things fast, such as load times and visit counts.

Your choices: turn any of these on or off at any time in Privacy choices.

Who handles it: we use service providers to run these functions, and they may process data outside your country, including in the United States and the European Union.

How long we keep it: only as long as we need it for these purposes. What the optional functions collect is kept for no more than 7 years.

Your browser may also send a short technical report to the service that delivers this website when a request to this website fails. That is part of delivering the site, and the choices above do not turn it off.

Controller for the data this website collects: rckt corp., based in Ontario, Canada.

What we do not operate

• No Offtime cloud account is required
• No remote access service for your firewall
• No sale of household or child identity data

Retention and deletion

On-device credentials are removed when you delete app data or uninstall Offtime. Information the app's optional functions have already sent is kept under our service providers' settings and policies, and periods differ by function. For this website, see "How this website uses data" above.

Children

Offtime is intended for parents and household administrators. It is not directed at children to use directly.

Changes

We may update this policy as the product evolves. Material changes will be reflected on this page with a revised effective date.

Contact

Questions about privacy or data handling: [email protected]