Sign in to book and see your community.
Free and takes a minute. Then join your community.
Security and privacy
How we protect the accounts and data of the people who book with Apoing, and what a town hall, a school or a community can check before using it.
What we do so that only you get in.
We don't store your password, only a fingerprint computed with PBKDF2 (100,000 rounds and a different salt for each person). Not even the Apoing team can tell what it is.
On top of your password you can ask for a 6-digit code from your phone. It is compulsory for Apoing staff with administrative access. How to turn it on.
If someone signs in to your account from a browser or phone we hadn't seen, we email you the device, the time and the IP address. From your profile you can see where your account is open and sign it out anywhere.
After several failed attempts we block sign-in for a few minutes and ask for "I'm not a robot". Changing your password signs out every open session, including the app's.
What we keep, for how long and how you take it with you.
From your profile you can download a file with everything we hold about you (profile, bookings, matches, messages, what you have accepted) and delete your account yourself.
Every night an automatic task deletes or anonymises whatever has passed its period:
We process data under the GDPR and Spain's LOPDGDD. We don't sell personal data. The details are in the privacy policy.
If something fails, what we can recover.
The database is backed up every night, checked, encrypted with AES-256 and stored elsewhere, in a folder the server cannot delete or overwrite. The server provider also takes a full daily copy that it keeps for 10 days.
Every week we automatically restore the latest backup on another machine and check that it is complete.
In Contabo data centres in Germany, inside the European Union.
Inside each community and inside Apoing.
A community's administrators see its members' bookings and contact details, and nothing from other communities. Members don't see each other's email or phone number.
If the Apoing team has to enter an account to fix a problem, we log who entered, when, why and which screens they saw. That log is kept for 12 months.
What a data protection officer usually asks for.
Each community accepts a data processing agreement (Art. 28 GDPR) when it signs up (existing ones, the first time their administrator signs in). We record who accepted it, when and which version, and the administrator can download it as a PDF in Edit community (website) or in the community settings (app).
If you need more information for your assessment (record of processing, technical measures or another document), write to support@apoing.com.
Accessibility statement
Thank you for telling us.
Write to support@apoing.com with "Security" in the subject and the steps to reproduce it. We'll look into it and reply as soon as possible. Please don't access other people's data or run tests that affect the service.
It summarises the measures we apply today. They may change to improve, and then we update this page. What legally binds us towards you is set out in the privacy policy and the terms and conditions. Last updated: 30 October 2026.