Privacy Policy

Last updated: September 24, 2026

Pelican Benchmark is a personal project. This page describes only what the site actually does today. Features that are not switched on are not written up here as if they were already collecting data; when something changes, this page changes with it.

1. Who is responsible

This site is operated by the individual behind Pelican Benchmark. For any privacy question or request, email contact@pelicanbenchmark.com.

2. What we process

If you only browse

• Hosting and security. The site runs on Cloudflare. To deliver pages and block abuse, Cloudflare processes technical information such as your IP address, the time of the request, the path requested, and your browser and device type. We do not build any profile from it. See the Cloudflare Privacy Policy.
• Analytics. We use Google Analytics to count visits and see which pages get read. It sets cookies in your browser and records the pages you view, the site that referred you, an approximate region, and your device and browser type. We look at it only in aggregate. See how Google uses information from sites that use its services, and section 4 for how to opt out.
• Cloudflare Web Analytics. Cloudflare automatically adds a measurement script to main-site pages. It sends page-view and loading-performance information, such as the page URL, referrer, and timing, to Cloudflare. The script does not read or write cookies or other browser storage. See Cloudflare’s description of its beacon. Both analytics tools can run on public and admin pages.

Besides page views, Google Analytics receives a short list of interactions, so we can tell which parts of the site get used: opening a result, switching between the two tracks, choosing a model in the filter, copying a prompt, an animated viewer loading (and whether it loaded automatically or after you tapped the play button), copying a result’s share link, starting to fill in the submission form, and a submission going live. These events carry at most the result’s ID, the track, the model’s key from our reviewed model list (a model not on that list yet, or filed under an “Other” provider, is reported only as “other”), and how the viewer was opened. A viewer load does not prove that an animation actually played or rendered successfully. They never include a contributor’s display name, the prompt, a source link, notes, source code, or anything else typed into the submission form, and GA page addresses omit query strings and fragments (external referrers retain only their origin). Every page is reported under the same fixed title because result-page titles contain the contributor’s name.

The site stores no saved preferences or local storage in your browser.

If you open an animated result that uses external resources, your browser may load scripts, styles, fonts, or images directly from cdn.jsdelivr.net, cdnjs.cloudflare.com, unpkg.com, fonts.googleapis.com, or fonts.gstatic.com. Those services receive request details such as your IP address and browser type. Which requests happen depends on the submitted result.

If you submit a result

You do not need an account and we do not ask for contact details. We store what you put in the form: the source code of your result, the model name, the prompt, the generation method, and — if you fill them in — the generation date, a display name, a source link, and notes. If the result is published, all of it becomes public, along with the time of submission. A real name or profile link you enter may then be public too; leaving the name blank displays a published result as “Anonymous”.

Please do not put account details, keys, private conversations, or personal information about other people into any field, including the prompt and the source code.

We do not store your IP address when you submit. To enforce a submission limit per visitor, we store a salted hash of it with the time of the attempt. This is a pseudonymous identifier, not an anonymous one: the address is not stored in readable form, but someone who has the salt could match the hash to a guessed address. Rows older than 24 hours are deleted when the next submission or admin login is attempted; they may remain longer when there is no such activity.

If you contact us

If you email us about privacy, a takedown, or another concern, we receive your email address, message, and any details you include. The message is routed through Cloudflare Email Routing to our Gmail mailbox. We may keep correspondence there after answering it for follow-up; you can ask us to delete it. Please do not send information you do not want us or those email services to receive.

If you try to log in to the admin area

Admin login attempts, successful or failed, store the same kind of salted hash and time as a submission, to limit repeated guessing. After a successful login, the admin area sets one session cookie. It keeps the administrator signed in and also identifies their submissions on the public submission page: these are credited to admin and marked as seed works, which do not count as outside submissions. The cookie is not used for analytics or advertising.

3. Why we are allowed to use it

We publish your submission because you asked us to and confirmed the permission when submitting; you can withdraw it at any time by asking us to take the work down. We use the rate-limit hashes and the hosting logs on the basis of our legitimate interest in keeping the site from being flooded or abused. Analytics is not necessary for the site to work; options to limit it are described below.

4. Cookies and analytics controls

This site sets cookies in exactly two situations:

• Google Analytics (_ga, _ga_<id>) — to count visits. These are the only cookies an ordinary visitor receives.
• The admin session (pb_admin) — set only after an administrator logs in. It is HttpOnly and contains no admin password, but an active copy grants admin access and must be kept private. Visitors never receive it.

Cloudflare Web Analytics does not set cookies. To limit analytics, you can:

• install Google’s opt-out browser add-on, which blocks Google Analytics but not Cloudflare Web Analytics;
• use a content blocker configured to block both analytics scripts and their requests.

Deleting Google Analytics cookies removes stored identifiers, but a later visit can create new ones. Blocking cookies alone does not stop Cloudflare Web Analytics or necessarily stop Google Analytics measurements. Blocking analytics does not affect your ability to browse or submit.

5. Who else sees it

We do not sell your information and we do not share it for advertising. It reaches these service providers only:

• Cloudflare — hosting, database, file storage, Web Analytics, Email Routing, and the headless browser that takes the cover screenshot of your result.
• DeepSeek — we send the rendered image of a submitted result to its vision model for automated screening, so obviously unsuitable content does not get published. Only the image is sent, not the form fields, and nothing is sent when you merely browse.
• Google Analytics — the browsing data described above.
• Gmail — stores messages sent to our contact address. Email delivery passes through Cloudflare Email Routing.
• External resource hosts — jsDelivr, cdnjs, unpkg, and Google Fonts may receive browser requests when an animated result uses their resources, as described above.

These providers store and process data outside your country, including in the United States and China, under their own policies. We may also disclose information if the law requires it.

6. How long we keep things

• Published submissions: until they are removed, by you or by us.
• Rejected and removed submissions: their records and source files may be kept privately afterwards to handle reports and prevent the same content being resubmitted.
• Rate-limit hashes: records older than 24 hours are removed on the next submission or admin login attempt; without one, they can remain longer.
• Contact emails: we do not promise a fixed deletion date. We may keep messages for follow-up, and you can ask us to delete yours.
• Google Analytics: for as long as the retention period configured in our Google Analytics property, after which Google deletes the underlying records; aggregate reports remain.
• Cloudflare Web Analytics: Cloudflare says it keeps unsampled beacon data for seven days and retains aggregated, sampled data longer. See its retention explanation.

7. Your choices and rights

Depending on where you live, you may have the right to ask for a copy of your personal information, to have it corrected or deleted, or to object to how we use it. In practice the main thing we hold about you is your public submission, and you can ask us to take it down or correct it at any time. Email contact@pelicanbenchmark.com with the link to the page. Because there are no accounts, we may not be able to connect a request to a submission unless you can identify it.

8. Security

We take measures proportionate to the size of this site, but no method of transmission or storage over the internet can be guaranteed secure.

9. Children

This site is not directed at children. If you believe a child has submitted personal information, email us and we will remove it.

10. Changes

When the site’s features or service providers change, we update this page and the date at the top. A change that matters will not be buried under wording left over from an older version.

11. Contact

contact@pelicanbenchmark.com

See also our Terms of Use.