This policy explains what personal data CosmosPM Ltd collects when you use LogicReader, why we collect it, who we share it with, and the rights you have over it.

1. Who we are

CosmosPM Ltd (company number 16886156), registered in England and Wales.

Registered office: C/O The Accountancy Partnership, Suite 5, 5th Floor, City Reach, 5 Greenwich View Place, London E14 9NN, United Kingdom.

ICO registration: ZC143102.

2. Two roles: controller and processor

CosmosPM acts in two different capacities depending on the type of data, and different rules apply to each.

3. What data we collect

• Registration data: name, email address, country and job role, collected when you register and confirmed through double opt-in email verification. We also ask how many people work in your organisation and how you heard about LogicReader. The job role and these two answers are required, and the form cannot be sent without them; you can choose “I do not know” or “I do not remember”. We also ask what software you use for your job. You tick one or more programs from a list, or you tick “None of these”. This answer is optional. We also ask what you are interested in. You tick one or more topics from a list, for example planning, claims and delay analysis, or training. This answer is optional. We keep these answers as choices from a list, not as free text, on your account, and we delete them when your account is deleted. We use them to understand who uses LogicReader, how they find it and which programs and topics matter to them, so that we can plan the product.
• Account credentials: your login password (stored in hashed form) and related account security data.
• Uploaded schedule files: XER or CSV project schedule files you choose to upload.
• Technical data: IP address, browser type, and security logs, collected automatically by our web server to keep the service secure and working.
• Product feedback: the message, rating, category, screenshots and diagnostic log you choose to send through the in-app feedback form, together with your browser family — the browser name, its major version and your operating system, for example “Chrome 128 / Windows” — which we keep so that we can reproduce a bug. We do not store your IP address with your feedback, and we do not store the full browser identification string.
• Early-access requests: if you ask for early access using the early-access form on logicreader.io before registering, we collect your email address and, if you choose the In-house offer, your company and team size. The form requires your email address and how you heard about LogicReader; an In-house request also needs your company and team size. (Until 12 October 2026 the form also asked for your name, role, organisation size, a message, the topics you are interested in and the software you use. We keep the answers that people gave then; our staff console shows them only as counts, and the e-mail to the owner showed them with the name and address. Those questions are now asked when you create an account: see Registration data.) We also record the date, the page you came from, your IP address and your browser’s identification details; we use the IP address and browser details only to detect spam. We also ask which offer you are interested in (Free, LR-Plus, In-house or Not sure yet), and we record your choice and, for In-house, the team size you choose. We also ask how you heard about LogicReader. This answer is required, and the form cannot be sent without it; you can choose “I do not remember”. We keep your answer as a choice from a list, not as free text. Your browser also measures how long you take from opening the “how did you hear” list to choosing an answer. Our server receives that time, puts it in one band (under 2 seconds, 2 to 10 seconds, or over 10 seconds), and does not keep the exact time. Nothing is stored on your device. We also record which version of our software took your first request. We use these answers to understand who asks for LogicReader, how they find it, and whether the answers can be trusted. Our staff console shows the organisation size and how you heard only as counts; it lists the offer you asked about with your request. The e-mail to the owner (see below) does show them with your name and address. We also ask, optionally: who it is for, how you work, your role. Each answer is a choice from a list, and you can leave it empty. Our staff console shows these answers only as counts; the e-mail to the owner shows them with your name and address. When you register your interest, we send you two emails: a short thank-you email, and an email with a link to confirm your address. We send at most two reminders of the confirmation email. The thank-you email goes through our email provider, Brevo. It has no links. We read from Brevo whether it was delivered, or whether your address does not exist. If your address does not exist, we send it no more email. Brevo adds a tracking image to the email that it sends; we do not use it to see who opened an email. The confirmation email and its reminders go from our Microsoft 365 mailbox. They have no tracking image and no tracking links. If that mailbox cannot send, Brevo sends the email instead. Brevo then adds a tracking image and changes the links. We do not use them to see who opened an email. Once you confirm, we email you once when public sign-up (or the offer you asked about: In-house or a presentation) is ready. We send that email because you asked for it, to answer your request. A second, separate box asks for occasional updates about LogicReader; it is unticked and optional. We record what you asked for, for which offer, and when. The confirmation email also has a link that stops all early-access email to you. We send you the news you asked for only after you click the confirmation link; we record when you confirmed. To limit these emails, we also record the network address the form came from. Every such email carries an unsubscribe link; in the thank-you email your mail program shows it, because the email text has no links. If you use it, we record that and when, and we stop both.
• Contact form: if you write to us through the contact form on logicreader.io, we collect your email address and your message, whether you ask for a pilot, and, if you choose to give them, your name and company. We also record the date, the page you came from, your IP address and your browser’s identification details, and we use the IP address and browser details only to detect spam. We also ask how many people work in your organisation. The answer is required, and “I do not know” is a choice. We keep it as a choice from a list, with your message.
• E-mail to the owner: when you send an early-access request or a contact message, our system also sends one e-mail about it to the owner of CosmosPM, at a CosmosPM Microsoft 365 mailbox. It carries the date and time, which form you used, your e-mail address, whether you have confirmed an e-mail box, the name, company, role, message and answers you gave, the e-mail boxes you ticked, the page you came from, which version of our software took the request, and a waiting-list number. It does not carry your IP address or browser details. It is for the owner only. It is not marketing. If you send a second request from an address that is already on our list, this e-mail can hold details that we do not store on the list. When you create an account, our system also sends one e-mail about the new account to the same mailbox. It carries the date and time, how you created the account, your name if you gave it, your e-mail address, your country if you gave it, your role, and your answers to the registration questions. It is not marketing.
• Product steps: for each account we record which steps in LogicReader it has reached — for example, opening your own project room, exporting an XER file, opening the upgrade dialog, or becoming a paying customer — and the date it first happened. We also record when you signed up, the first time you imported a real schedule (an XER, Excel or GraphML file — not a sample), and the first time you opened an analysis view, for example Compare or the Schedule calculation. From these steps and from the days on which you used LogicReader, we count how many new accounts reach these first steps within 7 days, and how many accounts come back in the weeks after they sign up. We record no schedule content, no project name and no IP address. We use it to see where people continue or stop, so that we can improve the product. The same opt-out as our usage analytics applies (section 10): if you opt out, we stop recording new steps and do not count earlier ones. We keep it until you delete your account, and we delete it with your account.
• Founding users: if we invite you to be a founding user, we mark your account and record the end date of that period. We use the mark only to look at founding users as their own group in our counts.
• Cancellation: when you cancel a subscription, we ask you one optional question: why you stopped. You choose one answer from a list and can add your own words; you can also skip the question. We keep your answer on your account. A few minutes after you cancel, the founder of CosmosPM sends you one short e-mail that asks for a few words about why you stopped. We send it at most once in 30 days. It is not marketing, and you do not have to answer.
• Support and other correspondence: messages you send us by e-mail or other channels, for example support requests.

We do not seek to collect any special-category data (such as health, religious belief, or racial or ethnic origin data) and ask that you do not include such data in your account profile, an early-access request or a contact message.

Providing your name, email, and country is necessary to enter the contract for the Service — without it we cannot create your account. The form also requires your job role, your organisation size and how you heard about LogicReader; the questions about software and topics are optional.

4. Why we process your data (lawful bases)

• Contract: to create and run your account and provide the LogicReader service you have signed up for.
• Consent: for marketing communications, only if you opt in — when you register, or with the updates box on the early-access form, confirmed with the link we email you. You can withdraw this consent at any time: open Email preferences in your account menu, or use the unsubscribe link that every marketing email carries. Service email about your own account (a licence key, a password reset) is not marketing and is not affected.
• Legitimate interests: to keep the service secure, to improve it, and to understand how the product is used (with an opt-out available — see section 10). This covers the usage analytics, which use a pseudonymous identifier, and the product steps in section 3, which are tied to your account. We also rely on it to answer early-access requests and contact-form messages. We also rely on it for the questions on those two forms, for the time band, and for the e-mail to the owner. We also use your address to check that it can receive email, and we stop sending to an address that does not exist. Our interests are: to know who asks for LogicReader and how they find it, so that we can plan the product and where we tell people about it; to see whether the answers can be trusted (a very fast answer can mean the person did not read the list); and to see each request quickly so that we can answer it. You can object at any time (section 9). This basis covers account, technical and usage data, and the product feedback you send us through the in-app form, including our review of it in our Microsoft 365 mailbox (see section 5). We do not analyse or use the content of your uploaded schedule files for our own purposes — see section 2(b). It also covers the optional question when you cancel a subscription and the one e-mail from the founder that follows it (section 3): our interest is to learn why people stop using LogicReader, so that we can improve it.
• Legal obligation: to meet our obligations to HMRC and the ICO, and other legal requirements.

5. AI processing — your own AI provider

AI-assisted features are optional and run only when you invoke them. AI is never used to compute your schedule’s dates, float, or critical path — LogicReader’s own deterministic engine always performs that calculation. Some AI features create or classify schedule content at your explicit request — for example, the AI Draft Builder, which drafts activities and links from a scope document, and the logic-type classifier, which suggests a logic type for a relationship. Content added or classified by AI is always marked as AI-sourced and remains subject to your review, edit, or removal.

On the hosted service, LogicReader does not supply an AI service. To use an AI feature you connect your own AI provider account: you choose the provider, paste your own key, and pay that provider directly. The choices in the app include Anthropic (Claude), OpenAI, Mistral, Azure, and a model you run yourself, such as Ollama or LM Studio. CosmosPM does not choose your provider and is not its customer for this purpose.

When you start an AI feature, the relevant schedule data, any scope document you supply, and your prompt are sent to the provider you chose, and to no other. This means:

• the request is made by the LogicReader server, not by your browser directly, so any endpoint you name must be reachable from that server. On the hosted service this means “local” or “self-hosted” refers to a model reachable from our UK server, not necessarily one running on your own laptop; if you run LogicReader as a desktop application, the server is your own machine, and “local” then does mean your machine;
• your key is kept in your browser. It travels to our server in one request header with each AI request and is used for that request only. We do not log it, write it to disk or keep it;
• the request and the response pass through our server so that we can relay them. We do not keep their content. We record only that a call happened and its size, not what it said. Content you choose to add to your schedule is saved in your workspace as usual;
• we do not remove or mask personal names in your schedule content before sending — they go to your provider exactly as written;
• CosmosPM is not a party to that provider’s terms or data processing arrangements, has not reviewed its security, and is not responsible for how it handles your data. You (or your organisation, as controller of any personal data in your schedule content — see section 2(b)) are responsible for having your own lawful basis and arrangement with that provider. The international-transfer safeguards described in section 11 do not extend to a provider you choose yourself;
• you are told before an AI feature runs, so you can choose whether to use it; and
• if you name a provider or endpoint that the request cannot reach — for example, because a required key is missing — LogicReader refuses the request rather than sending your data to any other provider.

If you choose Anthropic. You use your own Anthropic account under Anthropic’s terms with you. For UK and EEA customers the contracting company is Anthropic Ireland Limited, and Anthropic may process the data outside the UK, including in the United States. At the time of writing, Anthropic states that it deletes API inputs and outputs within 30 days, and its commercial terms say it does not train its models on API data. Check your account settings and Anthropic’s current terms. Our own agreement with Anthropic does not cover requests made with your key.

If CosmosPM later offers an AI service that runs on its own account, we will name the provider in this policy before that service is used.

When you send feedback through the in-app feedback form, we send the full report — your message, rating and category, the page you were on, the diagnostic log if you attached it, and the screenshots you ticked — by e-mail to our own Microsoft 365 mailbox. Our team reads it there, with the help of Microsoft 365 Copilot. The e-mail does not contain your IP address, your browser details or your user name. We do not send feedback to any AI provider ourselves; Microsoft 365 Copilot processes it as part of our Microsoft 365 service, under our agreement with Microsoft (section 6).

6. Who we share your data with

Sub-processors

We use a small number of carefully chosen sub-processors to run LogicReader. They process data on our behalf. We have signed data processing agreements with Hostinger, Microsoft and PostHog. We have not yet signed a separate data processing agreement with Brevo: Brevo receives only the email data described in the table below: the e-mails it sends for us and, only if you opt in, a marketing contact record, and PostHog receives only pseudonymous usage events and no schedule content. Your own AI provider is not one of our sub-processors: you choose it and you contract with it (section 5).

Independent controllers

When payment is enabled, Paddle.com Market Ltd sells our paid plans as our reseller and Merchant of Record. Paddle is not our sub-processor. When you buy a paid plan, Paddle processes your order and payment data as an independent controller, under its own privacy notice and its own terms with you as the buyer. Paddle never receives your schedule data.

7. How long we keep your data

• Account data: kept while your account is active. On a deletion request we delete your account and your personal data from the live service without undue delay. Copies can remain in our backups after that. We use backups only to restore the service.
• Uploaded schedule data: kept until you delete it, or for 90 days after your account is closed.
• Pending registrations: unverified sign-ups are kept only for a short, limited period before removal.
• Early-access requests: kept for 24 months from your last contact with us, then deleted. If you confirmed your address and have not unsubscribed, the last day you confirmed counts as a contact. You can ask us to delete them sooner. Your answers to the questions are kept with the request and deleted with it. The e-mail we send to the owner about your request or your new account is kept in the owner’s mailbox for 24 months after it was sent, then deleted. If you ask us to delete your request or your account, we also delete that e-mail.
• Early-access confirmation emails: a copy of each confirmation email and reminder that we send stays in our Microsoft 365 mailbox for about three months, then it is deleted.
• Early-access delivery state: whether your address was delivered or was a hard bounce (from Brevo’s delivery events) is kept with your request and deleted with it.
• Contact-form messages: kept for 24 months from your last contact with us, then deleted. You can ask us to delete them sooner. The e-mail we send to the owner about your message follows the same rule.
• Product feedback: the message, screenshots, diagnostic log and browser family (browser, major version and operating system) you send us through the in-app feedback form are kept for up to 3 months, then deleted — in the app and in our feedback mailbox. No IP address is stored with your feedback. You can ask us to delete them earlier at any time.
• Support and other correspondence: kept for up to 6 years, in line with HMRC record-keeping requirements.
• Security logs: kept on a rolling 90-day basis.
• Product steps, the founding-user mark and your cancellation answer: kept while your account exists, and deleted with your account.

8. How we protect your data

We apply the following technical and organisational measures to protect your personal data:

• data is encrypted in transit using TLS;
• passwords are stored only in hashed form, never in plain text;
• access to personal data is restricted to authorised personnel who need it to operate the Service;
• the Service runs on a single production server hosted in the United Kingdom;
• we take regular backups, held encrypted; and
• no card data touches our servers — payments, when launched, will use a hosted payment provider.

These measures are kept under review as the Service develops. We do not hold any security certifications at this stage.

9. Your rights

Under UK GDPR, you have the right to:

1. be informed about how your data is used;
2. access the personal data we hold about you;
3. have inaccurate data corrected;
4. have your data erased, in certain circumstances;
5. restrict how your data is processed, in certain circumstances;
6. receive your data in a portable format;
7. object to processing based on legitimate interests or for direct marketing;
8. withdraw consent at any time, where we rely on your consent (e.g. marketing), without affecting the lawfulness of earlier processing — for marketing email, through Email preferences in your account menu or the unsubscribe link in the email itself; and
9. not be subject to decisions based solely on automated processing that have a legal or similarly significant effect on you.

To exercise any of these rights, email privacy@cosmospm.com. We aim to respond within one calendar month.

If you are not satisfied with how we have handled your data, you can complain to the UK's data protection regulator:

10. Cookies and local storage

LogicReader uses only strictly necessary cookies — specifically the lr_session authentication cookie, which keeps you signed in — and local browser storage to remember your interface preferences. We do not use advertising or tracking cookies. See our Cookie Policy for details, including how to opt out of the pseudonymous usage telemetry active on this service.

11. International data transfers

Some of our sub-processors are based outside the UK. Where we transfer your data outside the UK, we rely on EU Standard Contractual Clauses together with the UK International Data Transfer Addendum, or equivalent safeguards as set out in the sub-processor table in section 6.

The Service is hosted in the United Kingdom. If you access it from outside the UK (for example from India, the United Arab Emirates, or the United States), the personal data and schedule content you provide are transferred to, and processed on, our server in the United Kingdom, and — where you use an AI feature — to the AI provider you choose, wherever it is located (see section 5). By using the Service from your location you understand that this cross-border processing takes place. This free beta is intended for sample or anonymised schedules, not confidential live project data.

12. Children

LogicReader is a professional tool intended for use by scheduling and project management professionals. It is not intended for, and we do not knowingly collect data from, anyone under 18 years of age.

13. Beta status

LogicReader is currently offered as a free beta service. As the product moves through development, data held in beta accounts may be deleted when the beta period ends. We will give notice before this happens.

14. Changes to this policy

We may update this policy from time to time. If we make a material change, we will notify you in-app or by email. The version number and effective date at the top of this page always show the current version.