Privacy Statement

1. Who are we?

Siendr is an online marketplace for sports video clips. People film matches, put the clips here, and players buy the footage of themselves. We also run a closed tournament gallery where photos and videos from a tournament are shared with the teams that were there.

Siendr is a sole proprietorship and is the data controller for all personal data processed through the platform. In practice that is one person. There is no data protection officer and no support department: if you email us, Louie Jay reads that email himself.

Trade name: Siendr
Legal form: sole proprietorship of Louie Jay Sienders
Dutch Chamber of Commerce: 80020712
VAT number: NL003382223B24
Country: The Netherlands
Email: louiejaysienders@gmail.com

That email address also receives our own internal notifications. So it is not a separate privacy desk, but it is the address where every request actually arrives and gets read.

2. Whose data do we process, and what?

Buyers

• Email address: the one you enter at checkout. Without it we cannot deliver your download.
• Payment source: we store no card number and no full IBAN, but we do store what Stripe reports back after the payment. For iDEAL that is the name the bank account is held under plus the last four digits of the IBAN. For a card it is the brand plus the last four digits.
• A fingerprint of the payment method: a short code that stays the same for the same account or card. It lets us see that two orders were paid with the same method, even under different email addresses. We use it to check whether a creator is buying their own clips.
• Tax country: the country Stripe establishes at checkout, because we have to charge the right VAT rate.
• Download key: a code in the link you use to collect your purchase.
• Withdrawal: if you ask for your money back within fourteen days, we record the time of your request on that order.
• Gifts: if you buy a clip as a gift, we store the recipient's email address and the message you write with it on your order.

Creators (videographers)

• Name and email address: provided when you apply. Required for account management.
• Business details: company name, VAT number, Chamber of Commerce number and invoicing address, if you switch on self-billing. Needed to produce a correct invoice.
• Instagram handle: if you enter one yourself, for your profile page.
• Date of birth: asked when you apply, so we know whether you are a minor. See section 9.
• Name and email of a parent: only if you are under eighteen when you apply, plus the exact consent text the parent confirmed.
• Your Stripe account: only the identifier of the account you hold at Stripe. You enter your banking details directly with Stripe. We never see or store your IBAN.
• Upload data: title, description, sport, date, location and file information for your clips.
• Last seen: we record when you were last in your dashboard, so we can see who is active.

Players and other people visible in a clip

• The footage itself: a sports clip is footage of recognisable people. Besides the player it is about, there are almost always teammates, opponents, referees and spectators in frame.
• Name, jersey number and team: of players linked to a clip. That name often ends up in the clip title as well, and players get their own page on the site.
• Note: most of these people never signed up with us and never gave us anything. How to ask for removal is in section 8.

Participants in the tournament gallery

• When you register: first name, last name, role (player, parent, coach or other), jersey number, email address and a password. We also record which team code you came in with and whether your registration was approved.
• If a parent registers: they enter their child's first and last name, so the gallery can show the right footage. That child entered nothing themselves.
• The footage: photos and videos from the tournament, in which players, coaches and spectators are recognisable. Some of them are children.
• What you do in the gallery: we record which photo or video you download or mark as a favourite, linked to your registration. We use that to see whether the gallery works and to be able to trace misuse.
• Jersey numbers on photos: to link footage to the right player, we have the original tournament photos scanned for jersey numbers. See section 5 and section 10.

Gift recipients and people following a player

• If someone gifts you a clip: we have your email address because the buyer entered it. You get an email with the clip, the buyer's message and the buyer's email address in it, so you know who it is from. Your address sits on that order and therefore falls under the seven-year tax retention period. If you want it removed, email us.
• If you follow a player: we keep your email address with that player, so we can email you when there are new clips. That email contains the player's full name. Every such email has an unsubscribe link at the bottom that genuinely deletes the follow.

All visitors

• Searches: what was typed, how many results it returned and the time. Plus country, region and city, the time zone and the coordinates of that city centre. Our hosting provider Vercel derives that location from the IP address of the request. The search log itself holds no IP address, no account and nothing that links searches to each other. We use it to see what people look for without finding it.
• Clip views: we count how often a clip was viewed and where the visitor came from, and the latter only as a category: direct, Instagram, Google, and so on. No IP address, no account.
• Rate limiting: to prevent abuse we count how often the same device performs a given action. Since September 2026 we no longer store the IP address itself for this, but an encrypted fingerprint of twelve characters. The same visitor produces the same fingerprint, but the address cannot be reconstructed from it. The old rows with readable IP addresses have been deleted. If you request a new password, your email address also goes into that counter in hashed form.
• What does see an IP address: Vercel sees every request and therefore every IP address, because a website cannot work otherwise. If you log in, Supabase Auth stores the IP address and your browser details with that session. That happens inside Supabase's own session management, not in our tables. And on every page the site opens a connection to Supabase for the counter of visitors currently online, which means Supabase also sees the IP address of people who never log in.

3. Legal basis for each processing activity

• Performance of a contract (Art. 6(1)(b) GDPR): processing purchases, delivering download links, delivering a gift to its recipient, paying out creators, managing accounts, and granting access to the tournament gallery.
• Legal obligation (Art. 6(1)(c) GDPR): keeping orders and invoices for seven years for the Dutch tax authority, charging the right VAT rate, and having a creator's VAT number verified by the European Commission.
• Consent (Art. 6(1)(a) GDPR): following a player, where you leave your email address yourself, and the tip emails for creators. Both have an unsubscribe link. For creators under eighteen, parental consent applies as well, see section 9.
• Legitimate interest (Art. 6(1)(f) GDPR), abandoned purchases: if you start checking out and do not finish, we keep your email address and the clip you wanted so we can remind you once. That interest outweighs your privacy interest because you had just entered that address to make the purchase, we send at most one message, and the data disappears automatically after sixty days.
• Legitimate interest (Art. 6(1)(f) GDPR), searches: logging search terms with a city-level location, to see which sports and places there is demand for that we do not yet serve. That interest outweighs your privacy interest because the search log holds no IP address and no account, the location is no more precise than a city, no profile is built, and the rows disappear automatically after twelve months.
• Legitimate interest (Art. 6(1)(f) GDPR), security and abuse: counting requests per device, checking uploads for inappropriate imagery, and keeping a fingerprint of the payment method to see whether someone is buying their own clips. We keep this as small as we can: the counter stores an encrypted fingerprint instead of an IP address and is cleared after thirty days.
• Legitimate interest (Art. 6(1)(f) GDPR), the platform itself: showing sports footage and linking player names to it, so a player can find their own footage. This affects people who never signed up. That is why section 8 explains how to object or ask for removal, and why we weigh that request more heavily than our wish to show the clip.
• What had no valid basis: the face profiles of twenty youth players. That requires explicit consent and it was never asked. The processing has therefore been stopped. See section 10.

4. Retention periods

A retention period that exists only on paper is not a retention period. The periods below marked “automatically” are genuinely carried out by a weekly clean-up job.

• Searches: twelve months, then deleted automatically. Twelve months so we can compare a full season with the previous one.
• Abandoned purchases: sixty days, then deleted automatically.
• Rate limit keys: thirty days, then deleted automatically. The window such a counter measures is at most an hour, so longer serves no purpose.
• Clip view rows: ninety days, then deleted automatically. The total counter on the clip stays.
• Tournament gallery activity log: ninety days, then deleted automatically. This is who downloaded or favourited what.
• Re-downloading your purchase: 365 days after the purchase. Thirty days before it ends you get an email about it. After that you can no longer collect the clip, while your order details are still kept for tax purposes.
• Orders: seven years after the purchase date, under Dutch tax retention law. They contain your email address, the amount, the country, the payment source and, for a gift, the recipient's address and message.
• Account data: as long as your account exists. There is no button in the site to close your account. If you ask by email, we do it by hand, after which anything covered by tax retention law stays for seven more years.
• Creator banking details: these sit with Stripe and not with us; the policy Stripe applies governs them.
• A removed clip: we are honest about this one. If a creator takes a clip down, it disappears from the site, but the data about the clip stays in our database. The video files are only truly deleted if the clip was never sold. If it was sold, the files stay for as long as buyers may still download it.
• Tournament registrations: these are not cleaned up automatically. If you ask for removal, we do it by hand.
• Notifications to ourselves: when someone requests removal of a clip, that arrives as a notification with the email address they entered. Those notifications are currently not cleaned up automatically.
• Face profiles: see section 10. Those of twenty players still exist and currently have no retention period.
• At our suppliers: how long Stripe, Resend, Cloudflare, Vercel and Supabase keep their own logs is not up to us. Resend, for example, keeps a readable archive of sent mail, with recipient and subject line.

5. Who do we share data with?

This is the list of every party that receives personal data from us, with the country the company is based in and exactly what goes there. We never sell your data, and there is no advertising or analytics party on this list.

• Stripe (United States): payments and payouts. At checkout your email address, the amount and the clip title go to Stripe. That title often contains a player's name. For a gift, the recipient's email address and message go too. For a payout, the creator's name goes along. Checkout itself happens on Stripe's own page, where Stripe processes your payment details, your IP address and its own fraud signals.
• Supabase (US company, database in Ireland): our database and login. Almost everything in this statement ends up here. The database runs on AWS in region eu-west-1, Ireland. Supabase Auth also stores the IP address and browser details for each logged-in session. On every page the site keeps a connection to Supabase open for the counter of visitors currently online, which means Supabase sees every visitor's IP address.
• Vercel (US company, execution in Dublin): hosting the website. The server functions run in Dublin and requests are first received in Frankfurt. Vercel sees every request and therefore every IP address. To be honest about it: if an email fails, the recipient address and the subject line end up in Vercel's logs, and such a subject line can contain a player name or a clip title.
• Cloudflare R2 (US company, storage in Western Europe): all files. Videos, previews, watermarked versions, thumbnails, profile pictures, team and sponsor logos, and the tournament gallery photos. Uploads go straight from the browser to Cloudflare, so the file never passes through our web server.
• Resend (United States): all outgoing email. So not just download links and confirmations, but also gift emails, reminders about an abandoned purchase, alerts that there are new clips of a player, consent requests to parents and withdrawal confirmations. Resend keeps the sent messages and they can be read back, with recipient and subject line. We do not know which region this account runs in.
• Google Cloud Vision (United States): two things. First, we check every clip a creator uploads for inappropriate imagery. We send the link to the thumbnail, after which Google fetches that image itself. Second, we have the original tournament photos scanned to read jersey numbers, so a photo can be linked to the right player. For that, Google gets a temporary one-hour read link to the original photo. Both cases involve footage of athletes, and some of them are children.
• Google Gemini (United States): every day we have the text of eight public calendar pages of sports federations summarised, to see where matches are played. No data about buyers, creators or players goes there; only the text of those public pages.
• Our own render server (at Netcup in Vienna, Austria): since September 2026 a server of our own produces the previews, the watermarked versions and the short homepage videos. That server fetches the original video files, processes them and puts the result back. It has access to the storage and the database to do so.
• European Commission (EU): if a creator switches on self-billing, we send the VAT number to the Commission's verification service to check that it exists. Nothing beyond that number goes there.
• unpkg.com (United States): on the upload page and a few admin pages your browser fetches a video module from this public library. In doing so, unpkg sees that user's IP address and browser. Your video file stays on your own device. Ordinary visitors never touch this.

6. Transfers outside the EU

Our main suppliers are US companies, but the storage and processing themselves take place in Europe. The Supabase database sits in Ireland, the Vercel server functions run in Dublin with requests first received in Frankfurt, the Cloudflare storage sits in Western Europe, and our own render server is in Vienna. That means your data is physically in the EU, and at the same time that the US parent company can in principle reach it. The latter still makes it a transfer in legal terms.

The parties where data genuinely leaves the EU are Stripe and Resend, and Google. With Google it is imagery: the thumbnail of a clip being checked for inappropriate content, and the original tournament photo being scanned for jersey numbers.

For these transfers we rely on the EU-US Data Privacy Framework where the party is certified for it, and otherwise on the European Commission's Standard Contractual Clauses. If you want to know which basis applies to a particular party, email us and we will look it up for you.

7. Cookies and local storage

If you visit the site without logging in and without switching language, we set zero cookies. There are two in total, and both only appear after an action by you.

• locale: remembers whether you want the site in Dutch or English. Only set when you click the language button yourself. Lasts 365 days and contains nothing but “nl” or “en”.
• The Supabase Auth login cookie: keeps you logged in. Only set when you log in or create an account. The Supabase default keeps it for 400 days, and the cookie is readable by JavaScript on the page. That is the default of the library we use and we have not changed it.

Stripe sets nothing on siendr.com. No Stripe script runs on our site. When you click checkout you go to checkout.stripe.com, and there Stripe sets its own cookies on its own domain.

Local storage on your own device

In four places the site stores something in your browser's local storage. That is not a cookie, it is never sent to us, and we cannot reach it. It covers: whether you dismissed the notice at the bottom, the clips you saved, your recent searches, and on the upload page the draft of an upload plus whether you dismissed the roadmap. Clear your browser storage and it is gone.

No tracking, and you can see it

There is no Google Analytics, Tag Manager, Meta pixel, Plausible, PostHog, Hotjar or Clarity on this site. Not a single script comes from another domain: everything is loaded from siendr.com. We serve the fonts ourselves too, so your browser makes no request to Google Fonts. There is no ad network and no profile is built about you.

What does happen: on every page the site opens a connection to Supabase for the counter of visitors currently online. Nothing is stored from it, but it does mean Supabase sees every visitor's IP address.

The notice at the bottom of the screen is not a consent request. There is nothing to refuse because there is no tracking, and functional cookies do not require consent. That notice is currently only in English.

8. Footage and image rights

The heart of Siendr is footage of people. If you are recognisable in a clip, we process personal data about you, even if you never entered anything with us. That applies to the player the clip is about, but equally to teammates, opponents, referees and spectators.

What of a clip is publicly visible:

• The preview version and the watermarked version sit publicly on our file server. That is the shop window: without it nobody can see what they are buying.
• The full paid video is not public. It is locked down and can only be downloaded with a valid purchase.
• The video on the homepage is a three-second fragment without sound, not the whole clip.
• A clip title often contains a player's name, and players have their own page with their name, jersey number and team. That title also goes to Stripe as the product name when someone buys.
• The photos and videos in the tournament gallery are not public. Since September 2026 even the small preview versions are served only through a temporary one-hour link, and they are blocked on the file server.

Asking for removal: that is me, take it down

Every clip page has a button to request removal. You enter your email address and, if you want, an explanation. To be honest about it: that does not take the clip offline immediately. A single button that lets anyone take down any clip is too easy to abuse, so we review it by hand. The request reaches us as a notification and as an email. Your email address stays with that notification.

There is no deadline built into the system to enforce this. We aim to respond the same day and in any case keep to the one month stated in section 12. If you appear in footage in the tournament gallery, or it concerns a child, email us directly at louiejaysienders@gmail.com. We take footage down at the request of the person in it, or their parent. We do not ask for proof of identity when the request itself already makes clear who it is about.

9. Minors

We film youth sport, so there are children in our footage and there are children with accounts of their own. This is what is arranged and what is not yet.

The tournament gallery

• You only get in with a team code, and on top of that every registration has to be approved by us. Both are required; a code alone is not enough.
• The photos and videos themselves are locked down. The original, the preview and the small version are served only through a temporary one-hour link and are blocked on the file server.
• We record for ninety days who downloaded or favourited what.
• Honest about what is missing: at registration we do not ask for a date of birth and we run no age check. So a child can register with their own email address and tick their own box, without parental consent being asked. We do not know which of those registrations belong to minors.
• If a parent registers, they enter their child's first and last name. That child had no say in it.
• If you are a parent or guardian and you want your child's data or footage gone, email us. We do that without asking questions back.

Creators under eighteen

• When applying as a creator, a date of birth is required. If you are under eighteen, we ask for a parent's name and email address and send that parent a consent email. If the parent confirms, we record not just the confirmation but the exact text that was agreed to, so a later change to that text cannot appear to apply retroactively.
• Honest about what is missing: that consent is currently not enforced. Uploading and selling are not blocked while the parent has confirmed nothing. And if we create a creator by hand ourselves, no date of birth is asked and the system silently treats that person as an adult.

If you are a parent or guardian with a question about this, or you want us to undo something, email louiejaysienders@gmail.com.

10. Face recognition

We have used face recognition and we have stopped. This is what happened.

To link tournament photos to the right player automatically, we trained a face profile for twenty players on the tournament roster: a series of numbers derived from their face, which lets that same face be recognised in another photo. The recognition itself ran in the browser, with models hosted on our own server. So no face was ever sent to an external service.

Such a profile is special category data (Art. 9 GDPR) and is only allowed with explicit consent. For children that means a parent's consent. That consent was never asked, and it was not in the previous version of this statement either. That was wrong.

What we have done:

• Face recognition is switched off. Both using and training profiles is stopped until consent is arranged.
• The face profile column on the general players table has been emptied and removed. Those profiles no longer exist.
• The profiles of the twenty players on the tournament roster still exist and are no longer used for anything. Only our server can reach them; they cannot be retrieved through the site.

What we still have to decide: whether those twenty profiles are deleted or whether we ask for consent after all. If you are on that roster, or the parent of someone who is, and you want the profile deleted now, email us. We will do it straight away.

For clarity: reading jersey numbers on photos is a different thing. That reads digits on a shirt, not faces. For that, the original tournament photos do go to Google, see section 5.

11. Automated decision-making

No decision about you is taken fully automatically that has legal effects or similarly significantly affects you (Art. 22 GDPR). Every decision that means something for you has a human looking at it. That is easy to keep up, because that human is one person.

What does happen automatically, so you have the full picture:

• Every clip a creator uploads is automatically checked for inappropriate imagery. A hit puts a flag on it; removing or approving is done by hand.
• Jersey numbers on tournament photos are read automatically. That produces a suggestion for which player is in the photo. The link is confirmed by hand.
• On payment we keep a fingerprint of the payment method used. It lets us see that different orders were paid with the same account or card, even under different email addresses. We use it to check whether a creator is buying their own clips. That is a manual check, but it does link data across purchases, which is why we mention it here.
• The search engine and the ordering on the homepage determine which clips you see first. That is ranking of footage, not a decision about you.
• Face recognition would have been a form of automatic identification. It is switched off, see section 10.

12. Your rights, and how to use them

Under the GDPR you have the following rights:

• Access (Art. 15 GDPR): request what data we hold about you.
• Rectification (Art. 16 GDPR): have inaccurate data corrected.
• Erasure (Art. 17 GDPR): have your data deleted, where no legal retention obligation applies.
• Restriction (Art. 18 GDPR): have processing halted in certain cases.
• Portability (Art. 20 GDPR): receive your data in a structured format.

How it works in practice

There is no button in the site to download a copy of your data or delete your account. That does not exist and we would rather not talk around it: access, correction and deletion are done by hand, after you email us. We respond within one month, as the GDPR requires. For a request that is not self-evident, we may ask you to confirm it is you.

What you can do yourself, without us:

• View your own purchases on the purchases page, using the link from your purchase email or by logging in.
• As a creator, see your clips, sales and payouts in your dashboard.
• Unsubscribe from the emails about new clips of a player, using the link at the bottom of that email. It genuinely deletes the follow.
• As a creator, unsubscribe from the event tip emails, using the link at the bottom of that email. Messages about your own sales and payouts will keep coming, because those are part of the service.

One thing is not possible, and we would rather say so than hide it: objecting to the search log achieves nothing. That log holds no IP address and no account, so there is nothing by which your rows could be found. Those rows disappear on their own after twelve months.

Withdrawing a purchase: within fourteen days of purchase you can ask for your money back. We record the time of your request on your order and you get a confirmation. The refund itself we do by hand through Stripe.

To exercise a right, email louiejaysienders@gmail.com with the subject “GDPR request”. Include your name and the email address you used with us.

13. Complaint to the Dutch Data Protection Authority

If you think we are not handling your personal data properly, we would prefer to hear it from you first so we can put it right. But you do not have to wait for us: you can always file a complaint directly with the Dutch Data Protection Authority.

Autoriteit Persoonsgegevens
PO Box 93374, 2509 AJ The Hague, Netherlands
www.autoriteitpersoonsgegevens.nl

14. Security

This is concretely what is in place, without dressing it up.

• All connections run over HTTPS. The site enforces that, so a browser cannot accidentally reach it unencrypted.
• We do not store passwords ourselves. They sit encrypted at Supabase Auth and we cannot view them.
• Access is role-based: a buyer sees their purchases, a creator their own clips and sales, and only an administrator sees the admin area.
• The paid videos and all tournament gallery imagery are not public on the file server. They are served only through a temporary one-hour link, and are blocked on the CDN.
• The team codes and the tournament roster with face profiles can only be retrieved by our server, not through the site's public key.
• The IP address is no longer readable in our rate counter, but stored as an encrypted fingerprint. The old rows have been deleted.

What we will honestly add:

• The previews and watermarked versions of ordinary clips are public. That is deliberate: it is the shop window.
• Our render server runs with the same keys as the website. Anyone who gains access to that machine can also reach the storage and the database.
• There is currently no Content Security Policy on the site. The other usual security headers are in place.
• We are a small operation with no security department. If you see something wrong, email us; we take it seriously and respond quickly.

15. Changes to this statement

This version 2.0 is a full rewrite. The previous version described a number of things differently from how they actually were: it said we do not store IP addresses while we did, Google and our own render server were missing from the list of parties, Supabase, Cloudflare and Vercel were listed as United States while the storage sits in Europe, and minors and face recognition did not appear at all. That has been put right, and where something is still not in order, we say so.

We may update this statement. For significant changes we notify everyone with an account by email. The current version is always at siendr.com/privacy. Questions, or something not right? louiejaysienders@gmail.com