Privacy
Controller
Aloaha Limited
„Helgoland“
45, Triq Gio Felice Inglott
Pembroke PBK1131
Malta
E-mail: info@aloaha.com · Phone: +49 541 3859 4554
Please write “GDPR request” in the subject line for data-protection matters. We answer within one month (Art. 12(3) GDPR).
What this website does not do
No cookies – neither our own nor third-party cookies.
No analytics or statistics services, no advertising or tracking pixels, no fingerprinting, no session recordings.
No external fonts or CDNs – fonts, scripts and images are delivered only by this website.
No forms and no user accounts.
Server logs
Like every web server, our server records technical access data: IP address, date and time, requested address, status code, amount of data transferred, referrer and browser identification (user agent). We need this data to deliver the website securely and to fend off attacks. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in secure operation). The logs are deleted automatically after 14 days; they are not used for advertising or profiling, not combined with other data and not passed on to third parties. The website is hosted in the European Union.
Storage in your browser
If you switch the colour scheme or the language, your browser remembers the choice in its local storage (keys codeb-theme and codeb-lang). The values stay on your device and are not sent to us. You can delete them at any time in your browser settings. This storage is strictly necessary for the function you requested.
Contact by e-mail or phone
If you write to us or call us, we process the details you provide (for example name, e-mail address, phone number and the content of your message) to answer your enquiry. Legal basis: Art. 6(1)(b) GDPR (pre-contractual measures at your request) and Art. 6(1)(f) GDPR. We keep this correspondence only as long as needed for the enquiry and for statutory retention obligations.
The CodeB Wallet app
Credentials in CodeB Wallet are stored on your device, protected by the Android hardware-backed keystore and your PIN or biometrics. Data from a credential is shared with a service only when you approve the request in the app.
To work, the app connects to the issuers and services you choose, to EU trust lists, and to the wallet-provider service that confirms the app’s integrity to issuers. Aloaha Limited receives credential data only if you choose an issuer or service operated by Aloaha Limited – for example the CodeB issuer.
Permissions. Camera: only to scan QR codes and the machine-readable zone of an ID card or passport; images are processed on the device and not stored or sent. Bluetooth (and, on older Android versions, location – Android requires this permission for Bluetooth scanning): only to exchange documents phone-to-phone when you show or check an ID in person; your location is not determined or collected. NFC: to start an in-person exchange with a tap, and to read ID cards, passports and signature cards you hold to the phone. Biometrics: unlocking is done by Android; your fingerprint never reaches the app. Files: only the PDF documents you choose to sign.
Address lookups. The app looks up server addresses with your phone’s normal settings. Only if that fails does it ask the encrypted DNS services of Cloudflare (1.1.1.1) or Google (8.8.8.8) for the address of that server name; they receive the name and your IP address, nothing else. The last addresses that worked are kept on your phone so that a short network problem does not stop the app. Connections stay encrypted and are checked against the server’s certificate in every case.
Remote signing. When you sign a PDF with a signing service, only a cryptographic fingerprint (hash) of the document is sent to that service; the document itself stays on your phone. If you use the CodeB signing service (phone.codeb.io), Aloaha Limited processes your account, your signing certificate and a record of each signature to provide and document the service.
Signing with a signature card. The card signs a fingerprint (hash) of the document; the key never leaves the card and the document stays on your phone. Your PIN is never stored. The card access number (CAN) is kept encrypted on your phone so that it can be offered next time; you can clear it in the dialog. For the trusted timestamp, only a fingerprint (hash) of the signature is sent to the CodeB timestamp service (phone.codeb.io). The certificate from the card is embedded in the signed PDF, as with every digital signature.
History and logs. The list of what you shared, added or signed is kept only on your phone. The app collects no analytics, shows no advertising and does not track you. A technical log file is created only when you tap “Retrieve logs” and leaves the phone only if you decide to send it to us. If the app stops unexpectedly, it writes a short crash report on your phone (numbers, e-mail addresses and keys masked; the last five are kept) and attaches it to that log only if you send one. At start the app checks your phone’s security on the phone itself (for example root access, an emulator, the security update level) and tells you once if something weakens protection; the result is not sent anywhere.
One-time codes. Accounts you add under One-time codes (service, account name and the secret key) are kept encrypted on your phone, apart from your documents, and are never sent to anyone. They leave the phone only when you show them as QR codes or include them in a backup file you create.
Pseudonyms (passkeys). For each website where you create a pseudonym, the app keeps a key in your phone’s secure hardware and, encrypted on your phone, the website address, the account name the website chose and your own optional name for it. The website receives only the public key and the signed sign-in confirmations – never your name, your own name for the pseudonym or anything from your documents. For other apps, the app checks the website’s public Digital Asset Links file (assetlinks.json) on that website.
Checking someone else’s ID. Details received with “Verify” are shown once and deleted when you close the result.
Reading ID cards and passports. When you read the chip of your ID card or passport, the data goes from the chip directly to the app on your phone. To check the issuing country’s signature, the app downloads the public list of country certificates (CSCA master list and revocation lists) from phone.codeb.io; nothing about your document is sent. The machine-readable zone is recognised on the phone with Google ML Kit, which Google Play services provides (Play services downloads its recognition model); Google Play services sends Google technical usage and performance information, never the camera images or the recognised text. The data read is shown to you and kept only if you choose to save it – then encrypted on your phone with a key held in its secure hardware. You can delete it in the app at any time.
Reading for the CodeB PID Provider. When you sign in at the CodeB PID Provider (phone.codeb.io) and choose to read your ID card or passport, the server reads the chip itself: your phone only passes the encrypted messages on and keeps no copy. The chip and the server talk over their own end-to-end encrypted and authenticated channel, so neither your phone nor anyone in between can read or change the data. To show that the request comes from the genuine app on a secure phone, the app sends a key certificate from your phone's secure hardware (Android Key Attestation) and a Google Play Integrity verdict; Google processes the request for this check. The server uses the data to open or prefill your account at the PID Provider.
Deleting your data. You can delete single documents in the app, or everything at once with Settings → Delete wallet (or by uninstalling CodeB Wallet). Data held by an issuer or signing service is governed by that provider; for services of Aloaha Limited write to info@aloaha.com.
The app uses a wallet-provider service to confirm to issuers that the app is genuine. For the CodeB issuer this is Aloaha Limited’s own wallet provider on phone.codeb.io: it receives the public key the app uses for that issuer, key certificates from your phone’s secure hardware (Android Key Attestation – for that key and for a one-time key made for each request; they also show whether the phone’s system is locked and verified, and its security patch level) and a Google Play Integrity verdict – Google processes the request for this check; if Google’s check is unavailable, the hardware certificates alone can be enough. For other issuers the app uses the EU reference wallet provider (wallet-provider.eudiw.dev). Neither receives your documents or their contents; if your phone cannot be checked, the app uses the EU reference wallet provider for the CodeB issuer too.
Your rights
Under Articles 15 to 22 GDPR you have the right to access, rectification, erasure, restriction of processing, data portability and objection, and to withdraw consent at any time. To exercise these rights, write to info@aloaha.com with “GDPR request” in the subject line.
Right to lodge a complaint
You have the right to lodge a complaint with a data-protection supervisory authority (Art. 77 GDPR). As the controller is established in Malta, the lead supervisory authority is the Office of the Information and Data Protection Commissioner (IDPC), Malta.