Application & pass generation
AWS, Paris region (eu-west-3).
The security of your data is our responsibility as much as yours. Walleett hosts and processes your customers' loyalty data. That responsibility shapes our entire architecture, our hosting choices, and our contractual commitments.
All databases containing your end customers' information, along with the critical pass generation and update services, are hosted in France and within the European Union, with established market providers.
AWS, Paris region (eu-west-3).
AWS S3, European infrastructure.
MongoDB and PostgreSQL, European hosting.
VM hosted in Europe.
Our hosting providers hold the market's highest certifications (ISO 27001, SOC 2 Type II), guaranteeing the quality of their data centers, physical and logical monitoring, and operational continuity.
Under GDPR, Walleett acts as a data processor within the meaning of Article 28. Customers (the brands, retailers, or event organizers) remain the data controllers for the data they entrust to us. We process that data strictly according to their instructions, and solely to deliver the subscribed service.
Every client receives a Data Processing Agreement (DPA) that formalizes our role as data processor, governs the conditions of processing, and sets out the mutual commitments in accordance with Article 28 of the GDPR.
Walleett processes only the data our clients send us to generate and manage their passes. The exact nature of that data depends on the configuration chosen: opaque identifiers, personalization variables (first name, loyalty number, points...), or technical identifiers required by Apple and Google Wallets.
Rights of access, rectification, erasure, and portability are exercised with the data controller (the brand or retailer that owns the customer relationship). Walleett provides the necessary technical capabilities (member deletion, data export).
Walleett's technical security is built on proven mechanisms and industry-recognized standards. Here are the main safeguards in place.
Apple Wallet and Google Wallet certificates are encrypted with AES-256-GCM, using keys derived uniquely per client (strict cryptographic isolation between tenants).
All communications use TLS, with HSTS enforced in production. Communications with Apple Push Notification Service use TLS encryption with certificate-based authentication.
Passwords and API secrets hashed with bcrypt at a high cost factor (never stored in plain text). Sessions managed via JWT with automatic expiration.
Each API key is scoped per brand and can be restricted to an IP range. Rate limits are configurable and enforced at the individual key level.
Progressive rate limiting by IP on repeated authentication failures. Automatic temporary blocking to limit brute-force attempts.
Each pass download URL is signed with HMAC-SHA256, guaranteeing authenticity and preventing any tampering.
In accordance with the GDPR data minimization principle, we retain data only for as long as strictly necessary to deliver the service. Our retention policy differentiates data by type and purpose.
Retained as long as the client actively uses it. Deletable at any time on request, through a multi-step technical procedure (revocation on Apple's side, deletion on Google's side, file and database erasure).
API access and operations retained for a maximum of 12 months, then automatically deleted.
Jobs, quotas, notification events purged automatically according to short retention periods (from 48 hours to 30 days depending on type).
Retained for 10 years in compliance with French accounting and tax obligations.
End-user IP addresses are not retained. IP addresses from API calls are logged in technical audit logs for 12 months for security and abuse detection purposes, then automatically deleted. Location information used for contextual features (country, city) is derived in memory and is not persisted.
Walleett is officially registered with the Apple Developer Program and the Google Wallet Issuer Program. Our architecture meets the requirements imposed by both platforms.
Walleett offers two certificate management modes for Apple Wallet and Google Wallet:
Since Apple and Google are US companies, pass generation and distribution operations involve transferring certain data to their servers in the United States. These transfers are governed by the EU-US Data Privacy Framework, of which Apple and Google are signatories, ensuring a level of protection equivalent to European GDPR. The precise terms are included in our DPA, provided to each client.
To deliver our service, Walleett relies on a limited number of technical sub-processors selected for their reliability, regulatory compliance, and security posture. The full list of our sub-processors, with their purposes, jurisdictions, and contractual guarantees, is provided to our clients on request.
Any addition or change of sub-processor is notified to our clients under the terms set out in their Data Processing Agreement, in accordance with Article 28 of the GDPR.
Walleett's high availability relies on our hosting providers' infrastructure and on an architecture designed for resilience.
Databases are backed up automatically by our hosting providers, with restore points that allow rollback in the event of an incident.
Critical services (pass generation, notifications, updates) run on a serverless, distributed architecture designed to absorb traffic spikes.
Our infrastructure is monitored around the clock to detect and address any anomaly quickly.
Whether you're in the evaluation phase, running a vendor review, or conducting an internal audit, we respond quickly.