No certificate
This page describes privacy rights in plain language for thelogicloom and thelogicloom.site. It is not a GDPR certificate, not a seal, and not a legal opinion. thelogicloom does not claim that a regulator has approved the site. Readers in the European Economic Area, in the United Kingdom, in India, and elsewhere can read the same text. What the frontend can actually do today is limited by the fact that it stores enquiry data only on the reader's device.
Where a right needs a server copy to be meaningful, this page says so. Pretending to run a data-protection office that cannot see the data would be worse than a short honest note. The longer text exists so the rules of the practice are still written down for the day a live inbox and a real client file exist.
Legal name, street, phone, and mailbox are not published on this site. This page does not state a registered office. Rights requests should use the contact form, understanding that the form currently stores the request locally.
Rights that apply to a website enquiry
Access, on this build, means you can read your own local storage. thelogicloom cannot produce a server export of an enquiry that was never sent. If a mailbox is later connected, an access request should quote the TL- reference and the email address you used. The reply should include the enquiry text the mailbox holds, not a dump of unrelated client files.
Correction means fixing a name, an organisation, or a phone number that was wrong. On this build, correct it by clearing the record and sending a new one, or edit the stored value in your browser. On a future mailbox, a correction request should say what is wrong and what is right. thelogicloom should not invent the missing fact.
Deletion means removing the enquiry. Clear the local key now. For a future server copy, ask for deletion through the form once the mailbox exists. Some correspondence may need to be kept to show what was answered. That limit should be narrow, explained, and not used as a reason to keep a student list.
Objection and restriction, for a marketing email thelogicloom itself might one day send, mean you can say stop. This site does not send a newsletter today. There is no hidden subscribe box. If one is added, it needs its own untick and its own sentence on this page.
Rights that belong with the institution
A student, a parent, or a counsellor who wants to know how an institution handles an application should ask the institution. thelogicloom is not the university. If thelogicloom later processes lead records for a client, it does so as a service provider under a scope, for a named purpose such as measuring cost per qualified enquiry in ₹. The institution decides why the data exists. Requests about admission decisions, fee waivers, and academic records are not agency requests.
thelogicloom should not answer a student by opening the institution's lead file and freelancing a disclosure. The right path is to direct the person to the institution and to help the client respond if the scope includes that help. This protects the student from a half-informed answer.
Public case studies are marketing. They are not a student's file. If a case study accidentally includes a personal story that identifies a private individual, write through the contact form and ask for a correction. That is a content fix, and it should be treated urgently.
International readers and children
Opening the site from another country does not create an account. It does not move a database across a border, because this build has no enquiry database. A live file transfer of client material would be different, and the scope should say where the file is stored. This page does not claim an adequacy finding.
Children are not the audience of the form. Articles discuss how institutions recruit students, including applicants who are young. That editorial subject is not a request for a child to identify themselves. Do not enter a child's contact details into the form. thelogicloom does not knowingly build a children's marketing list.
Automated decision-making is not used on this website. There is no scoring of visitors. A future lead-qualification tool inside a client account would be a client system, described in that scope, with a human review path for admissions decisions. An enquiry should not be rejected by a silent model with no appeal inside the institution.
How this page stays aligned
The same commercial rules sit underneath the privacy language. Review of a draft is ten business days. One similar exchange is allowed in that window before publication. The first strategy note is due ten business days after kickoff when access is ready. Monthly cancellation notice is thirty days. Unused prepaid professional fees are refunded within fifteen business days of confirmation. The strategy conversation is ₹0. The sample audit illustration is ₹40,000. The sample monthly band starts at ₹75,000. Media accepted by a publisher is outside thelogicloom's refund. Those rules are about contracts. They are repeated so a privacy request is not answered with a contradictory fee story.
Security, vendors, and retention for a live system must be filled in when the system is real. Leaving a placeholder vendor name would be fiction. Fiction does not belong in a rights page.
To ask a question, use the contact form and start with the words privacy rights. Keep the TL- reference. Until an inbox is confirmed, assume the only copy of your question is the one in your browser.
A month in the work
People sometimes ask for a GDPR certificate. thelogicloom does not claim one. The calendar shows the rights we describe as a practice for enquiry data and, later, for client files, and it says plainly which of those rights can be exercised on this frontend today.
Week 1
Week one is an access request about an enquiry. On this frontend the only copy is in the reader's browser. thelogicloom cannot look it up on a server, because there is no server. A person who wants to see the note can read it in their own site data, or quote the TL- reference if a live inbox is later connected. We do not describe this as a certified access process.
Week 2
Week two is correction and deletion. The reader can clear the stored enquiry. If a live mailbox later holds a copy, a deletion request should be sent through the contact form and should say which reference to remove. This page does not promise a regulator timeline we cannot operate yet. It does say that a live practice should not keep enquiry text longer than needed to answer it and to keep a record of the reply.
Week 3
Week three is client files, which are different from website enquiries. Student records, counsellor notes, and lead exports belong to the institution. thelogicloom would handle them only under a written scope, as a service provider for a named task. People in those files should ask the institution first. thelogicloom will not claim to be the university's privacy office.
Week 4
Week four is international readers and children. The site can be opened from outside India. Enquiry text still stays on the device in this build. thelogicloom does not knowingly ask children to create accounts. The work is aimed at institutions and their adult teams. A student who finds a case study is reading public marketing commentary, not signing up for a service. None of this is a claim of GDPR certification, a seal, or an adequacy decision.
Questions this note is often asked
Are you the controller of a student's application?
No. The institution is the place a student should ask. thelogicloom, if involved at all, would be a service provider under a scope.
Can you export my enquiry from your server?
There is no server copy in this build. Export the local storage yourself if you need a file. A future mailbox export should be limited to your message.
Do you appoint a representative in the European Union?
Not on the strength of this static site. If a real processing operation aimed at people in the Union is built, that question has to be answered then. It is not answered by a badge.
How fast will you answer?
This frontend answers instantly with a local reference, and with no human in the loop. A live rights request should be handled promptly once an inbox exists. This page does not invent a one-day promise the operation cannot keep.
Does the ₹ fee illustration affect my privacy rights?
No. Money rules and privacy rules are aligned so they do not contradict, but a privacy request is not a bill and a bill is not a privacy request.
Operating note 1
The contact form remains the only public path. It validates a full name, a business or company name, a business email, a phone number, a service, a preferred date and time, and project requirements of at least twenty characters. Failed validation stays on the page. Successful validation writes local storage and shows a TL- reference. That behaviour is part of these terms because it is the behaviour a reader can test. This sentence is specific to the privacy rights page: apply the note to rights requests, without a claim of certification. If a later scope changes a number, the scope should say so in ₹ and in days, and this public page should be edited so the next reader does not inherit a contradiction.