Overview
This policy covers the iOS app and the public 24 Block website.
24 Block is a visual time-block planning app for iOS. It works without an account and stores the main planning data on the user's device. While Lock Screen Live Activity is enabled on iOS, selected planning details are sent to an update service as described below.
The public iOS v1.1 release includes optional device-calendar display and private iCloud planner sync. Both are off until the user chooses to enable them. A separate 24 Block account or sign-in is not required or offered. The optional Live Activity update service has a separate upload confirmation and data flow, as described below. Features and available controls can vary by installed app version.
24 Block is operated by Jamgo Labs Ltd, a private limited company registered in England and Wales.
- Company number: 17181144
- Registered office: 4th Floor, Silverstream House, 45 Fitzroy Street, London, England, W1T 6EB
- Privacy contact:
support@24block.app
For the limited personal data described in this policy, Jamgo Labs Ltd is the controller.
Data We Store On Device
24 Block stores planning data locally on the device so the app can work as intended.
This can include:
- schedules and time blocks
- recurring routine definitions and generated routine blocks
- block comments and notes entered in the planner
- weekly and monthly note cards in builds that include this feature
- activity categories, colours, and theme selections
- app settings and planning preferences
To avoid asking for an App Store review too soon or too often, supported releases keep limited review-request information on the device: the first-use time, capped use-session and distinct-day counts, the latest counted session time, and recent request times and app versions. This information is not sent to Jamgo Labs, included in planner exports, or synced through planner iCloud sync. A rating or review you choose to submit through Appleās system dialog is handled by Apple under its own terms and privacy practices. The app cannot see whether you submit or dismiss that dialog.
On supported iOS devices, the app can also show current-block and upcoming-block information in a live activity or home screen widget.
Optional Device Calendars
Calendar sync is off by default. If the user connects device calendars in Settings and grants system permission, 24 Block can read calendars already available through the phone's calendar system, including calendars from providers the user has added there. Users choose which calendars to display. 24 Block does not ask for calendar-provider passwords or sign in directly to those providers.
The app reads calendar names, colours and source labels for selection, and event identifiers, titles, times, all-day status and cancellation status for display. Calendar information is held in memory while the app runs. Only the enabled setting, selected calendar identifiers and a flag recording that a selection has been made are saved in local app preferences. Imported events are kept separate from planning blocks and are not added to planner storage, iCloud planner sync, exports, schedule sharing, statistics, widgets or Live Activity update payloads. 24 Block does not upload this calendar information to its services or write, edit or delete events in the source calendars.
The app refreshes the displayed date range while in use, on return to the foreground and when the user requests a refresh. The phone's calendar system and the calendar provider control when provider changes reach the device; 24 Block does not provide its own background calendar sync service.
On iOS, reading events requires the system's full calendar-access permission, which also permits writes at the operating-system level. 24 Block uses that access only to read. It does not request access to reminders or device location for this feature.
Turning Calendar sync off clears the imported calendar information from the app's memory and stops further calendar reads while off. Users can also revoke access in device Settings. Neither action deletes events from the source calendar. The calendar provider and operating system continue to handle the original calendars under their own settings and privacy practices.
Optional Private iCloud Planner Sync
Local planning remains available without iCloud sync or a separate 24 Block account.
Private iCloud planner sync
Sync starts off. Enabling it requires confirmation before the existing plan is uploaded. On supported Apple systems, planner records are stored in the private CloudKit database of the Apple Account signed into iCloud on the device. 24 Block uses the Apple Account already configured for iCloud on the device; it does not require a separate 24 Block sign-in or silently move data between Apple Accounts.
Synced data includes scheduled blocks and comments, weekly and monthly note cards, routine rules and exceptions, custom activities and ordering, day themes and assignments, and these shared preferences: time format, app language, appearance mode and accent colour. Navigation, scroll position, selections, onboarding progress, push tokens, Live Activity identifiers and undo/redo history stay local. Weekly and monthly note cards are included in planner backup exports and restore. Their text is excluded from schedule sharing, statistics, widgets and Live Activity update payloads. Statistics and widget content are calculated from the plan. CloudKit is provided by Apple and is subject to Apple's service settings, availability and storage limits.
The Apple implementation migrates the planner to a native local store shared with the app's extension group, with atomic writes for records and pending sync work. It retains recovery copies of legacy data and a bounded set of recent backups and conflict/account-change recovery records. A failed migration keeps the original data recoverable. Platform backup settings may also apply. This policy does not claim end-to-end encryption for planner records or exports.
Sync and planner deletion
Disabling sync stops future sync work and retains the device and cloud copies. Erasing the planner is a separate action in the app's iCloud settings. Cloud erasure needs access to the relevant iCloud account, and incomplete cleanup remains visible. The reset protocol prevents old offline devices from restoring the erased dataset as the active plan. Keeping a local copy leaves sync off until the user deliberately enables it again. These actions affect 24 Block planner data, not the person's Apple Account.
Local planner erasure also removes the app's internal planner recovery copies and legacy planner storage. If cleanup of the old local storage fails, its pending status survives restart and the app retries; Settings also offers a retry. User-created exports or copies saved to another app are outside that deletion. Exported files contain personal planner content and recovery data; users choose where to save or share them and are responsible for those external copies.
Optional Live Activity Update Service
Lock Screen Live Activity is off by default. In v1.1, enabling it in Settings first explains what will be sent and asks the user to allow updates. Earlier On settings without that recorded confirmation are turned off; users can enable the feature again after reading the explanation. Existing Off settings stay off. Users can withdraw permission at any time by turning it off in Settings. While enabled on a supported iOS device, 24 Block sends the activity's push token and identifier, today's scheduled block names, colours, times, comment and note excerpts, and update timestamps to its backend hosted on Vercel. The backend uses Upstash QStash to queue future updates and Apple Push Notification service (APNs) to deliver them to the Live Activity while the app is in the background or closed.
This service does not create an account or synchronise the planner between devices. Home screen widgets use on-device data.
Turning Lock Screen Live Activity off stops new schedule uploads and requests cancellation of queued updates for the activity. Cancellation requires a working connection and may not stop messages already being delivered. It does not delete infrastructure logs or provider records. Vercel, Upstash, and Apple may also process request and delivery metadata to operate and protect the service.
For service protection and coordination, the update service may use Upstash Redis to hold keyed hashes derived from request IP addresses, activity push tokens and update contents, together with update-generation identifiers, timestamps and counts. This control store does not hold raw IP addresses, push tokens or planning text. Rate-limit counters expire after one minute; activity control records expire 30 hours after their last accepted refresh. These periods apply to those control records, not to infrastructure logs, queued updates, dead-letter records or other provider retention.
App integrity checks in supported releases
The following processing applies to releases that enable Apple's App Attest protection for the optional Live Activity service. It does not enable the service or grant upload permission by itself. Local planning and private iCloud planner sync do not require these checks.
After the user allows the disclosed Live Activity uploads, supported releases may ask Apple to verify the app and its device-generated signing key. The update backend on Vercel receives an app-specific key identifier, Apple-signed verification proofs, app identity, version and launch-validation information where available, and request-verification metadata. This metadata includes short-lived challenges, request digests and sequence counters that help prevent reused or altered requests. The same app key can be recognised across protected requests. We use this information to protect the update service from abuse, not for advertising or analytics. Apple operates App Attest under its own service terms and privacy practices.
The private signing key remains protected on the device. The app keeps its credential identifier and any pending registration proof in the device's Keychain, separately from the planner and private CloudKit database. Pending registration proof is removed when registration is confirmed or the attempt is retired; the credential identifier may remain to allow retry if retirement cannot be confirmed. These credentials are not included in planner exports or shared planner preferences.
Upstash Redis stores the verified public key, Apple's verification receipt and an anti-replay counter under a keyed hash associated with the app key and service. This credential record expires 90 days after its last valid signed update request, or after its initial registration if it has received no such request. A rejected proof does not extend that period. Challenges expire within five minutes, and challenge rate-limit counters within one minute. A confirmed, signed credential-retirement request removes the public key, receipt and counter; an opaque retirement marker can remain for up to five minutes to prevent reuse of an earlier registration attempt.
Turning Live Activity updates off requests retirement of an existing credential in releases that use these checks. Retirement requires a working connection and usable device key and may fail. If it is not confirmed, local credential metadata can remain for retry and the server credential record follows its idle expiry. Turning updates off, erasing the planner or uninstalling the app does not promise immediate removal of security metadata, provider logs or backups. These credential expiry periods do not set retention for Vercel, Upstash or Apple infrastructure records. Contact support@24block.app about data held by the update service.
Data We Do Not Collect Through the App
24 Block does not require an account and does not intentionally collect the following through its core local-planning functionality:
- name
- phone number
- payment information
- profile data
- advertising identifiers
- analytics data
- crash-reporting data
- location data
- calendar account data
- photos, files, or audio recordings
The optional calendar feature reads the device-calendar information described above after permission, without receiving calendar-provider credentials or uploading calendar content to 24 Block services. Optional iCloud sync and Live Activity uploads are described separately above. The app does not offer a separate 24 Block account, collaboration or advertising.
If a user chooses to contact support, Jamgo Labs Ltd may receive the email address, message content, and any details the user chooses to include in that email. Support email is used to respond to the request and improve support for the app, not for advertising or third-party marketing.
How Data Is Used
Planning data is used to provide the app's core functionality, including:
- displaying and editing schedules
- saving categories, themes, and preferences
- generating recurring routine blocks
- showing current-block and upcoming-block information in live activities and home screen widgets on supported iOS devices
24 Block does not use in-app data for advertising, third-party marketing, behavioural profiling, or personalised ad targeting.
Where support email or website request metadata is processed, the purposes are to:
- respond to support, feedback, or privacy requests
- maintain basic business records
- operate, secure, and protect the public website
- understand and resolve service, abuse, or security issues
Lawful Bases
Where UK data protection law applies, Jamgo Labs Ltd relies on the following lawful bases for the limited personal data it handles:
- legitimate interests for responding to support requests, maintaining service security, protecting the website from abuse, and producing aggregate website analytics, which visitors can turn off on the privacy page
- legal obligation where records must be kept to comply with applicable law
- consent only where a user has clearly chosen an optional action, such as sending a support email or using a device share feature
- consent for the optional Live Activity update service; v1.1 asks the user to allow the disclosed uploads before enabling it in Settings
- consent for optional iCloud planner sync when the user chooses to enable it
- consent for optional device-calendar access when the user connects calendars and grants system permission
Users can turn Lock Screen Live Activity off in Settings, leave Calendar sync off or turn it off, revoke calendar access in device Settings, and choose not to send support email or share schedule content through external apps.
Sharing and External Actions
24 Block includes optional actions that hand user-selected content to other apps or services only when the user initiates them.
These include:
- sharing schedule text through the system share sheet
- preparing feedback to
support@24block.appin the iOS system mail composer, or handing it to the user's email app when the in-app composer is unavailable - opening external links such as the product website
Opening the feedback composer does not send the message automatically. The user chooses whether to send, save a mail draft, or cancel.
When a user uses one of these actions, the selected content is handled by the chosen app, service, or provider under that provider's own terms and privacy practices. If the user sends feedback to support@24block.app, Jamgo Labs Ltd receives the email and its contents so the support request can be handled.
After the user allows the disclosed uploads, the Live Activity update service sends the details described above while its setting is enabled; it does not require a separate sharing action for each update.
Public Website
The public website is a static site hosted with Cloudflare Pages. It uses PostHog's EU service, acting as our processor, to produce aggregate statistics about website visits and clicks on links to the App Store, so we can improve the website. This analytics is not used for advertising or to build profiles of individuals.
PostHog analytics can include the page viewed, the download button's position, referring website domain, campaign labels, browser and device type, IP address, approximate location (country, region and city, worked out from the IP address), and event time. An App Store click records a visit to the store listing; it does not establish that the app was downloaded.
You can object at any time: use the "Turn off analytics" button in this section at 24block.app/privacy. The website then stops sending events straight away and no longer loads PostHog in that browser. It remembers the choice in your browser's local storage, under the name 24block-analytics; this stores only your choice, not an identifier. Clearing your browser's site data resets it. If your browser sends Do Not Track or Global Privacy Control, PostHog is never loaded. Turning analytics off does not affect how the website works.
PostHog is configured for cookie-free audience measurement with no analytics cookies or browser-storage identifiers. Its stateless mode uses a daily rotating identifier derived from request metadata, including IP address and user agent. PostHog receives the IP address to process the request, derive this identifier and work out approximate location, and stores it with the analytics events.
We do not enable session recordings, automatic form or text capture, or person profiles. Query strings, URL fragments and referrer paths are removed before analytics events are sent. Only short campaign labels using letters, numbers, dots, hyphens or underscores are accepted. Analytics is used to improve the website and understand which pages and campaigns lead visitors to the App Store.
Cloudflare and other infrastructure providers may process standard request metadata, such as IP address, user agent, request URL, referrer, and timestamp, to deliver and protect the website under their own terms and privacy practices.
Service Providers
Jamgo Labs Ltd may use service providers to operate 24 Block and its public website. These may include:
- Apple App Store
- website hosting and security providers such as Cloudflare
- PostHog for cookie-free website analytics hosted in the EU
- Vercel for Live Activity API hosting, Upstash QStash for scheduled update delivery, and Apple APNs for delivering updates to the device
- email and business infrastructure providers used to receive and respond to support messages
These providers may process limited personal data only where needed to provide their services, comply with law, or protect their platforms.
Some providers may process data outside the United Kingdom. Where this happens, the provider is responsible for applying the transfer safeguards required for its service, such as adequacy arrangements or contractual safeguards.
Permissions and Platform Capabilities
Optional calendar display requests calendar access, as described in the device-calendar section above.
The iOS platform configuration includes:
- iOS live activity support for the current block
- iOS home screen widget support for current and upcoming blocks
- an iOS app group used by the widget and live-activity extension
- iOS app transport security configured to disallow arbitrary network loads while allowing local networking for development
The calendar feature includes iOS calendar usage descriptions for legacy and full calendar access. These permissions are requested only after the user chooses to connect calendars.
If the app later adds capabilities or permissions that affect user data, this policy will be updated before those changes are released.
Storage, Backups, and Deletion
The app stores the main planning data locally. If users enable iCloud sync, planner records are also stored in their private CloudKit database as described above. Disabling sync keeps existing local and cloud copies; planner erasure is a separate action. When Lock Screen Live Activity is enabled, copies of the update details are held by the update service and its delivery queue. Queue, retry, failed-delivery, and infrastructure records are subject to provider retention settings and policies; turning the feature off or uninstalling the app does not itself erase these records. Contact support@24block.app about data held by the update service.
Depending on the user's operating system settings, local app data may also be included in device backups managed by Apple. Backups are not operated by 24 Block.
Users can remove planning data from within the app where controls exist, or remove app data by uninstalling the app, subject to how the operating system handles local storage and backups.
Support emails and privacy requests are kept only for as long as reasonably needed to handle the request, maintain business records, resolve disputes, and comply with legal obligations.
Website request metadata is retained by hosting and security providers under their own retention settings and policies. PostHog website analytics events are kept for up to one year.
Security
24 Block uses local storage for the planner and encrypted network connections for its configured Live Activity update service. No software system can guarantee absolute security, but the product should follow platform security defaults and continue improving as features expand.
Private CloudKit sync uses Apple's platform access controls and the Apple Account configured for iCloud on the device.
Children
24 Block is a general productivity app and is not intended to knowingly collect personal information from children.
Privacy Rights
Depending on where the user lives and the basis for processing, privacy rights may include the right to:
- access personal data held about them
- ask for inaccurate personal data to be corrected
- ask for personal data to be deleted
- restrict or object to certain processing
- receive a copy of personal data in a portable format
- withdraw consent where consent is the lawful basis
Most planning data is stored locally on the user's device and is not held by Jamgo Labs Ltd. For support emails or other personal data Jamgo Labs Ltd does hold, users can contact support@24block.app.
Users also have the right to complain to the UK Information Commissioner's Office at https://ico.org.uk/ if they are unhappy with how their personal data is handled.
Changes to This Policy
If the app, legal requirements, or data practices change, this policy will be updated before those changes take effect in release builds.
Contact
For privacy questions, contact support@24block.app.