privacy policy

1. who is responsible

the controller within the meaning of the gdpr is Dominik Scheidel, c/o Postflex #5812, Emsdettener Str. 10, 48268 Greven, Germany. email: [email protected]. more in our imprint.

2. the short version

• yapcap stores counts and metadata, never the text of messages.
• it never counts how long anyone is online.
• any member can opt out with /privacy, which also deletes their data.
• a server's data is deleted 7 days after yapcap is removed.
• we don't sell data and don't use it for advertising.

3. what the bot counts

for each member, per day and per channel, in the server's local time:

• messages sent (and at which hour), replies and mentions sent and received, reactions given and received, voice and streaming time
• threads, stickers, polls and poll votes, pins, server boosts, bot commands used and scheduled events attended
• who interacts with whom (replies, mentions, reactions, time in voice together), for awards like top duo
• which emoji are used as reactions, and the ids and reaction counts of the most-reacted messages, so a recap can show the message of the week
• discord ids of members, channels and the server, and the server's settings from /setup

if the server turns them on and discord has granted yapcap the matching permissions ("privileged intents"), it also counts:

• message content: what kind of message it was (image, gif, video, file, link and its site, question, all caps, a laugh, gm or gn, an edit), message length, and word totals with stopwords, links and numbers removed. the text itself is read in memory to count it and then dropped.
• server members: join and leave dates, rejoins, how often a nickname changed (stored as a hash, never the nickname), welcomes and, if the server enables it, who invited whom.
• presence: spotify tracks played and listening time, games played and playtime, and deliberate status changes (switching to do-not-disturb, changing the custom status, the custom status emoji once a day). the custom status text is never stored.

4. what the bot never stores

• the text of messages. when a recap shows a quote, it is fetched live from discord while the recap is built and is never saved.
• attachments, images or files.
• how long anyone is online, or when.
• direct messages.
• anything from members who opted out.

5. the history import

when a server runs /setup, yapcap reads its channel history back to jan 1 of the current year (in january, the year before too) and counts it under the same rules as above. message text is never stored during the import either.

6. why we may process this (legal basis)

• legitimate interests (art. 6(1)(f) gdpr): the server's admins added yapcap to show their community recaps and awards, and members can see and share their own stats. because only counts are kept and every member can object at any time with /privacy, we consider this balanced.
• contract (art. 6(1)(b) gdpr): providing and billing the yearly wrapped and pro.
• legal obligation (art. 6(1)(c) gdpr): keeping invoices and payment records as german tax and commercial law requires.

7. how long data is kept

• daily counts: 25 months, then deleted month by month.
• word and music detail: about 2 months, then folded into monthly totals (the top 100 per member), which are kept 25 months.
• opt-out: that member's data is deleted right away.
• yapcap removed from a server: all of that server's data is deleted after 7 days.
• purchase records: up to 10 years (german tax law).

8. your controls in discord

run /privacy in any server with yapcap to:

• see what yapcap counts about you
• opt out of everything, or only words, quotes, music, games or status changes, in that server or everywhere. opting out deletes the matching data.
• opt back in at any time
• export your data as a file (once a day)

9. this website

the website stores nothing on your device: no cookies, no local storage. we count visits with posthog in cookieless mode, through our own address brew.yapcap.xyz, with the project hosted in the eu (frankfurt). posthog records the pages you view, the links you click, how you arrived, browser, device type and approximate location, and counts unique visitors with an anonymous hash that changes daily. no ip address, account or discord id is stored, and visits are not linked to you. legal basis: our legitimate interest in understanding and improving the site (art. 6(1)(f) gdpr); object any time by email or by blocking brew.yapcap.xyz. events are kept up to one year. see posthog's privacy policy.

10. payments

on this website, payments are processed by stripe payments europe ltd., which receives your name, email, billing address and payment details on its own checkout page; card data never reaches us. we store your discord user id, the server id the purchase is for, the product and the stripe reference. stripe uses radar for fraud prevention. see stripe's privacy policy. purchases inside discord are processed by discord, which sends us the purchase record (user id, server id, product, period).

11. where data lives, and who helps us

• the bot, its postgresql database and our error tracking (glitchtip, self-hosted) run on servers of netcup gmbh in germany.
• stripe: payments and fraud prevention.
• posthog: cookieless website analytics, eu-hosted.
• discord: the platform yapcap runs on, under discord's privacy policy.

12. your rights

under the gdpr you can ask for access, rectification, erasure, restriction and data portability, and object to processing based on legitimate interests. most of this works instantly with /privacy; for anything else, email [email protected] and we'll answer within one month. you can also complain to a supervisory authority; ours is the landesbeauftragte für datenschutz und informationsfreiheit nordrhein-westfalen.

13. changes and contact

we update this policy when yapcap changes what it counts, and change the date above. questions: [email protected] or the support server.