Many Hats. by Loom & Logic

MANY HATS BY LOOM & LOGIC

Privacy Policy

Draft updated 20 October 2026 · Awaiting final publication approval

Review before public promotion. This draft incorporates the owner's approved directions. Final publication remains on hold while the processing assessments, provider checks and incorporation preparations are completed. The current operator remains the individual named below.

Who operates Many Hats

Many Hats by Loom & Logic is operated by Aron Edward Owen, trading as Loom Logic, based at 1 Plas Dyffryn, Parc y Bryn, Aberystwyth, SY23 2DL. The operator is the contact responsible for decisions about the personal information used by this service. Privacy enquiries and requests can be sent to aron.e.owen@gmail.com.

No registered-company status or company number is asserted here.

Information the application collects

  • Google sign-in: your name, email address, whether Google has verified that email, and Google’s stable account identifier, linked to an internal Many Hats user ID. Account creation and update timestamps are also stored. Google profile pictures and Google access, refresh and ID tokens are not retained in the application database.
  • Your workspace: hat names, task titles, optional plain-text notes, each task’s hat and column, ordering information and completion timestamps where recorded.
  • Sessions and sign-in checks: application session identifiers/tokens and expiry timestamps, and temporary verification records needed to complete Google sign-in securely.
  • Technical requests: requests to the service involve information such as your IP address and browser/request headers. The application uses a trusted client IP for basic authentication rate limiting; it does not retain your IP address or browser user-agent in application session records. Infrastructure providers may process their own technical and security information.

Use Many Hats for ordinary task management. Do not enter passwords, confidential business material or sensitive personal information, including health, financial or identity-document details. Keep task notes appropriate to this service and avoid adding other people’s personal information unnecessarily.

Why this information is used and the lawful bases

Essential service delivery — contractual necessity: the account details needed to identify you, your hats, tasks and notes, and session information are used to provide the private workspace you request under the Terms of Use. This covers signing in, saving and displaying your workspace, and carrying out your edit and deletion instructions. Optional notes are processed only when you choose to add them. This basis does not cover advertising or unrelated uses of your information.

Proportionate security — legitimate interests: the operator has an interest in protecting users' workspaces and keeping the service available. Limited technical information is used for sign-in rate limiting, detecting invalid sign-in attempts and investigating reported misuse. The assessment considers necessity, less intrusive alternatives and users' rights, including the interests of 16- and 17-year-olds. Session IP addresses, browser user-agents and Google tokens are not retained in the application database; routine task-content logging is not enabled.

Your right to object: you can object to processing based on legitimate interests by contacting the operator. We will consider your circumstances and stop that processing unless applicable law permits it to continue. Security checks needed to protect an account may affect whether the service can safely be provided. Visiting or signing in is not consent to unrelated processing. The documented assessments and the application of these bases to the intended audience remain subject to final review.

Google and Cloudflare

Google manages your Google account and authentication under its own terms and Privacy Policy. You choose an account on Google's site; Many Hats never receives your Google password. The operator is responsible for the account information received by Many Hats. Google's sign-in developer terms and user-data policy apply to the integration; this is not a Google-hosted task database.

Cloudflare hosts Many Hats through Workers and stores application records in D1, processing hosted personal data on the operator's behalf. Its standard self-service agreement incorporates its Data Processing Addendum. Cloudflare also describes its own account, technical and security processing in its Privacy Policy.

Provider processing can take place outside the UK. We do not promise UK-only storage. Cloudflare's published DPA contains international-transfer provisions, including UK transfer safeguards where applicable. Provider agreement details and the applicable transfer arrangements are recorded separately for final review; this draft does not certify a particular account-specific agreement or guarantee every processing location. Contact the operator for information about the safeguards relevant to your data.

Necessary cookies and technical storage

Many Hats uses necessary session and sign-in state cookies to authenticate requests and complete the Google sign-in flow. Application session cookies are signed, HttpOnly, SameSite=Lax and Secure on production HTTPS. Sessions are configured to expire after 30 days and may be refreshed while the service is used; signing out revokes the current session.

Hat selection and the selected Done page may be recorded in the page URL. The service uses local font files and adds no advertising or product-analytics scripts. Google and Cloudflare have their own technical processing. No advertising consent system is included.

On production, __Secure-many-hats.session_token identifies your session and lasts up to 30 days, renewed during use. The sign-in check cookie __Secure-many-hats.state lasts five minutes. Both are host-only, HttpOnly, Secure and SameSite=Lax. Temporary database verification records expire after ten minutes; expiry does not guarantee immediate physical erasure. The application does not use localStorage or sessionStorage. These cookies are used only for the requested sign-in and its security, not tracking. The necessity and duration assessment is documented for final review.

Deletion, retention and backups

The current application keeps account and workspace records until they are deleted; it does not implement automatic deletion for inactive accounts. You can delete individual tasks or hats in your workspace. The sidebar’s Delete account action requires confirmation and removes that account’s live profile, Google account mapping, application sessions, hats and tasks. It does not delete your Google account. These application deletion actions cannot be undone through the normal interface.

Standard Cloudflare D1 Free Time Travel is the ongoing recovery arrangement. It provides a rolling recovery window of up to seven days for the database; it is not an unlimited archive or a guarantee that every deleted item can be recovered. Restoring the whole database can bring back accounts, tasks or sessions deleted after the chosen recovery point. A live deletion therefore does not immediately remove data from all recovery history.

Before reopening a restored service, the operator must reconcile previously honoured deletion requests and remove restored records that should remain deleted, and revoke restored sessions. Historical local migration/development copies are reviewed separately; any still needed for rollback are access restricted. No paid backup service or additional backup infrastructure is used. No fixed erasure deadline for retained historical copies is asserted.

Session and temporary verification records have the expiry periods described above. Their expiry does not mean a scheduled physical purge takes place at that moment. There is no automated inactive-account deletion schedule. Any necessary records for handling a privacy request are limited to what is needed to fulfil and evidence it; a fixed operational retention schedule has not been adopted in this draft.

The Google account details needed for sign-in are provided by Google when you choose to authenticate. Without those details, Many Hats cannot create or authenticate your workspace. Tasks and notes come from you; notes are optional. The application does not make automated eligibility or other decisions with legal or similarly significant effects about you.

Your choices, requests and complaints

You can edit or delete your hats and tasks, and delete your account after confirmation. Depending on the circumstances, you may also request access, correction, erasure, restriction or a portable copy of your information and object to legitimate-interest processing. Contact aron.e.owen@gmail.com for help or to raise a concern. No special form or legal wording is required; this email route does not restrict other valid ways of making a request.

We will check your identity only as far as reasonably necessary, clarify the request if needed, and respond without undue delay within applicable UK GDPR timescales — normally one month. If a lawful extension or exception applies, we will explain it and your options. Requests are normally free. We will not disclose another user's information in responding. There is no separate in-app export feature; you can request your data from the operator.

You can complain to the Information Commissioner's Office if you are unhappy about how your personal information is handled. You do not have to give up that right to use the service. The ICO provides more information about your rights.

Our intended audience

Many Hats is intended for people aged 16 and over, including 16- and 17-year-olds. We do not request identity documents, dates of birth or location for age verification. The privacy safeguards apply to every account. Keep notes to ordinary tasks, sign out on a shared device, and contact the operator if you need help with your information. The owner is reviewing the service against the Children's Code because under-18s are within the intended audience; a 16+ statement is not a claim that those requirements disappear.

Changes and review

We will explain material changes in advance where reasonably practical, using appropriate direct notice to affected account holders. Minor corrections may be published directly with an updated date. Urgent legal or security updates may take effect sooner when justified, with an explanation as soon as practical. No promotional mailing list or new notification feature is added.

These pages remain drafts pending final approval. Incorporation is planned, but no limited company or company-level ICO registration is asserted to exist. The current individual operator remains responsible unless and until a properly documented transition takes place. Any change of controller will be assessed and communicated appropriately. See the Terms of Use.