Privacy
What we keep about you.
What LLM Monster collects, why, who processes it and how long it stays. Last updated 15 November 2026.

The short version
- Tevelis Limited in Cyprus runs LLM Monster and decides what happens to your data. Write to help@llmmonster.com about any of it; a person answers.
- We keep what the service needs and say below for how long. We do not sell personal data and run no advertising trackers. Google Analytics counts visits to our marketing pages only if you accept its cookies, and never runs on the pages that hold your scans, checks or reports.
- Search Console and Google Analytics data you connect is shown only to your organisation and is never sold, never used for advertising and never used to train AI models. LLM Monster's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
- Our cartoon characters' email replies are written by an AI system, and each reply says so.
- You can delete your account yourself, and ask us for a copy of your data or to delete it at any time.
Who we are
LLM Monster is run by Tevelis Limited, a private limited company registered in Cyprus (registration number HE 492969), Adonis, Aphrodite Hills, Kouklia 8509, Cyprus. For the personal data on this page we are the controller. Write to help@llmmonster.com about anything here; privacy requests are answered by a person. We have not appointed a data protection officer, because the law does not require one for the work we do.
When a business customer has us scan its websites, connect its Google properties, or (for an agency) collect leads with our widget, we process the personal data in that work for the customer, as its processor. Then the customer's own privacy notice applies, and our data processing addendum sets out what we do for it.
What we collect
Your account
When you create an account we receive your email address, the name you give and whether you confirmed the email. Sign-in runs on our own Keycloak server at auth.llmmonster.com, which stores your password as a one-way hash; we never see the password itself. To stop bots from making accounts, the sign-up page runs Google reCAPTCHA (see Cookies and browser storage), and we keep the network part of the address you signed up from (the first three parts of an IPv4 address, or the first half of an IPv6 one) with the record of the sign-up. Each sign-in session keeps the IP address it started from for its 30 days, so you and we can spot a session that is not yours.
If someone in your organisation invites you, we keep your email address, the role and who invited you, until you accept or the invite runs out after 7 days.
You can delete your account yourself: Account, Settings, Delete your account. The page lists what goes and what stays before you confirm. Your sign-in account, sessions, settings, site proofs, the contact record from your free scans, and the records of Munch's letter and the monthly AI check email for the same address are deleted at once, and every Search Console and Google Analytics connection you made is disconnected as described under Search Console data. You leave every organisation; one with no other member is deleted with its sites and reports. In an organisation that has other members, the reports stay with the organisation and your name and address are taken off them. Orders and paid subscriptions stay, with the name and email address of the account that placed them, for as long as tax and accounting law requires, and nobody can sign in with that record. A running subscription has to be cancelled first. The AI checks and AI Visibility Audits sent to your address, invitations to it and its messages from the contact page are deleted too. Mail to our characters is kept by a keyed hash of the address, not by account; write to help@llmmonster.com to have it deleted. Copies in the backups of the server that holds accounts are gone within 7 months.
The free scan
The website address you type and what the scanner reads on that site's public pages. To keep scans fair we count them per network (the first three parts of an IPv4 address, or the first half of an IPv6 one): 8 an hour and 24 a day. The network is kept with the scan, and the scan service's log keeps the full IP address for a short time (see How long we keep it).
Before a scan runs you show that the site is yours: a code we email to an address at the site's domain, a DNS record, a file on the site, or, when you are signed in, a Search Console property of the domain that your Google account can read (see Search Console data). With the email way we keep, as a lead, the address, the domain, when you confirmed it, the version of the consent line shown under the email field and the campaign tags of the link you arrived by (such as utm_source). With the other ways we keep the domain and when it was confirmed. If you are signed in, the confirmation is linked to your account so the next scan of that domain skips the step. Your browser keeps a list of your last 10 scans, with the email you typed, for 30 days, so you can go back to them; nobody else can read it.
The free AI check and the AI Visibility Audit
The website, the email address you confirm, what you fill in or correct about the business (what it does, where, who buys, rivals, questions), the answers the AI assistants gave, and our analysis of them. Your browser keeps your check in progress, with that email address, until you clear it.
To keep the free lookups to one per person, your browser keeps a random id (a cookie and the same id in its storage, for a year) and works out a short hash of its basic settings (browser version, languages, screen size, time zone and the like; no canvas or graphics card readings). Only hashes leave your browser. Our server keeps a keyed hash of the id, of that browser hash and of your network (as for the free scan), with the websites looked up, for a year. We look up the country of your IP address in DB-IP's free country list on our own server, to ask the assistants from the right market and because the free check is not offered everywhere; we do not keep the IP address for this.
If you ask for the monthly email after a free AI check, we keep your email address, the website, your time zone as your browser reports it, when you asked, when you confirmed the code we sent, and the version and text of the line you ticked. That is the record of your consent, and it is the only legal basis for these emails. Each one has a link to stop them, and mail programs that offer a one-click unsubscribe use the same link. We use the data only to send that one email a month, with a link to the check and a short note about our paid products, and we note which note each email carried so the next one is different.
Munch's letter and the field guide
If you sign up for our newsletter (the form at the foot of our pages and on the newsletter page), we keep your email address, the page you signed up on, the country your connection came from, when you asked, when you confirmed, and the version and text of the line shown under the field. The country is looked up from your IP address in a copy of DB-IP's free country list kept on our own server (IP Geolocation by DB-IP); we do not keep the IP address itself for this. We use the data to send you the field guide and a letter at most once a month about AI answers and LLM Monster, and to count sign-ups by page and country.
Your consent is the only legal basis for these emails. We send nothing but the confirmation link until you click it; an address that is never confirmed is deleted after 2 days. Every letter has an unsubscribe link, and mail programs that offer a one-click unsubscribe use it too; you can also reply "stop" or write to help@llmmonster.com, and a person takes you off the list. Withdrawing consent does not affect the emails sent before. The field guide's link keeps working after you leave.
The Full Meal early-access list
Until November 2026 the home page had a form to join a waiting list for the Full Meal. For the people who joined it we keep the email address, the domain and when they joined, to tell them the Full Meal is open. We send nothing else to that address because of the list, and the form is gone, so no one new is added.
Agency features
Agencies on an agency plan can scan a prospect's website without the prospect's permission (public pages only), and can put our lead widget on their own website. When you use an agency's widget, we receive the website and email address you type and when, and the agency gets them as a lead; we also keep a keyed hash of your IP address against floods. For that data the agency is the controller and we act for it (see the data processing addendum); ask the agency, or write to help@llmmonster.com, to have it deleted.
The guestbook and the suggestion box
If you sign the guestbook or post an idea in the suggestion box, we keep what you type (for the guestbook a name, where you write from if you say, and the message; for the suggestion box the idea and a name if you give one), the time, and a keyed hash of your network address (the first three parts of an IPv4 address, or the first half of an IPv6 one) to stop floods of notes. We do not ask for an email address. A person reads every note before anything is shown. Approved guestbook entries are public on the guestbook page with the name and place you gave and the time you signed; ideas are never published.
When you sign, you get a link that deletes your note at once. You can also write to help@llmmonster.com with the name and the day, and we delete it. The legal basis for showing your entry is your consent, which you withdraw by deleting it; for the spam checks it is our legitimate interest in a guestbook free of spam. The complaints box on the complaints page sends nothing: what you type there stays in your browser.
Mail to our cartoon characters
Our cartoon characters have their own addresses, such as munch@llmmonster.com. Their replies are written by an AI system in the character's voice, and each reply says so at the end and carries a machine-readable mark that it is AI-generated. Questions about your data get a fixed answer and go only to a person. Anything about an order, a payment, a complaint or a legal matter is copied to help@llmmonster.com, where a person picks it up; you can write there at any time.
When you write to a character, we first check that the mail comes from a person and not from a newsletter or an automatic reply. Then the text, the subject and the name you wrote under go to the AI providers below to judge the mail (is it a person, is it a real question, is it rude) and to write the reply; for the first check, the labelling provider also gets the domain of your address. We do not send your address itself, but text you quote or sign with goes as you wrote it, addresses included.
So that a character can follow a long conversation and the characters know who they have talked to, we keep a record of each exchange: the text and subject of your mails and of our replies, their dates and message ids, those judgments, and a keyed hash of your address with a random id in place of the address itself. The text, subjects and message ids are deleted after 180 days; the rest after 2 years without a new mail from you. A conversation that goes on and on, or is mostly insults, gets short fixed answers and then none; other characters can see that too. The mail itself stays in our mailbox for 30 days. Reply "stop" and no character writes to you again; for that we keep a keyed hash of your address. Write to help@llmmonster.com to have everything about your address deleted. The legal basis is our legitimate interest in answering mail you send us.
The contact page
On the contact page you write to us. We email your name, email address and message to our own inbox, with your address as the one to answer, and a person reads it and answers you by email. The server keeps no copy once that email has gone. We keep the email and our answer as long as we need them to deal with what you asked. Messages written to one of our characters through the earlier version of the page, before 16 November 2026, were kept until you confirmed them by the link we sent, and at most 48 hours unconfirmed or 7 days after confirming, then handled as mail to our characters. The legal basis is our legitimate interest in answering a message you asked us to answer.
Payments
PayPal handles the payment. We keep the order: product, website, amount, currency, status, dates, PayPal's order and capture ids, and the payer details PayPal sends back (name, email address, PayPal payer id and country). We send PayPal your email address and our id for your account or organisation, so the payment can be matched. We never receive your card number. For every order and subscription we also keep what you ticked at checkout (the terms version, the start-now request and, if you buy for a business, its name and country), with the exact wording and the time, as long as the order records; the IP address you ticked them from is kept with them for 30 days. If you withdraw from a purchase on the account page, we keep your statement, name, email address and the time, also as long as the order records.
Sites we do not serve
When we refuse a website (see the terms), we keep the domain, the reason, where it happened and the time, and no report. If a site appears to show child sexual abuse, we fetch nothing more, and a person may report the domain to a hotline such as the Internet Watch Foundation. The legal basis is our legitimate interest in not serving those sites and, for child abuse, in protecting children.
Server logs and security records
Our web servers and services log each request with its IP address, time, address requested and browser type, to keep the service running and to stop abuse. A few security events (a failed sign-in step, a payment message that did not verify) are recorded with the IP address they came from.
Search Console data
LLM Monster's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
You can connect Google Search Console for a domain: from your account, under a free scan report, or as a way to show a site is yours before a scan. Connecting is free and needs an account. You sign in with Google and allow read-only access (Google's permission webmasters.readonly, nothing else). It does not let us change anything in Search Console.
From that property we read clicks, impressions, click rate and average position by date, search query, page, country and device, going back as far as Google makes them available, then the newest days once a day. We read them for web search and for the other result types Search Console reports (images, videos, news, Discover and Google News), and the same totals by search appearance. On a day with more rows than Google sends in one answer, we ask for that day in smaller parts, so rare searches are kept too. We also read the list of sitemaps each day and Google's index status (URL Inspection) for up to 200 pages a day, chosen from your most important pages, pages that changed, pages with the most clicks and, in turn, every other page we know, and we keep each day's sitemap list and every index status as a dated history. Google only offers a limited number of past months. The days we have already read stay stored while the connection is on, also after Google stops offering them, so the history we hold for you grows longer than the one Search Console shows.
We use it only to show you your own figures (top queries and pages, quick wins, pages with a low click rate for their position, queries split across two pages, trends and dated changes) and, for a domain on the Full Meal, in that domain's monthly audit: queries as keyword ideas, clicks to rank which pages matter, your real clicks to correct our traffic estimates for your competitors in your report, and figures in the summary. For a Search Console site on a Full Meal, its monthly report is made from the same data, on our own servers: no provider gets that site's Search Console data.
For the Full Meal audit some of the providers listed below get a part of it, only to return a result to us for your report: our search data provider gets search queries, to look up their search volumes and results; our labelling provider gets search queries, to label them; our text-grouping provider and Anthropic get search queries, to group and name them, and Anthropic also the figures that go into the written summary of the month and, for suggested titles and descriptions, the searches that lead to a page with that page's own public text; and some of your queries become buyer questions that we ask the AI assistants listed below, directly or through our web access provider, to see who they name. Each may use them only to give us that result. Nobody else gets Search Console data from us.
Search Console data is never sold, never shown to other customers, never added to the market data we compare across sites, never used for advertising, never used to train AI models, and never used to decide anything about you as a person. Nobody at LLM Monster reads it unless you ask us to for support, security needs it or the law requires it. We would pass it on in a merger or sale of the business only after asking you first.
Who sees it: every current member of the organisation that connected it, or only you for a connection made without an organisation. If you sign in with Google and your Google account can read a property of the domain, we also record that as proof the domain is yours, like the DNS record or the file; a verified owner of the property joins the organisation whose home is that domain.
The permission Google gives us is stored encrypted (AES-256) on our account server and is never sent to the server that reads the data, which only gets access that expires within an hour. The data itself sits in a private part of our database on the server that runs scans.
We keep it while the connection is on and your organisation uses LLM Monster, back to the first day we read, so your history keeps growing. Google Analytics rows are the exception: we keep the last 400 days. If your organisation has had no paid plan and nobody has signed in to it for 12 months, we disconnect and delete the data as below. Disconnect in your account or under the report and we delete the stored permission at once, revoke it at Google, and delete every row of your Search Console data within an hour; copies in our encrypted nightly backups are gone within 40 days. If you remove our access at Google instead (myaccount.google.com/permissions), we stop reading at the next daily update and mark the connection as needing attention; disconnect it to have the data deleted. When you delete your account, every Search Console connection you made is disconnected first, which deletes its data the same way.
Google Analytics data
LLM Monster's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Once a site is shown to be yours, you can connect a Google Analytics 4 property of it from your account. You sign in with Google and allow read-only access (Google's permission analytics.readonly, nothing else), then pick the property whose web stream is on your domain. We cannot change anything in Google Analytics.
From that property we read only search and AI assistant visit counts per page: for each day, page address and channel, the number of sessions that came from organic search (Google Analytics' Organic Search, Organic Shopping and Organic Video channels) or from AI assistants (its AI Assistant channel and the assistants' own web addresses), and for AI visits the assistant's address, such as chatgpt.com. Nothing else: no other channels, no engagement, page view or event figures, no visitor, device, location, demographic or user details. Google filters the data before it reaches us, so we never receive the rest. We read the last 180 days, then the newest days once a day. We use it only in that domain's paid reports, to list pages people reach from search or AI assistants that no other page links to, pages search engines cannot list that still get those visits, and pages with no such visit in 90 days. It is worked out on our own servers: no provider gets your Google Analytics data, and it is never sold, never shown to other customers, never added to the market data we compare across sites, never used for advertising and never used to train AI models.
Who sees it, how the permission is stored, how long it is kept and how disconnecting deletes it work as for Search Console data. One difference: Google keeps one permission per Google account for everything you allowed us. While the same person has both connected by signing in with Google, disconnecting one deletes its stored permission and its data, and the Google permission stays in place until the other is disconnected too.
Checks we run with Google
Some findings in a report come from Google services that we ask about the website, not about you: real-visitor speed figures from the Chrome UX Report, and, where we show it, whether Google's Web Risk lists the site as unsafe. We send Google the page addresses and nothing else. Speed figures come from the Chrome UX Report by Google, licensed under the Creative Commons Attribution 4.0 licence. A Web Risk warning is shown as Google's advisory, with Google's notice that it may not be complete or free of errors.
AI in LLM Monster
We use AI systems in these places, and nowhere else:
- To ask AI assistants the questions your buyers ask, and to read their answers.
- To read and judge page text, write example fixes and summaries, and group search queries, in scans and audits.
- To judge mail sent to our cartoon characters and to write their replies. Every reply says it was written by an AI system.
We do not use your data to train AI models, and our providers may use what we send them only to give us the result. No decision with legal or similarly significant effect on you is made by a machine: AI results go into reports for people to read.
Why we use it, and the legal basis
| What for | Legal basis |
|---|---|
| Giving you what you asked for: a scan, a check, an audit, your account, your team, its reports and connections | Performing our contract with you, or steps you asked for before one |
| Taking payment and keeping accounting records | The contract, and our legal duty to keep records |
| Keeping the service fair and safe: rate limits, bot checks on sign-up, logs, refusing sites we do not serve | Our legitimate interest in security and fair use, and in keeping the service free of abuse |
| Munch's letter and the monthly AI check email | Your consent, which you can withdraw at any time with one click |
| Counting visits to our marketing pages with Google Analytics | Your consent, which you can withdraw at any time under Cookie settings at the foot of every page |
| Writing to you about your results and LLM Monster's paid audits, after you gave your email for a free scan or a free AI check | Our legitimate interest in telling you about similar services; you can opt out in any such email or by replying stop |
| Short notices to our team when a scan, check or order comes in, so a person can follow up | Our legitimate interest in looking after customers |
| Answering mail to our characters and the contact page | Our legitimate interest in answering you |
| Publishing a guestbook entry | Your consent |
| Agency leads and client data | We act for the agency, which decides the basis (see the data processing addendum) |
Where we rely on legitimate interest, we have weighed it against your interests and kept the data to what the purpose needs; you can object at any time (see Your rights). We do not sell personal data.
Data outside Europe
Our servers are in the European Union. Some providers above are in the United States (the AI companies, PayPal's parent, Google, Backblaze, and some of the providers listed by role) or reach data from there; the United Kingdom, where our email sending runs, has an adequacy decision. Where data leaves the European Economic Area for a country without one, we rely on the European Commission's adequacy decision for the EU-US Data Privacy Framework (for certified companies) or on the standard contractual clauses, with the UK addendum for UK data. Write to help@llmmonster.com for a copy of the safeguards that apply.
How long we keep it
| What | How long |
|---|---|
| Free scan reports | 30 days, then deleted |
| What we read on the public pages of the competitors of a site on a Full Meal or an agency plan: counts, findings and a few page addresses as examples, never the pages' text | While the site keeps its plan, then deleted within 7 days (for an agency's client site, within 47 days of its last monthly report) |
| AI visibility audits and checks, with the email they were sent to | 400 days, then deleted |
| Your email as a contact, from the free scan or the free AI answer check | 2 years from our last contact, unless you ask us to delete it sooner |
| That you stopped mail about our paid audits (from the link in a free AI check email) | A keyed hash of your address, not the address, for as long as we send such mail, so it stays stopped |
| Your email, website, time zone and consent for the monthly AI check email | While the emails go out, then 2 years from the day you stopped them (the record that you agreed and that you left), unless you ask us to delete it sooner |
| Your email, sign-up page, country and consent for Munch's letter | While you stay on the list; if you never confirm, 2 days; after you unsubscribe, 2 years (the record that you agreed and that you left), then deleted, unless you ask us to delete it sooner |
| Your email and domain on the Full Meal early-access list | 2 years from the day you last joined, unless you ask us to delete it sooner |
| The free AI check's lookup records (keyed hashes of the browser id, browser settings and network, with the websites) | 1 year |
| Mail you send to our characters | The mail itself, 30 days. Our record of the exchange: text, subjects and message ids 180 days; the judgments, the keyed hash of your address and its random id 2 years after your last mail. If you replied "stop", a keyed hash of your address for as long as the characters answer mail. All of it sooner on request |
| A message from the contact page, with your name and email address | Until the character gets it (then as mail to our characters, above); 48 hours if you never confirm; 7 days after you confirm at the most |
| Agency widget leads, with a keyed hash of the network address they came from | As long as the agency keeps its plan, then 90 days, unless it or you ask us to delete them sooner |
| Guestbook entries | Until you or we delete them; an entry nobody approved, 30 days; one turned down or marked as spam, 7 days. The hash of your network address, 30 days |
| Ideas from the suggestion box | A year after a person read them; one nobody read, 30 days |
| Orders and payment records, with the name and email of the account that placed them | As long as tax and accounting law requires (in Cyprus, currently 6 years), also after the account is deleted |
| Your account, your organisation and the full reports in it | Until you delete the account (how) or the organisation, or ask us to close it. Reports stay readable after a plan ends |
| Search Console and Google Analytics data you connected | While the connection is on (Google Analytics rows: the last 400 days), and deleted once the organisation has had no paid plan and no sign-in for 12 months; deleted within an hour of disconnecting, backup copies within 40 days |
| Sign-in session, with the IP address it started from | 30 days, or until you sign out |
| A sign-up that was never confirmed | 7 days; the sign-up check record, 35 days |
| Invitations to an organisation | 7 days, or until accepted |
| Codes and links we email you | Up to 48 hours |
| A domain check that was started but not finished (the domain, its token and any address typed) | 7 days |
| Records of sites we refused | 2 years |
| Server logs and security records with IP addresses | Up to 30 days |
| Visit counts in Google Analytics, if you accepted its cookies | At most 14 months, then Google deletes them; the cookies themselves last 13 months |
| Your answer to the cookie question | 180 days in your browser, then we ask again |
| Backup copies | Of the scanning server, up to 40 days. Of the servers for the site, accounts, payment records and the AI visibility service: hourly copies for 2 days, then one a day for 14 days; nightly copies one a day for 7 days, one a week for 4 weeks and one a month for 6 months, removed by the backup provider within 30 days after that, so something deleted on those servers is gone from the backups within about 7 months. Backups are only used to recover from a failure |
Cookies and browser storage
Most cookies and browser storage here are ones the service needs to do what you ask, or that keep a setting you chose. One kind needs your consent: Google Analytics, which counts visits to our marketing pages. The first time you open one of those pages we ask, with Accept and Reject side by side and drawn the same.
Until you accept, Google's analytics script does not load at all: Google gets nothing from the page and sets no cookie. If you reject, or your browser sends Global Privacy Control or Do Not Track, it never loads. It never runs on the pages that hold your account, scans, AI checks, reports, shared links or checkout, and it never receives what you type into a form. The page addresses it gets are cut before any ? or #, and we give it no user id. We use no advertising cookies; Google signals and ad personalisation stay switched off.
The legal basis is your consent (Article 6(1)(a) GDPR, and for the cookies Article 5(3) of the ePrivacy Directive and regulation 6 of the UK's PECR). You can change your answer at any time under Cookie settings at the foot of every page; rejecting deletes the Google Analytics cookies on llmmonster.com. Google acts as our processor under its data processing terms for Google Analytics and may use the counts only to give them to us. Google may handle them in the United States: Google LLC is certified under the EU-US Data Privacy Framework and its UK extension, and its terms include the standard contractual clauses.
| Name | What it does | How long |
|---|---|---|
llmm_sid | Keeps you signed in | 30 days, or until you sign out |
llmm-consent (browser storage) | Your answer to the cookie question | 180 days, then we ask again |
_ga (Google Analytics, only after you accept) | A random id that tells one browser's visits apart from another's | 13 months |
_ga_J389VFJKB8 (Google Analytics, only after you accept) | Keeps count of your visits and the one under way | 13 months |
llmm_auth | Holds a sign-in that is under way | 10 minutes |
Keycloak's cookies on auth.llmmonster.com (AUTH_SESSION_ID, KC_RESTART, KEYCLOAK_IDENTITY, KEYCLOAK_SESSION, KEYCLOAK_REMEMBER_ME) | The sign-in itself, and remembering you if you ask it to | Up to 30 days (7 days without use) |
llmm_scanv | Remembers up to 5 domains you showed are yours (before a scan or by connecting Search Console), so the next scan skips the step | 30 days |
lm_id and llmmonster-aivis-id | The random id that keeps the free AI lookups to one per person | 1 year |
Storage for your work: llmm-scans, llmm-verify:*, llmmonster-ai-visibility-v1, llmmonster-aivis-audits, llmmonster-aivis-team, llmm-in | Your recent scans and checks, a domain check in progress, links to your audits, and the first letter of your name while signed in | Scans 30 days, audit links 90 days, the rest until you clear them |
Settings you chose: llmm-motion, llmm-sound, llmm-gags, llmm-gsc-nudge:*, llmm-advent, llmm-egg* | Motion, sound and jokes on or off, a dismissed card, and the little surprises you found | Until you clear them |
Short-lived storage: llmm-utm, llmm-guard-*, llmm-gag-last:* | The campaign tags of the link you came by, a form check carried from one page to the next, and which joke you saw last | Until you close the tab |
| Google reCAPTCHA (on the sign-up page of auth.llmmonster.com only) | Tells people from bots; Google sets its own cookies | Google's own terms |
| PayPal (only once a checkout reaches its payment step) | Takes the payment; PayPal sets its own cookies | PayPal's own terms |
Apart from Google Analytics after you accept, and PayPal's script during a checkout, no other company's script runs on our pages; fonts and pictures come from our own servers.
Your rights
You can ask us to tell you what we hold about you and send you a copy, correct it, delete it, limit or stop our use of it, or hand it over in a common format. You can object at any time to our use of your data for our legitimate interests, and to any email about our services, which then stops. Where you gave consent, you can withdraw it at any time. Write to help@llmmonster.com; we may ask you to show the address or account is yours. We answer within one month, and tell you if a complex request needs up to two more.
If you are unhappy with how we handled your data, you can complain to the Commissioner for Personal Data Protection in Cyprus (gov.cy/dataprotection), to the authority where you live or work (in the United Kingdom, the Information Commissioner's Office), or go to court. We would like the chance to put it right first.
If you are in the United States
We do not sell personal information, and we do not share it for cross-context behavioural advertising. We do not use sensitive personal information to infer anything about you. If your state gives you privacy rights, you can use them as described under Your rights; we will not treat you differently for doing so.
Children
LLM Monster is for adults. We do not knowingly collect data from anyone under 18. If you think a child has given us personal data, write to help@llmmonster.com and we delete it.
Changes
When we change how we use personal data we update this page and the date at the top. If the change matters to you (a new use, a new kind of provider), we also email account owners before it applies.
