Privacy
What we keep, and whose it is.
Ringske processes data in two very different roles. That distinction drives everything on this page, so it comes first.
Two roles
On ringske.be itself — this page, the homepage — we are the controller. We decide what we measure and why.
On a wedding site (for example moya-elian.ringske.be) and in its RSVP flow we are only a processor. The couple getting married is the controller there: they decide who they invite and what they ask. We store and process that data on their instructions and never use it for ourselves.
Do we measure visits?
On ringske.be we use Google Analytics to see which pages people visit, and the Meta Pixel to see whether our ads on Facebook and Instagram achieve anything. That second one is not anonymous measurement: it lets Meta recognise visitors to this site and target ads at them.
Both of them load only after you click "sure". If you decline, or click nothing at all, no script from Google or Meta is fetched — no request goes to their servers, not even one carrying only your IP address.
Changed your mind? Use Cookie settings at the bottom of every page to choose again. If you withdraw your consent, we clear the Google and Meta cookies in your browser and the tags stop loading.
The wedding sites and the RSVP flow carry no tracking tags at all, not even with consent. A couple's guests are not our visitors, and we do not retarget them. That is pinned down by tests, not by a promise.
What data do we process?
- As a wedding guest: your name, whether you are coming, to which parts of the day, and — if the couple asks — your dietary requirements or allergies. Those last ones are health data; they are used only to brief the caterer and go nowhere else.
- As a couple: your name, email address and everything you put into your wedding site, guest list and planner yourself.
Where does it live?
Everything is in the European Union. Fonts and all other assets are self-hosted — nothing is loaded from Google Fonts or any other foreign CDN. If you do consent to the tags above, your browser fetches those from Google and Meta, so your IP address travels to the United States.
Connecting Claude or ChatGPT
A couple can connect Ringske to Claude (by Anthropic) or ChatGPT (by OpenAI). That only happens when a partner does so themselves, with their own login, and explicitly gives permission. From then on Ringske answers that AI's questions about the wedding: the guest list, the answers, dietary needs, tasks, budget and vendors. What is asked and answered goes to the AI the couple chose, under Anthropic's or OpenAI's terms and outside the EU.
For guests' data the couple remains the controller here too, as for the rest of their guest list. Ringske keeps nothing extra from those conversations: only which action took place, with ids and without names. The couple revokes access with one click, in the dashboard under Claude & ChatGPT.
What we do not do
We do not sell anything on. Guest data is never used for advertising, not by us and not by the couple. We send email only for RSVP confirmations and the delivery of your wedding site — no newsletters you did not ask for.
Your rights
Under the GDPR you have the right to access, correction, erasure and portability. If you are a guest at a wedding, address the couple first — they are the controller. If that does not work out, or if you are our customer, email hallo@ringske.be. We reply within one month, as the GDPR requires, and usually much sooner.
Who are we?
Ringske is a product of ElianCodes BV, Limburgstraat 82, 9000 Ghent, Belgium — VAT BE 1005.910.883.
Last updated: 10 October 2026.