T.I.M · Legal information
Cookie Policy
Cookies, app storage and your choices
This policy explains cookies and similar technologies used to deliver the T.I.M website, open-beta accounts, live request functions and checkout, and how optional technologies are controlled.
On this page
1. Operator and scope
This policy applies to the website, legal pages and open-beta services operated by Jonathan Johnson trading as T.I.M — Time Is Money. Contact access@tim247.app about cookies, device storage or privacy choices.
Read it with our Privacy Policy, which explains personal-information use, recipients, international processing, retention and rights, and our Terms & Conditions.
2. What cookies and similar technologies do
A cookie is a small item of data a website asks a browser to store and return with relevant requests. Local storage can retain information until it is removed; session storage generally lasts for a browsing session. Apps can use equivalent secure storage, device identifiers, software development kits, pixels and similar technologies.
Some technologies authenticate an account, preserve a request state, remember a choice, prevent fraud or complete a payment. Others measure use or support advertising. An ordinary request for a page, image, API response or email resource can disclose an IP address and request information without placing a cookie.
3. Current use by service
| Service | Current position |
|---|---|
| Legal pages | These Terms, Privacy and Cookie pages do not themselves set cookies, write to local or session storage, or load optional analytics, advertising tags, external fonts or tracking pixels. The logo is requested from T.I.M's own website. |
| Public website | Netlify delivers pages, handles forms and may process necessary security, network and anti-abuse information. Company searches are sent through a T.I.M server-side function to obtain the requested register result. |
| Beta app and portals | Base44 platform services may use cookies or app storage required for sign-in, session continuity, account security, navigation, submitted request state and the function the user chooses to operate. |
| Payments | The payment provider shown at checkout may use necessary cookies or equivalent technology to authenticate the client, prevent fraud and maintain the payment state used to place the full platform-fee authorisation at submission, keep or renew the hold during routing, capture it on completion, partially capture and refund it after client cancellation, or release it after network decline or rejection. This begins when the user opens or uses that checkout. |
| External images and links | Background images on parts of the public website are requested from images.unsplash.com, which receives technical request information. Following an external link or app-store link brings the user within that destination's own arrangements. |
4. Necessary and requested functions
Storage or access may be used without a consent banner where it is strictly necessary to transmit a communication or provide an online service the user expressly requests. Depending on the function, this can include:
- authentication, session continuity, account recovery and security;
- load balancing, network delivery, fraud prevention and protection against abuse;
- preserving information during a multi-step application, request or checkout;
- remembering a privacy or accessibility choice requested by the user; and
- placing, maintaining, capturing, partially capturing, refunding or releasing a payment authorisation the user initiates.
A provider-supplied tool is not necessary merely because it is available. The necessity depends on the purpose and whether the requested function can work without it.
5. Optional technologies and consent
Optional analytics, advertising, cross-service profiling, social-media embeds and similar technologies must remain inactive until a valid consent is obtained where consent is required. Optional choices must be clearly described, unbundled and not preselected. Refusal must be available without consenting to unrelated tracking.
Browsing, scrolling, submitting an application, approving a paid request or accepting the Terms & Conditions does not give cookie consent. If optional technologies are introduced, the relevant control will identify their purpose, provider and duration before activation and will allow consent to be withdrawn as easily as it was given.
6. Duration and cookie details
Session technologies expire when the relevant session ends. Persistent authentication, security, preference or checkout technologies expire according to the provider's configured period or earlier when removed. Local storage can remain until the service or user deletes it.
Because cookies visible to a user depend on the domain, account state and function opened, the browser's site-data panel provides the exact live cookie name, domain and expiry for that session. T.I.M will keep the information presented in any consent or privacy-settings control aligned with the optional technologies actually deployed. This policy does not authorise an unnamed optional tracker.
7. Managing and withdrawing choices
You can inspect, block or remove cookies and storage through browser or device settings, usually for an individual site as well as across sites. Blocking necessary storage can sign you out, interrupt a request or checkout, or require information to be entered again.
Where a T.I.M consent or privacy-settings control is available, use it to change or withdraw optional choices. Withdrawal does not affect earlier lawful processing. You may also clear site data in the browser. Emailing us is not an immediate technical blocker for a third-party script, but we will address the underlying configuration or rights request as applicable.
Deleting device storage does not delete information already submitted to a server. Use the rights routes in the Privacy Policy for account, application or request records.
8. Email, app stores and third parties
Email providers and clients process technical information when delivering or displaying messages, including externally loaded content. You can control external-image loading in your email client. We do not treat an administrative acknowledgement as consent to unrelated email tracking.
App stores, suppliers, maps, registers, payment services and other destinations have their own cookie and privacy arrangements when opened. A link does not give T.I.M control over their storage. Information supplied directly inside the T.I.M platform remains subject to the Privacy Policy.
9. Updates and contact
We review this policy when the website, beta app, checkout, providers or technology arrangements change. Material changes requiring a new consent choice are addressed before the affected optional technology is enabled. The effective date and version appear above.
For questions, choices or concerns, email access@tim247.app or write to Jonathan Johnson trading as T.I.M at the address below.