Privacy Policy

1.1 Your account

If you sign up with an email address, we store the address and a hash of your password. We never store the password itself. If you sign in with Discord, we store your Discord user ID, and we receive the username and avatar Discord exposes. We also receive the email address on your Discord account when Discord says it is verified, and we use it to fill in your Illarin address only if you have none.

Every account also has the handle you chose, and the date it was created.

1.2 What you upload

The file you uploaded, kept exactly as you uploaded it. The name, blurb, tags, and adult content answer you attached. The images you added. Anything written inside the work itself.

1.3 Your settings

Whether you want to see adult content, and whether your adult work appears on your public profile.

1.4 Apps you connect

For each app you connect: the name and version it reported, the permissions you granted it, when you connected it, and when it last used its access. Its access tokens are stored only as hashes.

1.5 Server logs

Our web server records the usual line for each request: the IP address it came from, the time, the address requested, the response status, and the browser’s user agent string. One-time link codes are stripped out of that line before it is written.

1.6 Page views

Illarin counts page views with Umami, an analytics tool we run on our own servers, so the counts never go to another company. For each page you open, it records the page address without anything after a “?” or “#”, the page title, the address of the page that linked you here, your browser, operating system, device type, screen size, and language, and the country, region, and city your IP address points to. It sets no cookie, stores nothing in your browser, and keeps neither your IP address nor anything tied to your account, so no identity is kept. Every page view record is deleted after 30 days. Staff read only Umami’s traffic charts, and no number Illarin shows comes from it.

1.7 Counts of what happens

When an account is created, the site is visited, a work’s page is viewed, a work is downloaded or sent to an app, or a work is published, Illarin records which of those happened, the work where there is one, and the day. The record holds no account, no IP address, no time of day, and nothing about the browser. Illarin reads the browser’s name to skip known bots, and never stores it. Views by a work’s creator and sends to the creator’s own apps are not recorded. Each night Illarin adds these records up into totals for each day and deletes the records older than 30 days. The daily totals are kept, and a work’s page shows its total views and downloads, with sends to an app counted as downloads.

A view or a download counts once per reader, per work, per day, a visit to the site counts once per reader per day, and a send counts once per app, per work, per day. To tell readers apart, Illarin turns your IP address, your browser’s user agent string, and the work, where there is one, into a code, using a secret made new each day. The code can’t be turned back into your address or matched across two days or two works, and the IP address and user agent are never stored. At midnight UTC the day’s secret and every code made with it are deleted.

1.8 Monitoring

Illarin’s servers send their logs to Datadog, a monitoring service, so that errors and outages show up. Those logs hold the request lines described in 1.5, with the IP address replaced before they leave the server, and the errors Illarin’s own programs write. Datadog also receives how busy the servers are. Nothing from Datadog runs in your browser.

1.9 Money

Illarin takes no payments today. If you support Illarin on Ko-fi, Ko-fi handles the payment under its own terms, and Illarin sees only what Ko-fi shows the owner of a page, such as the name and message you leave. Illarin does not tie it to your account.

Illarin may later let you donate, take out a membership, or pay a creator for commissioned work. When it does, a payment provider handles the payment, and your card or bank details go to that provider, never to Illarin. Illarin keeps what it needs to run those features and meet tax law: who paid whom, how much, when, what for, and the provider’s reference for the payment. A creator who is paid gives their payout details to the provider, not to Illarin. This section applies once those features exist.

• We do not record who downloads what. Illarin counts downloads for a creator’s benefit. The record holds the work, the format, the time, and whether the download came from the creator, a connected app, or anyone else. It holds no account, no IP address, and nothing else that could point back to a person.
• There are no ads on Illarin, and there never will be. There are no advertising or cross-site tracking cookies, and no third-party script tracking what you read. Illarin does not sell your data or share it with advertisers.
• Nothing you upload is scanned by a machine learning model. Illarin runs no content classifiers, and it does not use your work as training data.

Illarin sets a cookie holding your session when you sign in, and two short-lived cookies during a Discord sign-in so that it can bring you back to the page you started from. All three are strictly necessary to sign you in. Counting page views sets no cookie.

Your browser also keeps a few display choices locally, which never reach us: light or dark appearance, whether the front page moves, how wide the side panel is, which follow suggestions you dismissed, and, for the length of the tab, how adult content is shown.

• To run Illarin: signing you in, showing your work, search, downloads, and exports.
• To hand your library to the apps you have connected, within what you granted.
• To send you the emails the account needs, which are address verification and password resets.
• To act on reports and enforce the Acceptable Use Policy.
• To keep Illarin working and to see what broke when it does not.
• To see which pages people read, which sites send them here, and how many works are viewed, downloaded, sent, and published each day.
• To take and pass on payments, once Illarin offers them, and to keep the records tax law requires.

We rely on contract to give you the service you signed up for, legitimate interests to keep Illarin secure and to act on reports, consent where you have opted in, which is how adult content works, and legal obligation where the law requires us to respond.

We do not sell your personal data, and we have no interest in doing so. It reaches:

• Our hosting provider, whose servers hold the database, the uploaded files, and the logs.
• Our email provider, which receives your address and the message when Illarin sends a verification or password-reset email.
• Datadog, our monitoring service, which receives the server logs described above.
• Discord, if you sign in or link with it, or connect a channel for announcements. A connected channel receives the public page details of what you publish.
• Ko-fi, if you support Illarin there.
• A payment provider, once Illarin takes payments, which receives what it needs to charge you or pay you.
• Apps you connect, which receive the work they are allowed to fetch.
• Anyone, for work you publish and for your profile. That is the point of publishing.
• Authorities, where the law, a court order, or a genuine safety risk requires it.

Account data lasts as long as your account. Work you publish lasts until you delete it or it is removed. Deleted work sits in a 30 day recovery window while you can still restore it, and is destroyed after that. Sign-in sessions, email verification links, password reset links, and app connection codes all expire on their own. Page view records and the counts described in 1.7 are deleted after 30 days, and the daily totals made from them are kept. The codes that keep a view or a download from counting twice are deleted at midnight UTC each day. Server logs are kept for a short rolling window. Once Illarin takes payments, payment records are kept for as long as tax law requires, even after the account is gone.

You can see and change most of your data in your account settings, including your email address, your password, your handle, your connected apps, and your content preferences. Deleting a work or your account is a normal control, not a request you have to file.

For anything else — a copy of your data, a correction you cannot make yourself, an objection, or withdrawing consent — write to team@illarin.com. If you are in California you have further rights under the CCPA and CPRA. If you are in the EEA or UK you have further rights under the GDPR and UK GDPR, including the right to complain to your data protection authority.

Illarin is not for children under 13, and we do not knowingly collect anything from them. If you believe a child has given us personal data, write to team@illarin.com and we will delete it.

Illarin’s servers, and the email, monitoring, sign-in, and payment services it depends on, operate across several countries including the United States. Using Illarin means your data travels to those places. Where the law requires safeguards for that transfer, we rely on the ones our providers put in place, such as Standard Contractual Clauses.

Passwords are hashed, never stored in readable form. Session tokens, password reset links, email verification links, and app tokens are stored as hashes too, so a copy of the database does not hand someone your account. Traffic to Illarin is encrypted in transit.

None of that makes a system perfectly secure. Use a password you use nowhere else, keep your Discord account secure, and write to team@illarin.com if you think someone has got into your account.

We may update this policy. The effective date at the top says when the current wording took effect, and for a change that matters we will say something through Illarin itself.

Privacy questions and requests go to team@illarin.com.