Privacy Policy
Accounts are optional. Curfew works locally without an account.
Who we are
Hypertext Studio is responsible for the personal information it handles through Curfew, its website, accounts, and connected services. This policy explains what stays on your devices and what is shared when you choose an account or integration.
What we use and why
- Your schedules, extension and override budgets, wake settings, preferences, activity, reflections, and license keys make Curfew work and let you review your history.
- If you use an account, we handle your identity and email, sign-in and recovery information, connected devices, assistant permissions, and records of account and remote-control activity. We also handle information about when encrypted content changes and which device should receive it. This supports sign-in, sync, security, and device control you authorize.
- Purchase records, payment and refund references, and support messages let us manage licenses, billing, refunds, and your requests.
- Website requests and connection information, including IP addresses, let us deliver pages and protect the service. Sign-in uses cookies or tokens. Our account service does not save raw IP addresses in authentication records; it limits abusive requests without saving those addresses in your account. Hosting providers may handle connection logs separately.
The local app has no analytics, telemetry, or crash-reporting service. We do not sell personal information or use it for advertising.
On your devices and connected services
Without optional integrations, your schedules, activity, reflections, and settings stay on your devices. Calendar access shows today’s events without changing them. Notifications provide warnings and alerts. Optional Accessibility access supports keyboard shortcuts during lockout.
If you enable camera presence detection, Curfew checks on your Mac whether a person is present, without identifying them. Camera frames are not saved or sent. The result is replaced by the next reading or cleared when capture stops. Presence changes and camera start and stop events are recorded locally. Turning the feature off releases the camera.
Optional browser enforcement observes the web destinations you visit while enforcing a task. It does not read page content, embedded resources, or your general browsing history.
Accounts and other optional services
Curfew Account sync is end-to-end encrypted. Hypertext Studio carries the encrypted content but does not hold the keys needed to read it. Your account identity, purchase records, device connections, and security activity are separate from that encrypted content.
Save your Curfew Recovery Key. Sign-in backup codes restore access to your account, but an enrolled device or your separate Recovery Key is needed to read encrypted content.
If you enable optional device status reporting, Curfew sends the server you choose a device identifier, lockout status, time zone, an identifier for the current schedule, and information about the timing and order of status changes. It does not send reflections, camera frames, or presence results. The receiving service has its own privacy and retention terms.
If you enable iCloud schedule sync, your settings, device registration, activity updates, and lockout status are stored in your private iCloud database. Apple’s service and privacy terms apply.
Lifetime license checks work offline. Subscription licenses contact our license service on launch and periodically while active to renew the license.
Service providers and sharing
Cloudflare hosts our website and account services. Stripe handles payments and receives payment details directly; we receive purchase and license records. Apple or Google receive the information needed when you choose their sign-in service. Cloudflare forwards support email to Google Workspace, which handles our support correspondence.
We may disclose information when applicable law requires it or when needed to protect rights or security. This does not give others unrelated access to your content.
Assistants and task review
When you connect an assistant on your Mac, it can read your enforcement state, schedules, extension and override budgets, current-week activity, weekly summaries with device names and device attribution, and reflections. It can request extensions or schedule changes. It can read reflections but cannot change them. Curfew asks before write requests by default; you can change that setting.
An assistant may send this information to its own service, where its provider’s privacy and retention terms apply. Encrypted sync does not prevent sharing you authorize with an assistant.
Remote assistants receive only the access you approve. The hosted service handles device status, requests and reasons, and security records needed for that access. Remote unlocks are limited in time and recorded. Direct unlock is off by default and needs separate authorization. You can revoke access.
If you enable task-based browser enforcement, known destinations stay on your Mac. For an unfamiliar destination, Curfew sends Docket and Athena the site address and path, the organization and task being reviewed, your justification, and any challenge answer. It removes URL credentials, query strings, and fragments first. Review may use AI under those services’ policies. Avoid putting secrets or sensitive information in your answers.
Curfew temporarily keeps review answers while a decision is pending and clears them when the review finishes. Its local browser decision history records the hostname, decision, and type of access allowed, without paths or answers. Docket, Athena, and connected assistants may retain what they receive under their own policies. Deleting Curfew data or your account does not delete their copies.
Retention and deletion
Local activity and reflections have a rolling 52-week retention target. Cleanup runs while Curfew is open, so older records can remain until a later successful cleanup. Browser decision history follows a 90-day rotation policy; the current log can remain until it rotates. Settings and license keys remain until removed.
You can export account information before deleting your account. Successful deletion removes your account, its encrypted content, and access during the request. Purchase records are kept separately, and retained security records are no longer linked directly to your account. Cancel subscriptions separately before deletion.
Account deletion does not erase copies on your devices, in iCloud, with assistants, or with payment providers. See the Data Retention Policy for periods and deletion limits.
Security
Curfew encrypts synced content, limits assistant access to what you approve, and requires additional verification for sensitive account actions. Protect your devices, sign-in details, and Recovery Key. No system can guarantee absolute security. See Security for more information and reporting.
Your choices and rights
You can use Curfew without an account, decline optional permissions, turn off integrations, revoke assistant access, export account information, and delete your account. Manage local and iCloud copies separately.
Depending on applicable law, you may have rights to access, correct, delete, restrict or object to the use of your information, receive a portable copy, withdraw consent, and complain to your data protection authority. Contact us to exercise these rights. We may need to verify your identity.
Where a legal basis is required, we use information to provide the account or purchase you request, protect and support the service, meet legal obligations, or act on your consent for optional processing. You can withdraw optional access in settings without affecting earlier lawful processing.
Children
Hosted accounts are for people aged 16 and older. A parent or guardian must agree and supervise where local law requires it. We do not knowingly collect hosted account information from children under 16. Contact us if you believe a child has provided it. This account rule does not change the MIT license for the accountless app.
International processing
Hypertext Studio operates in the United States. We and our providers may process information in the United States or other countries with different privacy laws. Where law requires safeguards for an international transfer, we must use a valid transfer mechanism. Contact us about the safeguards that apply to your information.
Changes
We show the effective date above and give prominent notice of material changes before new processing where required. The policy history preserves prior documents. This update explains current practices and does not authorize unrelated new uses of your information.
Contact
For legal notices and privacy requests, email legal@hypertext.studio or write to Hypertext Studio, 1810 East Sahara Avenue STE75246, Las Vegas, NV 89104, United States.
For help, refunds, billing, security, or abuse reports, email support@thecurfew.app. For general inquiries, email contact@thecurfew.app.