1.Who is responsible
Shortformia (“Shortformia”) is the controller for our website, partner program and creators’ accounts. For the data of a community’s members, the creator is the controller and we process it for them under our Data Processing Addendum.
2.What we collect
From Whop: your user ID, username, display name and avatar, and the community you use the app in. From Discord or Telegram: your user ID, username and display name (and your Discord avatar).
What you post: the win title, amount, category, optional quote and the redacted or blurred screenshots or photos (up to 4 per post: one on the card, the others kept as proof for the community's team only). For links: click counts, platform tags and Whop referral events.
Card backgrounds you upload (a community’s Signature background, or a member’s own when the community allows it): the image and the finished, card-size versions. They are stored publicly, like a logo, because they appear on shared cards. Removing one deletes its files.
Joins through a member’s link: the new member’s user ID and name on that app, whether they’re still in, and what they pay through the link, so the right member gets the credit.
Billing: your plan, its status and the amounts paid, as reported by Whop. We never see or store card numbers.
3.Website visitors, support and partners
If you contact support, we use your name, email and message to answer you.
If you apply as a partner, we store your name, email, channel, audience and what you wrote, and later your payout details and the stats of communities credited to you. We keep a hashed IP address of applications to stop abuse.
When someone opens a partner link, we store a hashed IP address (see below), the time and the referring page, to count the click. Which partner sent you is remembered in a cookie only if you allow referral cookies.
4.How we use it and why we may
To provide the service: make cards and videos, show stats and leaderboards, credit sign-ups to the right win, and run the partner program (contract).
To keep it safe and working: prevent fraud and abuse, fix problems and improve the service (legitimate interests).
To remember a partner referral in a cookie (your consent, which you can withdraw at any time in Cookie settings), and to keep records tax and accounting law requires (legal obligation).
We don’t sell data and we don’t use it for advertising.
5.Screenshots and redaction
On Whop, the privacy brush runs on the member’s phone. Only the redacted image is uploaded; the original never leaves the device.
On Discord and Telegram, a screenshot is downloaded once and personal details (names, emails, account and order numbers) are blurred on our servers. Only the blurred copy is stored, and the original message is deleted from the chat.
To read the result (the kind of win, the amount, the date), the blurred copy is sent to Anthropic’s AI. The original screenshot never is.
A small fingerprint of the original is kept to detect reused screenshots.
On a photo win (a car, for example), the member can blur anything they want on it themselves, through a private link only they get. The AI may point out number plates it sees, but nothing is blurred unless the member chooses to. Their edit is kept next to the photo, and they can go back to the photo as it was.
6.Shortformia Wins for Discord
When a server adds the bot, we store the server's ID, name and icon, and the channels the admins pick in /wins setup.
The bot only acts on images posted in the server's chosen wins channel. Such a screenshot is downloaded once and personal details (names, emails, account and order numbers) are blurred on our servers; the blurred copy is then read to find the result. Only the blurred copy is stored; the original message is then deleted from Discord. Messages in other channels and text-only messages are not stored.
For the member who posted it we store their Discord user ID, username, display name and avatar, and the message text as the card title. The card is posted in the channel and sent to the member in a direct message.
Admins and members can log in on the web with “Log in with Discord” (scopes: identify and guilds). We use your server list only to find which servers with Shortformia Wins you manage (for the dashboard) or are a member of (for your own wins), keep that in a signed cookie for 24 hours, and never store your Discord token or your full server list.
7.Shortformia Wins for Telegram
When a group adds @ShortformiaBot, we store the group’s ID and title, the topic chosen in /setup, and the Telegram IDs of its admins.
The bot only acts on images posted in that topic. Such a screenshot is downloaded once, personal details are blurred, only the blurred copy is stored, and the original message is deleted from the group.
For the member who posted it we store their Telegram user ID, name and username. Each member gets their own invite link to the group; when someone joins through it, Telegram tells us which link was used, and we store the new member’s Telegram ID and name to credit the right member.
Admins open the dashboard through a one-time link the bot sends them in private. We never see or store a Telegram password or login code.
8.Connected accounts
Members can connect their Discord and Telegram accounts within one community, so their wins and credit count together. Either account can be disconnected at any time, and each keeps its own wins.
9.Clicks and hashing
When a link is opened we store a salted hash of the IP address that changes every day, plus the user agent and platform tag.
The IP address itself is never stored, and the hash can’t be turned back into it.
The same goes for “Want this for your community?” links under cards and on wins pages: we count where the click came from, with that hash, and set no cookie.
10.Sub-processors
Supabase (database and storage, EU), Vercel (hosting, EU functions), Whop (sign-in, billing, affiliates), Anthropic (AI reading of blurred screenshots, and caption text; never the original screenshot), Discord (for servers that use the bot), Telegram (for groups that use the bot) and Railway (the Discord bot’s connection; it passes messages through and stores nothing).
11.International transfers
Our database is in the EU. Some sub-processors are based in, or reach data from, other countries such as the United States. Where that happens, the transfer is covered by an adequacy decision, such as the EU-US Data Privacy Framework, or by standard contractual clauses.
12.How long we keep it
Community data stays while the community uses the service. Creators can delete a community’s data from the dashboard, and members can delete their own.
Support messages are kept as long as needed to help you. Partner data is kept while you are a partner; records of commissions and payouts are kept as long as tax and accounting law requires (usually up to 7 years).
13.Security
Row-level security on every table, server-only database access, signed and HTTP-only session cookies, an append-only audit log, screenshot redaction and hashed click data. No system is perfectly secure; if a breach affects you, we tell you as the law requires.
14.Children
The service is not meant for anyone under 16, and we don’t knowingly collect data from them. If you think a child’s data reached us, contact us and we delete it.
15.Your rights under GDPR
You can access, export, correct or delete your data, object to or restrict how we use it, and withdraw consent at any time. Members do this from the app’s settings; creators from the Compliance tab; anyone else through the support page.
You can also complain to your local data protection authority.
16.Changes
When we change this policy, we update the date above and, for material changes, tell creators and partners first.
17.Contact
Privacy questions can be sent through the support page.
Questions? Contact support.