Last updated 6 October 2026
This policy covers COEY as a company. What a product does on your own computer is in its supplement: GroundSlate privacy supplement.
COEY Privacy Policy
Last updated: 6 October 2026
This policy explains what Royler, LLC, d/b/a COEY ("COEY", "we", "us"), of 2173 Rockledge Drive, Rockledge, FL 32955, USA, does with your information. It covers the coey.com website, your COEY account, your licence, payment, and support.
Each COEY software product adds a supplement describing what that product does with your information, including where it runs and what reaches COEY. Some COEY products run entirely on your own computer and send us nothing about your content; others are hosted by us, and holding your content is what they are for. The supplement says which, for the product you use. GroundSlate's is the GroundSlate Privacy Supplement, published beside this policy. Where a supplement is silent, this policy applies.
The short version
We hold what is needed to sell you a licence and keep it working. We build no profile of you from anything a COEY product does. The advertising in section 5 is different, and section 5 says so in terms: Google, Meta and OpenAI profile the visit, and that is what you are agreeing to or refusing. An email address, a licence, the machines it is activated on, and records of the downloads and messages that passed between us. A product may hold more in order to do its job, and its supplement says what: section 1 is the company-level list, not every product's.
The website measures traffic and advertises. coey.com uses Google Analytics, Google Ads, Meta and OpenAI. They set cookies, they see the pages you visit, and they build a picture of that visit which Google and Meta also use across other sites and OpenAI uses for its advertising in ChatGPT. When you buy or take a free key, that is reported to Meta from our own server as well as from your browser, with a scrambled copy of your email address so they can match the sale to an ad. OpenAI's tag also reads an email address, name or phone number typed into a form here or shown on a page, and sends a scrambled copy of it. You can refuse all of it, and section 5 says how.
None of that reaches what a product holds for you. The measurement above is about the website. It is not connected to your library, your licence, or anything a COEY product processes.
We never see your card. Stripe takes payment and holds those details. A card number has never reached a COEY server.
Where your content lives depends on the product, and only the supplement can tell you. Some COEY products keep everything on your own computer and send us nothing about it; a hosted product holds it for you, which is what it is for. Neither is the default, so read the supplement for the product you use rather than assuming from this page.
1. What we collect, and why
Your account
| What | Why | Where it comes from |
|---|---|---|
| email address | it is your account, and it is how a licence key and a receipt reach you | you give it to us |
| sign-in token | a single-use link proving the address is yours, valid briefly and then spent | we generate it |
| licence key, product, tier, status, seats | so we know what you bought and what it entitles you to | your purchase |
| Stripe customer and subscription identifiers | so a renewal or a cancellation finds the right subscription | Stripe |
| renewal date | so we can tell you what renews and when | Stripe |
There is no password, so there is none to lose. Signing in sends a link to your email address.
Your machines
When a COEY product activates, it sends its licence key, a machine identifier, the machine name you gave that machine, its operating system version, the product version, and the role it runs in. The product's supplement lists those fields exactly. We keep that as an activation record so a seat ties to one machine and can be released again.
We also derive one thing from it that the product does not send: when a machine reports a different version from last time, we record that it moved from the old version to the new one. It is how we know whether a release reached anyone. It is tied to the machine identifier, not to anything about how you use the product.
A benchmark you send
A COEY product can measure how fast it runs on your machine and send us the measurement, and it does that only when you ask it to. Nothing is sent on a timer, at launch, or as a side effect of anything else. What is measured is a fixed input that ships inside the product and is the same on every installation, which is what makes one machine's figures comparable with another's, and it is why this is a measurement of the product rather than of you.
What a record carries, and this is the whole of it. When you started the run and how long the whole of it took; how much of it you asked for, the short measurement or the full one, and for each thing measured whether it ran or was skipped and why; the timings, memory figures and progress figures of each thing that did run; for a produced file, an identifier derived from its own bytes; the chip, how much memory the machine has, its operating system version and the product version; the versions of the engines that ran; which of the product's features this machine is capable of; and the record's own format version with a label saying what kind of record it is, so that we can refuse one we do not understand rather than guess at it. The product's supplement lists those fields exactly. A record carries no file name, no path, no machine name, no account name, and nothing about what you keep in the product: no counts, no identifiers of your own media, no profiles and no folders.
The start time is in that list on purpose. It is the one field that says something about your day rather than about your machine, and a figure cannot be compared across releases without it, so it is named here rather than left to be discovered.
A record is anonymous unless you attach it to your account, and anonymous is the default. An anonymous one carries no licence key and no machine identifier, so nothing in the record links one run to another. Attaching adds your licence key and the same machine identifier the activation record above carries, which is that machine's hardware UUID, so the run appears on your account and you can withdraw it from there. The product names both in the sentence it shows you above the send button, nothing adds either to a record afterwards, and a run you sent anonymously is withdrawn with a secret the product hands you at the time.
What we keep beside the record is not nothing, and here it is. As with the two rows below, we store a salted digest of your IP address and the User-Agent, kept with the record for as long as the record is. The digest is there for one job, to count how many benchmarks a single origin has sent so that nobody can post a corpus of them, and counting them means they are grouped by that digest. So the honest statement is the narrower one: nothing in an anonymous record ties it to you or to another run, and the digest beside it is the same origin marker the downloads and messages rows carry. It is a SHA-256 of the address with a secret salt, truncated, and it is not the address: without the salt it cannot be matched back to one, it is not an account, and it does not follow you off the connection you sent from.
Downloads and messages
| What | Why | Kept with |
|---|---|---|
| which build you downloaded, and when | so we know how many copies of each build are out there | your licence, when you were signed in |
| the contact form: your name, email, company, topic and message | so we can answer you | the message |
Codes, links and the limits on them
| What | Why | Kept with |
|---|---|---|
| an email code record: your email address, the code as a keyed hash (never the code itself), when it was sent, when it was used and how many wrong tries it has had | a product can get you a key by emailing you a six digit code, and this is how the code you type is checked | nothing else; section 6 says when it is deleted |
| rate limit records: a salted digest of your IP address, and hashed counters per email address of codes sent, wrong codes tried and download links sent | so nobody can flood an inbox with codes or links, or keep guessing at a code | nothing else, and neither kind is your address |
| a download page counter record: a salted digest of your IP address | so one network cannot inflate the download page's daily counts below; it caps how many times one network can add to them in an hour | nothing else, and it is not your address |
Emailing yourself the download link. When you ask a download page to email you the link, so you can open it on the computer the product runs on, your email address is used to send that one email and is not stored. What remains is the hashed counter above, which limits how many links one inbox can receive.
Counts with nobody in them. The download page keeps daily totals: how often it offered to email the link and to which kind of device (a phone, a tablet, another kind of computer), how often a link was sent, and how often "Download anyway" was used. Each is one number per day per event, with no identifier, no cookie and no address, so the counts cannot be tied to anyone and need no consent. Counting the offer being shown is the one step that keeps anything about the visit: the counter record above, a salted digest of your IP address that caps how many times one network can add to that count, deleted within two days of the last moment it counts toward that cap.
Your consent decisions
When you answer the cookie question we keep a record that you answered it, and what you said.
The law that makes consent meaningful also requires us to be able to show it was given, and a cookie
sitting on your own computer proves nothing because you can clear it. So each decision is recorded
here with the two choices, how it was made (the banner, the Your Privacy Choices panel, or your
browser's signal), the version of the question, the coey_cid id above, a salted digest of your IP
and your User-Agent. Your account is attached only if you were signed in.
It is append-only, so changing your mind adds a record rather than erasing the old one. Ask us for your record and we will produce it.
Both of the rows above also record a salted digest of your IP address and the User-Agent your browser sent. The digest is a SHA-256 of the address with a secret salt, truncated, and it is not the address: it tells one origin from another when a number looks wrong, and without the secret salt it cannot be matched back to an address.
What we do not collect
No tracking inside a product. The claim that follows is about COEY's software, not about coey.com: see section 5 for the website, which does use analytics and advertising.
COEY products carry no analytics, telemetry, crash reporting or usage tracking, and none reports your usage to us. The promise is that we do not measure you, and the one measurement a product can send is of a fixed shipped input you started and sent yourself, which is the benchmark described above: nothing about how you use a product, what you keep in it, how often you open it or which of its features you touch is in it, or reaches us by any other route. We do not buy data about you.
Website advertising and your account meet in two places, and both are named. When you buy a licence or take a free key, that conversion is reported to Meta with a scrambled (hashed) copy of your email address, so a sale can be matched to an advert. And OpenAI's tag reads an email address, phone number or name typed into a form on coey.com, and an email address or phone number shown on one of its pages, including your own address on your account page, and sends a hashed copy with what it reports. Those are the only links between the two, both happen only with your agreement, and neither carries anything else: not your licence key, not your machine identifiers, not anything a COEY product holds. Section 5 gives the detail.
No card details. See section 4.
No analytics from inside a product. COEY products contain no analytics, telemetry, crash reporting or usage tracking, and none reports your usage to us. That is a commitment about measurement and it holds however a product is deployed, and it is stated exactly: no measurement of you, and the only measurement a product sends is of a fixed shipped input you started and sent yourself, which is the benchmark described above. It is not a claim that no product ever receives your content: a hosted product necessarily does, and what any given product sends, holds, or processes is in its supplement.
Our legal basis, where the GDPR or UK GDPR applies
| What | Why we may do it |
|---|---|
| your account, licence and activations | performance of a contract with you |
| payment, and the records that show it happened | a legal obligation, and performance of a contract |
| support and contact messages | legitimate interests: answering someone who wrote to us |
| the salted IP digest and User-Agent on downloads and messages | legitimate interests: telling one origin from another when a number looks wrong |
| email codes, the download link email, and the rate limit records on both | performance of a contract for a code that gets you a key or a link you asked for; legitimate interests for the limits, which keep either from being used against someone else's inbox |
| the IP digest on the download page's counts | legitimate interests: keeping one network from inflating a count we use to judge the page |
| analytics and advertising (section 5) | your consent, and nothing else. Withdraw it at any time |
We collect no sensitive personal information as the CPRA uses that term, and none of the special categories in GDPR Article 9. We do not ask for it, and we have no field for it.
2. Cookies
Cookies on coey.com fall into two groups, and the difference is the one that matters: the first group is needed for the site to work, and the second is not and is yours to refuse.
Necessary, always on. None of these carries advertising value or identifies you to anyone else.
One of them travels: coey_cid is passed to Stripe with a checkout, for the reason its row gives.
| Cookie | What it does | How long |
|---|---|---|
coey_session |
keeps you signed in. It holds your email address and an expiry, signed so your browser can carry it but cannot edit it. There is no session table on our side | 30 days |
coey_redeem |
carries a redemption code across the sign-in round trip, so a code you typed before signing in is not lost | 15 minutes |
coey_consent |
remembers your answers below, so we do not ask again. It holds your two choices, the date, and the version of the question you were asked | 180 days |
coey_cid |
a random id for this browser, with no account behind it, so the record of your consent decisions can be threaded together and shown back to you. It is also passed to Stripe with a checkout, because a payment confirmation reaches us from Stripe with no browser attached and this is how your advertising choice is looked up before anything is reported. It is used for nothing else | 180 days |
Analytics and advertising are two separate questions, and you can answer them differently.
Measuring which pages get read is not the same thing as showing you an advert later, so we ask them
apart rather than as one lump, and taking one without the other is a normal answer rather than an
awkward one. These are set by Google, Meta and OpenAI, not by us, and Google's and Meta's are
readable by them across other sites that use the same tools. They include Google Analytics
cookies (_ga and similar), Google Ads cookies (_gcl and similar) and Meta's (_fbp, and _fbc
when you arrive from one of their ads). Typical lifetimes run from a few days to about two years;
Google's and Meta's own policies, whose addresses are in section 3, carry the current figures.
OpenAI's tag sets three cookies: __obref, a random id for this browser, kept for a year;
__oppref, which records the OpenAI advert you arrived from when you did, kept for 30 days; and
__oaiq_consent, which holds your advertising answer for OpenAI's own code, kept for 30 days. It
also keeps that answer in this browser's local and session storage, and sets one more cookie only
to learn which domain it may write to, deleting it at once.
Refusing them is a real refusal. The site asks before setting anything in this group and sets nothing in it until you say yes. That applies wherever you are, not only where the law compels the question. Saying no is one click and leaves the site fully usable. Section 5 covers what runs, changing your mind, and the signals we honour.
3. Who else handles it
We keep the list short on purpose. This is the list for coey.com, your account and your licence; a product that runs on COEY infrastructure adds its own, and its supplement names them. Each entry below acts on our instructions, under its own security and privacy terms, except where marked otherwise.
| Who | What they do | What they see |
|---|---|---|
| Vercel | hosts the website | requests to coey.com, including IP addresses, as any web host does |
| Neon | hosts the database | everything in section 1, at rest |
| Stripe | takes payment | your card details, your billing address, and what you bought |
| Resend | sends the sign-in link, receipts, the six digit codes a product asks for when it gets a key by email, and download links | your email address and the message |
| Cloudflare | runs the Turnstile check that keeps bots off the contact form | your IP address and browser signals, on that form only |
| Analytics, and Ads including remarketing | the pages you visit on coey.com, your IP address, device and browser, and whether a visit led to a purchase. Google also uses this for its own purposes across other sites, under https://policies.google.com/privacy | |
| Google Ads | the advertising half of the row above, including remarketing and conversion measurement | the same, plus which ad or search led you here. Controls at https://myadcenter.google.com |
| Meta | advertising, including remarketing and conversion measurement | the same shape of visit data through Meta's pixel, and, when you buy or take a free key, that conversion sent from our own server with a hashed copy of your email address, the browser and click ids Meta's own pixel set, and your browser's user agent. Used for its own purposes across other sites, under https://www.facebook.com/privacy/policy. Controls at https://accountscenter.meta.com/ads |
| OpenAI | advertising in ChatGPT, including conversion measurement | the pages you visit on coey.com, your IP address, device and browser, which OpenAI advert brought you here, whether a visit led to a checkout, a purchase (with its amount) or a free key, and a hashed copy of any email address, phone number or name typed into a form on coey.com, or email address or phone number shown on its pages. A country, city, region or postal code typed into a form would be sent as written, not hashed; no form on coey.com asks for one. Used for its own purposes under https://openai.com/policies/privacy-policy |
Google, Meta and OpenAI are not ordinary processors, and it would be misleading to list them as if they were. For their rows above, they decide their own purposes as well as ours, so they are controllers in their own right and their policies govern what they do next. Every row above theirs acts only on COEY's instructions.
4. Payment
Stripe processes every payment, and card details never reach COEY. They go from your browser to Stripe. We receive confirmation that a payment succeeded, the identifiers that let us find the subscription again, and what you bought. Stripe holds your card under its own privacy policy.
5. Analytics and advertising
Status. This is running. Earlier versions of this policy said it was not, and described it in advance because COEY had decided to introduce it; that is no longer the case, and the date at the top moved when it changed. The controls that let you refuse it were built first, which was the order we chose deliberately: the machinery to say no existed before there was anything to say no to.
What runs on coey.com. Google Analytics measures which pages people read and which routes lead to a purchase. Google Ads and Meta advertise COEY elsewhere, and both use remarketing, which means a visit here can be why you later see a COEY ad on another site or in a Meta app. OpenAI advertises COEY in ChatGPT, and measures which of those adverts led to a checkout, a purchase or a free key.
What they receive. The page you are on, the referring page, your IP address, your device and browser, and the fact that a visit turned into a download or a purchase.
Two of those conversions are also sent from our own server, not only from your browser: buying a licence, which is reported when Stripe confirms the payment, and taking a free key. This is worth stating plainly because it is easy to assume otherwise: a browser extension that blocks the pixel does not stop these. Refusing does. They are sent only with your agreement, and for a purchase that agreement is looked up from the record described in section 1, because a payment confirmation reaches us from Stripe with no browser attached.
Those two carry a hashed copy of your email address, a SHA-256 of it rather than the address itself, so Meta can match the sale to an advert without our handing over the address in the clear. They also carry the browser and click ids Meta's own pixel set in your browser and your browser's user agent. We do not send your IP address with them, and we never send your licence key, your machine identifiers, or anything a COEY product holds.
OpenAI's tag also reads what is on the page. OpenAI calls this automatic advanced matching, and it is switched on. When you have agreed to advertising, the tag looks for an email address, phone number or name typed into a form on coey.com, and an email address or phone number shown on one of its pages. For example: the address you type to sign in or to have a download link emailed to you, your name and email address on the contact form, and your own address on your account page or a receipt. It hashes what it finds in your browser and sends the hash to OpenAI with what it reports, so OpenAI can match a visit to an advert, and those details do not leave your browser in the clear. A country, city, region or postal code typed into a form would be sent as written rather than hashed, and no form on coey.com asks for one. It reads nothing else on those pages: not your licence key, not your Macs' names, not anything a COEY product holds. On COEY's own administration pages it reads nothing and reports nothing, because customers' addresses appear there, and nobody's address may be read on somebody else's agreement.
These are the two places where website advertising and your account meet, and section 1 says so there too. Until 4 September 2026, this policy said we sent advertisers no email address at all. That was true when it was written and it is not true now, so it has been replaced rather than softened.
Under California law this is "sharing" for cross-context behavioural advertising, and under the GDPR it needs your consent rather than our legitimate interest. Both mean the same thing in practice: it is yours to refuse, and refusing costs you nothing.
How to refuse, and how to change your mind. All of it is built and working. The question only appears where a tracker is actually configured, because asking you to decide something that has no effect would teach you the question is meaningless.
- Say no when the site asks. Nothing in the analytics or advertising group is set unless you agree, wherever you are, and not only where the law compels us to ask. Refusing is one click, it sits first, and it is the same size and weight as agreeing.
- Use the Your Privacy Choices control in the footer of every page, at any time, including to withdraw agreement you gave earlier. It shows you what you last chose.
- Turn on Global Privacy Control in your browser or an extension. We treat a GPC signal as an instruction not to share, it applies without your having to ask us, and it overrides an earlier yes: a browser that starts sending the signal has changed your mind in the way it knows how.
One control exists today, because it is not ours. Google and Meta offer their own, which reach further than this site: https://myadcenter.google.com and https://accountscenter.meta.com/ads.
None of this reaches your library or anything a COEY product holds, and the only places it meets your account are the hashed details described above. Refusing changes nothing about your licence, your purchase, or any COEY product.
6. Retention
| What | How long |
|---|---|
| email address, licence, activations | while you have a licence with us |
| version history for a machine | while the licence exists |
| download records | indefinitely. Deleting your account does not delete them: the row is kept and its link to your licence is severed, deliberately, so that a count of what was downloaded survives. What remains is the build, the date, the salted IP digest and the User-Agent, with nothing tying them to you |
| a benchmark you sent | indefinitely. It describes a fixed input that ships inside the product and names nothing of yours, and the one question it answers, whether a new version made a machine faster, is a question that needs the old records. You can withdraw one at any time, with the secret the product gave you when it sent it, or from your account if you attached it. Deleting your account does not delete one you attached: its link to your licence is severed and the record stays, with nothing tying it to you, which is the treatment the download records above get and for the same reason. A record you withdraw is taken out of every reading of the corpus immediately and is not put back; the row itself is kept, marked withdrawn, and its origin digest goes on counting toward the limit on how many one origin may send, so that withdrawing is not a way to reset that limit |
| contact messages | as ordinary business correspondence |
| analytics and advertising data (section 5) | held by Google, Meta and OpenAI under their own retention settings, not by us. We hold no copy |
| your consent decisions | while you use the site and for a period after, because a record of consent is only useful if it outlives the consent. It is the evidence that we asked and you answered |
| sign-in tokens | until used, or until they expire, whichever is first |
| email code records | deleted by a daily scheduled clean-up within two days of the code expiring |
| rate limit records (IP digests and hashed per-address counters), and the download page counter's IP digest | deleted by the same daily clean-up within two days of the last moment each counts toward a limit |
| the address you give to have the download link emailed | not stored: it is used to send that one email |
| the download page's daily counts | indefinitely. They are totals per day and name nobody |
Ask us to delete your account and we will, which releases any machines on the licence. Some records must survive that: Stripe keeps what tax and accounting law requires it to keep, and we keep what we need to show a payment happened.
What a product holds, where it holds it, and how long, is in that product's supplement. For a product that runs on your own computer, that data is yours and we hold no copy of it.
7. Your rights
Where the GDPR, UK GDPR, CCPA and CPRA or similar laws apply, you have rights of access, correction, deletion, portability and objection over personal data a company holds about you.
How you exercise those rights depends on where the data is, and the supplement says where. For a product that runs on your own computer, most of what it knows is not ours to give you because it is already yours: it sits in your own files, readable and deletable by you without asking us. For a product we host, we hold it, and you exercise these rights against us the same way you do for anything in section 1.
What we hold is section 1, and it is small. You can see your machines and release them yourself from your COEY account. For access, correction, deletion or a copy, write to privacy@coey.com and we will act on it. We do not charge for this and we do not require an account to ask.
We DO share personal information for cross-context behavioural advertising, as the CCPA and CPRA use that word, because Google Ads, Meta remarketing and OpenAI's advertising measurement are exactly what that term describes. We receive no money for it. We do not claim it falls outside the statutory definition of a "sale", which reaches other valuable consideration and which regulators have applied to advertising technology of this kind, so treat the opt-out below as covering both. Section 5 says what is shared and how to stop it, the footer carries a Your Privacy Choices link, and we honour Global Privacy Control.
An earlier version of this policy said we did neither. That was true of a site with no advertising on it and stopped being true when advertising arrived, which is why it is stated plainly here rather than left for someone to discover.
We will not discriminate against you for exercising any of these rights. Refusing analytics and advertising, or asking us to delete your account data, changes nothing about your price, your licence, or the software you receive.
An authorised agent may act for you. Send us written proof that you authorised them and we will deal with them as we would with you.
Do Not Track. Browsers send a Do Not Track signal that has no agreed meaning, so we do not act on it. We do act on Global Privacy Control, which does have one. See section 5.
You may also complain to your local supervisory authority. If you are in the UK, the EU or the EEA and want a point of contact for these rights, write to privacy@coey.com and we will name one.
8. Children
COEY products are not directed at children, and we knowingly collect nothing from anyone under 13. You must be 18, or the age of majority where you live, to hold a COEY licence.
We do not knowingly advertise to children or share a minor's information for advertising. The advertising in section 5 is aimed at adults evaluating professional software, and under the CCPA and CPRA we do not sell or share the personal information of anyone we know to be under 16.
Products are frequently used on family footage, which may contain children. Where that footage is held is in the product's supplement, and the responsibilities that come with processing it are set out there and in the product's Schedule to the COEY Master Terms.
9. International transfers
We are in the United States and the infrastructure in section 3 is operated from the United States. If you are in the UK, the EU or the EEA, using COEY means your account data is transferred there. We rely on the UK and EU Standard Contractual Clauses that our processors incorporate, and on your consent where the transfer is one you asked for by buying from us.
Google and Meta transfer and process internationally under their own arrangements, including the EU-US and UK Data Privacy Framework and their own Standard Contractual Clauses. OpenAI relies on adequacy decisions and the Standard Contractual Clauses with the UK addendum, as its European privacy policy describes at https://openai.com/policies/eu-privacy-policy. Where you refuse analytics and advertising, there is no such transfer to make.
10. Changes
If this policy changes materially we will update the date above and the version marker at the top of this file, and note the change in the release that carries it.
11. Contact
COEY, Royler, LLC · privacy@coey.com · legal@coey.com
Write to either address for anything in this policy, including a rights request under section 7.