This policy explains what personal data this website processes and why, pursuant to the EU General Data Protection Regulation (GDPR). It covers this marketing/documentation site only — see the note on the application further down.
1. Controller
The controller responsible for data processing on this website is:
Ruben Lütke
Bahnhofstraße 27, 86666 Burgheim, Germany
Email: [email protected]
2. What we collect — and what we don’t
This is a static website. We do not use tracking cookies, analytics, advertising pixels, or third-party fonts. Beyond the sign-in cookies described in section 7 and the comment draft described in section 8, the site code stores nothing in your browser. Web fonts are self-hosted; apart from the marketplace catalog and the bot check on the upload forms, both described in section 6, nothing is loaded from a third-party server that would expose your IP address to that third party — the comments included (section 8).
Cloudflare may set strictly necessary security cookies if a visitor encounters an automated security or abuse-prevention challenge. We do not use these cookies for analytics or advertising.
Server log files
When you visit, our hosting provider automatically processes technical data that your browser transmits, stored in server log files:
- your IP address,
- date and time of the request,
- the page/file requested and the amount of data transferred,
- the referring URL, your browser type and version, and your operating system.
Purpose & legal basis: Art. 6 (1)(f) GDPR — our legitimate interest in operating a stable, secure website and defending against abuse. We do not routinely access these logs and do not merge them with other data sources; they are retained only as long as necessary for these purposes — as a rule for a few days — and in no case longer than our hosting provider’s standard log-retention period.
Contacting us by email
If you contact us by email (e.g. to exercise your rights or ask a question), we process the data you provide — your email address, your name if given, and the content of your message — solely to handle your enquiry. Legal basis: Art. 6 (1)(f) GDPR, our legitimate interest in responding. We delete this correspondence once it is no longer needed and no statutory retention obligations apply.
3. Hosting
This website is hosted by Cloudflare, Inc., 101 Townsend St, San Francisco, CA 94107, USA, and delivered through Cloudflare’s global content delivery network. Cloudflare processes the server log data described above on our behalf as a processor under a data processing agreement (Art. 28 GDPR); see Cloudflare’s Data Processing Addendum.
Because Cloudflare is based in the USA, your data may be transferred to and processed in the United States. This transfer is safeguarded by EU Standard Contractual Clauses and Cloudflare’s certification under the EU–US Data Privacy Framework, as set out in the DPA above. You can obtain a copy of these Standard Contractual Clauses from us at the contact address above, or view them in Cloudflare’s Data Processing Addendum linked above. Legal basis: Art. 6 (1)(f) GDPR.
4. TLS encryption
This site uses TLS/SSL encryption (HTTPS) to protect the transmission of any data between your browser and the server.
5. External links
We link to third-party services such as GitHub, X, Instagram and YouTube. These are plain links — nothing from these services is loaded when the page opens. Only when you follow such a link does the respective provider process your data under its own privacy policy, over which we have no influence.
6. Marketplace registry (GitHub)
The marketplace page and every profile page (section 7) load the community catalog directly in your browser from personaljarvis.github.io, a static hosting service operated by GitHub, Inc., 88 Colin P. Kelly Jr. St, San Francisco, CA 94107, USA. When one of those pages opens, your browser therefore transmits your IP address and the technical request data described above to GitHub. Legal basis: Art. 6 (1)(f) GDPR — our legitimate interest in showing the current community catalog without operating our own server infrastructure. GitHub may transfer this data to the USA; GitHub participates in the EU–US Data Privacy Framework. See GitHub's privacy statement.
The publish form validates your entries in your browser. When you press "Publish" while signed in, your submission is transmitted to our endpoint, which opens the pull request in the public registry repository for you — see section 7 for the sign-in itself.
Uploading a wallpaper takes the same route: the image file, the title and description you type and the license you choose go to our endpoint, which publishes them the same way. A published wallpaper carries your GitHub username as its author — that is what publishing it means.
Bot check (Cloudflare Turnstile)
Both upload forms are guarded by Cloudflare Turnstile, so that a script cannot flood the registry with submissions. These two pages are the only ones that load it, from challenges.cloudflare.com: opening such a form transmits your IP address, your browser data and interaction signals to Cloudflare, Inc., which may store a strictly necessary cookie for the check. Turnstile answers one question — "is there a person here?" — and serves nothing else: no profile, no recognition across websites, no advertising.
Legal basis: Art. 6 (1)(f) GDPR — our legitimate interest in keeping an upload path open to everyone without a bot filling the registry. The cookie is strictly necessary for the function you asked for and is therefore consent-exempt under § 25 (2) TDDDG. On the transfer to the USA, the same applies as in section 3; see Cloudflare's Data Processing Addendum.
7. Signing in with GitHub (publishing)
Publishing to the marketplace requires signing in with your GitHub account — it is the identity that owns your listing. When you press "Sign in with GitHub" you are redirected to github.com; after you authorize there, GitHub transmits your public profile to us: your numeric account id, username, avatar URL and account creation date. The sign-in requests no access to your repositories or any other account data.
We store none of this on a server. Your identity lives solely in a signed session cookie (pj_session) in your browser — httpOnly, valid for 30 days. A second short-lived cookie (pj_oauth_state, 10 minutes) protects the sign-in against request forgery. Both are strictly necessary for the sign-in you explicitly request and are therefore consent-exempt under § 25 (2) TDDDG; they are not used for tracking of any kind. The temporary GitHub access token is discarded immediately after the identity check — it is never stored and never reaches your browser. The only exception is writing a comment, which is described in section 8.
When you publish, your GitHub username and numeric account id become part of the public registry entry (the ownership record and the pull request) — that is the purpose of publishing. To limit abuse, we reject accounts younger than a minimum age and rate-limit submissions per account. Legal bases: Art. 6 (1)(b) GDPR for sign-in and publishing (performance of the service you request), Art. 6 (1)(f) GDPR for the abuse checks. You can sign out at any time — the session cookie is deleted immediately and expires by itself after 30 days at the latest.
Publishing also creates a public profile page on this website at /marketplace/u/<your GitHub username>. It shows your username, your GitHub profile picture (our server fetches it and passes it on, so GitHub does not learn the reader’s IP address — see section 8), the listings you published (read from the registry in the reader’s own browser, section 6), the counters under them, a karma figure (section 9) and a list of the listings you commented on. All of it is assembled from what is already public; nothing new about you is stored to build it. Legal bases: Art. 6 (1)(b) GDPR for the parts that follow directly from publishing, Art. 6 (1)(f) GDPR for collecting them onto one page, which is our legitimate interest in letting a reader see who stands behind a listing.
8. Comments (GitHub Discussions)
Every listing page has a comment section. The comments live in GitHub Discussions in our public registry repository, and this website displays them itself. Reading them contacts nobody but us: our server fetches the thread from GitHub and passes it to your browser, so no comment widget, iframe or other third party is loaded and GitHub does not learn your IP address while you read. The profile pictures next to the comments are fetched by our server for the same reason.
Writing a comment requires a GitHub account. When you press "Comment" we send you to github.com once, so that GitHub can give us permission to post in your name. That permission is stored encrypted in a separate short-lived cookie (pj_write, httpOnly, 15 minutes) and is used for nothing else; it is deleted when you sign out and expires by itself. While you are typing, your unsent text is kept in your browser's session storage (pj-comment-draft:…) so that this redirect cannot lose it — it never leaves your device and is removed once the comment is posted.
Your comment is published in GitHub Discussions under your own GitHub account and is public, including your username. You can edit or delete it on GitHub at any time, and GitHub's terms and moderation apply to it there.
A profile page also lists where and when you commented — the listing, the date and the score, with a link to your comment. It never shows the text of a comment and never keeps a copy of one; the list is read from GitHub and held for at most five minutes, so a comment you delete on GitHub disappears from it within that window.
Legal bases: Art. 6 (1)(f) GDPR for showing the comments (our legitimate interest in putting questions and warnings about a listing where the listing is), and Art. 6 (1)(b) GDPR for posting one (performance of the service you requested). The cookies and the draft above are strictly necessary for exactly the function you asked for and are therefore consent-exempt under § 25 (2) TDDDG. When you post, GitHub processes your comment as the operator of Discussions under its own privacy policy.
9. Votes, views and install counts
Listings and comments can be voted on, and we count how often a listing is viewed and installed. These numbers live in a database we operate ourselves (Cloudflare D1, Western Europe).
A vote requires a sign-in, because one account may cast one vote. We therefore store, per vote, your numeric GitHub account id, what you voted on (a listing key or a comment id), whether it was up or down, and when. No username, no email, no IP address — and no reader ever sees who voted, only the totals. Withdrawing a vote (pressing the same arrow again) deletes the row. Views and install counts are plain counters and carry no identity at all. Your own profile page can show you the listings you voted on; that list is put together for you alone, is never cached, and is never shown to anybody else.
A profile page shows a karma figure: the upvotes minus the downvotes on the listings that person published and on the comments they wrote. Karma names the person the votes were cast for, never the people who cast them. It is recalculated from the public totals every time a profile is opened and is not stored anywhere. Legal basis: Art. 6 (1)(f) GDPR — our legitimate interest in a store where a reader can see how a publisher’s work has been received.
Legal bases: Art. 6 (1)(b) GDPR for the vote you cast (performance of the service you requested) and Art. 6 (1)(f) GDPR for the counters and for tying a vote to an account, which is our legitimate interest in a score that cannot be manufactured in a loop. You can have your votes deleted at any time — see section 11.
10. The Personal Jarvis application
The Personal Jarvis software runs on your own machine, with your own API keys. It does not send your voice, conversations, files, or credentials to us — this website operator receives no application data of any kind. Any AI providers or tools you connect (e.g. Anthropic, OpenAI, Google, OpenRouter) process your data under their own terms and privacy policies, which you accept directly with them. See the Terms & Disclaimer.
11. Your rights
Under the GDPR you have the right to:
- access (Art. 15), rectification (Art. 16) and erasure (Art. 17) of your data,
- restriction of processing (Art. 18) and data portability (Art. 20),
- object to processing based on legitimate interests (Art. 21), and
- lodge a complaint with a supervisory authority (Art. 77).
To exercise any of these rights, contact us at the email address above.
Deleting your votes changes the karma figures of the people you voted on, and removing your listings removes them from your profile page.
If you want your profile page removed, write to the address above. The page is not stored anywhere: it is built on request from your registry entries and your comments, so it disappears once those are gone. We take the listings out of the registry; comments you can delete yourself on GitHub at any time.
The supervisory authority competent for us is the Bayerisches Landesamt für Datenschutzaufsicht (BayLDA), Promenade 27, 91522 Ansbach, Germany. You may also lodge a complaint with the supervisory authority of your habitual residence or the place of the alleged infringement.
Right to object (Art. 21 GDPR): You may object at any time, on grounds relating to your particular situation, to processing based on Art. 6 (1)(f) GDPR. We will stop that processing unless we can demonstrate compelling legitimate grounds that override your interests, rights and freedoms, or the processing is required for the establishment, exercise or defence of legal claims.
12. Changes
We may update this policy to reflect changes to the site or legal requirements. The effective date at the top of the page indicates the current version.