1. What cookies and storage technologies are
A cookie is a small piece of information stored through your browser. Online services can also use local storage, session storage, scripts, tags, pixels, device identifiers and related methods to store information on, or access information from, a device.
UK rules on storage and access technologies are wider than cookies alone. They can apply to web storage and other technologies whenever information is stored on, or accessed from, your device.
Browser permissions are related but different. For example, permission to send a desktop notification or play audio is controlled by the browser or operating system and is not itself a cookie.
2. Consent, exceptions and your choices
Under the UK Privacy and Electronic Communications Regulations (PECR), storage or access generally needs prior consent unless an exception applies. UP TIMER only relies on an exception where the actual purpose and implementation meet its conditions.
Examples can include authentication, security, payment flow, entitlement checks, consent records and storage needed to provide a feature you actively use.
Selected settings or interface choices may be stored where necessary for the requested feature or, where the legal conditions are met, under the relevant functionality or appearance exception.
Limited analytics may require consent or may qualify for the statistical-purposes exception where its sole purpose is aggregate measurement to improve the service and a simple, free objection is available.
Advertising, profiling or behavioural tracking is not treated as necessary service storage. Where used, the required consent and controls must be in place before non-exempt technologies are activated.
Where consent is required, non-exempt technologies are not activated before you choose them, and withdrawing or rejecting that choice should be as straightforward as accepting it.
3. Current service inventory
The table below describes the main storage and access technologies associated with the current website and browser product. Exact identifiers and lifetimes can vary by browser, provider configuration and product change, so the inventory is reviewed when the service changes.
| Technology / provider | Purpose | Typical duration | Choice position |
|---|---|---|---|
| Timer local or session storage | Remember timer settings, selected preferences, Lite-window timing and application state on the device. | Session or persistent depending on the item; retained until replaced, cleared, expired or removed by the browser. | Necessary or preference/functionality depending on the exact item and purpose. |
| UP Capture local browser storage | Keep signed-out Capture items and related local application state in the browser so notes, ideas, questions, reflections and to-dos can remain available on that device. | Normally persistent until the item is deleted, local site data is cleared or the browser removes the stored data. | Used to provide the signed-out Capture feature you choose to use. It is not advertising or behavioural tracking. |
| Supabase authentication storage | Maintain sign-in sessions, refresh authentication and support account security for signed-in features. | Session or persistent according to the configured authentication session. | Necessary for the requested signed-in account service. |
| Stripe hosted checkout and customer portal | Payment, fraud prevention, checkout, invoices and subscription management on Stripe-hosted routes. | Set by Stripe according to its service and policy. | Necessary when you choose the payment or billing route. |
| Wocode / Duda website technologies | Deliver the marketing site and support platform functions such as security, page delivery and forms where used. | Depends on the specific production technology and provider configuration. | Depends on the purpose of the individual technology. |
| Consent preference record | Remember your storage choice and avoid repeatedly asking for the same decision on every page. | Stored for an appropriate period and refreshed when required. | Used to record and honour the choice you make. |
| Google Analytics / Google Tag Manager, where enabled by the live configuration | Measure visits and selected product or conversion events so the website and service can be improved. | Depends on the final analytics and consent configuration. | Used only where the applicable consent or statutory-exception conditions are met. A statistical-purposes exception requires clear information and a simple, free way to object. |
| Vercel and security / hosting logs | Deliver requests, protect the service, diagnose faults and monitor availability. | Provider and configuration dependent. | Server logs are not necessarily browser storage. Related personal-data processing is explained in the Privacy Policy. |
4. Timer and UP Capture browser storage
UP TIMER may store selected durations, working hours, water settings, movement settings, Learn Sprint choices, audio or voice preferences, Lite-window timing and other application state in the browser.
UP Capture has two different storage contexts. While you are signed out, Capture items can be held locally in that browser. When you use signed-in Capture, items can be associated with your account and synchronised through the connected service rather than existing only as local browser data.
Clearing cookies or site data can reset timer settings and can remove locally held signed-out Capture items. If an item exists only in local browser storage and has not been synchronised to an account, clearing that storage can remove it from that browser.
Browser storage is linked to the browser profile and device. Do not attempt to alter storage to bypass Lite, trial, subscription or security controls; entitlement can also be checked using server-side records.
5. Analytics and campaign measurement
Measurement can be used to understand page visits and selected product events such as CTA clicks, account creation, a first timer start, manual Full-trial activation, Full membership, Company enquiries and support contact.
UP TIMER does not use analytics to read the text of UP Capture notes, ideas, questions, reflections or to-dos. Analytics is intended to measure product and website events, not the private content you type into Capture.
Statistical analytics is not automatically exempt from consent. Where the statistical-purposes exception is relied on, the analytics must stay within that exception’s conditions, including the limited improvement purpose, clear information and a simple, free way to object. Otherwise the relevant consent is obtained before non-exempt analytics is activated.
Marketing, profiling or behavioural advertising storage is not treated as essential service storage.
6. Third-party services
The website and browser product use external providers for functions such as hosting, account authentication, payments, email delivery, analytics and website delivery. Relevant providers can include Duda/Wocode, Vercel, Supabase, Stripe, Resend and Google services where enabled.
Not every provider listed here necessarily sets storage on your browser. Some operate server-side or only when you choose a connected route. Where a third party does set or access information on your device through UP TIMER, the applicable PECR information, consent or exception requirements still have to be met.
When you follow a link to a separately hosted checkout, account portal or external service, that provider may also apply its own cookie, storage and privacy controls.
7. How to manage your choices
Withdrawing consent does not affect the lawfulness of processing that took place before withdrawal. If you object to storage being used under an exception that requires an objection mechanism, the relevant storage or access must stop for that purpose.
8. Production reviews and changes
We review storage and access technologies across uptimer.app and timer.uptimer.app when the product, analytics, payments, authentication, consent tooling or embedded services change.
Reviews include the behaviour of the marketing website and browser product in fresh sessions and across different consent choices, including local storage, account authentication, payment routes and analytics configuration where relevant.
A technology used for more than one purpose must be assessed against each purpose. A new non-exempt purpose is not covered simply because the same cookie, tag or storage key was already present for another reason.
We update this policy when providers, purposes, storage behaviour or the choices available to users change materially. A change can also require a fresh consent request or a new opportunity to object.
9. Contact
Email questions about cookies, local storage, UP Capture browser storage or consent to privacy@uptimer.app. The Privacy Policy explains personal-information processing, account data and privacy rights.