Legal & Privacy
Last updated: November 3, 2026 — V2.4
📋 Summary
GlabTech operates SBIX, SBIX Certify and GCMOB / GO. SBIX provides sovereign proof infrastructure for creators and enterprise. For SBIX verification and certification, we do not store submitted raw images or files: those systems work on cryptographic hashes and perceptual fingerprints. GO processes ride and driver information as described below.
🏢 1. Legal Information
- Publisher: GlabTech SARL
- Location: Anse des Cayes, 97133 St-Barthelemy, France
- ASN: 30077 (ARIN registered)
- Founded: 2011
- Email: founder@glabtech.com
- Hosting: Self-hosted infrastructure (ASN 30077) + IONOS backup (EU)
🛡️ 2. Our Products
SBIX Verify API (certify.sbix.io/check)
Visual origin engine. Detects image copies, infers probable origin, traces cross-platform propagation. 5.4M images indexed across 14 platforms.
- Data processed: Perceptual hashes only (pHash/dHash/aHash) — images are never stored
- Index: Public platforms (Teia, Objkt, Wikimedia, MET, NASA, Europeana...)
- Decision: BLOCK / REVIEW / SAFE returned in <200ms
- Legal proof: eIDAS Qualified timestamp on every BLOCK decision
- Enterprise POC: Available under NDA — contact@sbix.io
SBIX Certify (certify.sbix.io)
Proof of creation for digital artists. Legal timestamps + blockchain anchoring in 60 seconds.
- Data collected: Email (for account), file hash SHA-256 (never the file itself)
- Timestamp: eIDAS Qualified (AlfaSign / AlfaTrust) or RFC-3161 local
- Blockchain anchoring: Tezos L1 + Aleph.im
- Payments: Processed by Stripe (PCI-DSS compliant)
SBIX Core (sbix.io)
Enterprise proof infrastructure for MiCA compliance. On-premise deployment available.
- Data collected: Contact form submissions only
- Deployment: On-premise available — data never leaves your infrastructure
🔐 3. Personal Data (GDPR)
3.1 What data do we collect?
- Account creation: Email address
- Contact forms: Name, email, message
- Certify usage: File hashes (SHA-256), timestamps, proof IDs
- Verify API: Perceptual hashes of submitted images (pHash/dHash/aHash)
- Analytics: Plausible (cookie-less, privacy-first, EU-based)
3.2 What we do NOT collect
- Your files or images — we only process cryptographic fingerprints
- For SBIX product processing, no IP address is stored as product data; GO web-server access logs do record IP addresses (see GCMOB / GO section).
- Tracking or advertising cookies
- Third-party marketing data
3.3 Legal bases
- Contract: Account creation, certification services, API access
- Legitimate interest: Analytics, security, service improvement
- Legal obligation: Invoicing, tax records
3.4 Data retention
- Proofs/certificates: Stored indefinitely (blockchain anchored)
- Perceptual fingerprints: Stored in index indefinitely to improve detection
- Account data: Until account deletion + 30 days
- Contact requests: 24 months after last contact
3.5 Your rights (GDPR Articles 15-22)
- Access, rectify, or erase your personal data
- Restrict or object to processing
- Data portability
Exercise your rights: founder@glabtech.com — Supervisory authority: CNIL (France)
🚕 GCMOB / GO : confidentialité / Privacy
Français
Responsable : GlabTech SARL, Anse des Cayes, 97133 Saint-Barthélemy. Contact : founder@glabtech.com.
Voyageurs : GO traite le lieu de prise en charge, la destination, les indications saisies, un identifiant temporaire et les étapes de la course pour organiser la mise en relation avec un chauffeur. Avec votre choix, il utilise votre position GPS, les notifications du navigateur ou un numéro WhatsApp facultatif. Le point GPS de prise en charge est supprimé à la montée, à la fin ou à l'annulation de la course, ou expire après deux heures. Le contact WhatsApp facultatif est supprimé du dossier temporaire après l'avis d'arrivée ou selon les actions prévues dans le parcours. Autres échéances : abonnement aux notifications, au plus 24 heures ; code de montée, 24 heures ; identifiant temporaire et cookie technique sbix_go, 7 jours.
Chauffeurs : GO traite les informations professionnelles nécessaires à l'admission et aux courses : identité, contact, véhicule, immatriculation, autorisation ADS, disponibilité, propositions, réponses et étapes des missions. Le prénom peut être visible depuis le QR personnel du chauffeur. Le chauffeur peut choisir librement, depuis son espace, d'autoriser la publication de son numéro WhatsApp pour que ses clients puissent le joindre, par exemple en cas d'objet oublié. Avec ce consentement explicite, son numéro est accessible depuis sa carte personnelle (lien ou QR) et depuis la page de course des voyageurs qu'il a transportés, jusqu'à 7 jours après la course, dans la limite de la durée du suivi propre au voyageur. Ce consentement est distinct de l'admission dans GO : sans lui, le numéro n'est jamais affiché. Il peut être retiré à tout moment ; le numéro cesse alors d'être affiché, mais un numéro déjà consulté ou enregistré par un voyageur peut rester connu de lui. Les notifications WhatsApp professionnelles nécessitent un accord explicite préalable, qui peut être retiré. Le lien d'une course expire après 48 heures ; le lien de l'espace chauffeur reste valable jusqu'à sa révocation.
Invitations entre chauffeurs : un chauffeur peut inviter un confrère en indiquant son prénom et, s'il le souhaite, son numéro de téléphone. Ces informations servent seulement à présenter l'invitation à la personne invitée ; le numéro n'est pas réaffiché à l'auteur de l'invitation. La personne invitée décide librement d'accepter. Si elle accepte, elle déclare elle-même son prénom et son numéro, confirmé par un code WhatsApp, et peut indiquer son autorisation de taxi (ADS). Une ADS déclarée n'est pas une autorisation vérifiée : l'admission dans GO reste une décision humaine après contrôle. Lorsqu'une invitation expire ou est refusée, le prénom et le numéro indiqués par l'auteur de l'invitation sont supprimés après son expiration, lors d'un traitement ultérieur du service ; l'invitation reste enregistrée sans ces données. Pour une invitation acceptée, le numéro indiqué peut être conservé avec l'invitation.
Bases légales : exécution du service demandé (mise en relation et suivi de la course) ; consentement (notifications WhatsApp, notifications du navigateur, publication du contact WhatsApp du chauffeur) ; intérêt légitime (sécurité du service, réponse à une réclamation ou à un litige).
Destinataires : le chauffeur sollicité voit le lieu de prise en charge, la destination et les indications de la demande. Aucune donnée n'est vendue ni utilisée à des fins publicitaires. Les données nécessaires au fonctionnement du service sont transmises uniquement aux destinataires et prestataires décrits ci-dessous, ou lorsque la loi l'exige.
Prestataires : Meta/WhatsApp traite les informations nécessaires à l'acheminement des messages choisis, éventuellement hors de l'Union européenne ; les services de notifications push des navigateurs acheminent des notifications chiffrées. GO conserve aussi des journaux techniques, notamment les adresses IP et les chemins demandés, pour l'exploitation et la sécurité.
Conservation : les données temporaires ont des échéances techniques variables. Les journaux de courses et les fiches chauffeurs ne sont pas encore soumis à une purge automatique. GlabTech a fixé comme objectifs une conservation maximale de 12 mois après la course et de 12 mois après la fin de la relation avec le chauffeur, sauf obligation légale ou nécessité justifiée de conservation plus longue. Pour les journaux techniques, l'objectif est de 30 jours maximum, sous réserve de vérification et de mise en conformité de la rotation effective. Ces objectifs ne décrivent pas une suppression automatique déjà opérationnelle. Invitations entre chauffeurs : voir le paragraphe ci-dessus ; pas de délai fixe de suppression.
Vos droits : vous pouvez demander l'accès, la rectification, l'effacement ou la limitation du traitement de vos données, selon les règles applicables, à founder@glabtech.com. Vous pouvez également contacter la CNIL.
English
Controller: GlabTech SARL, Anse des Cayes, 97133 Saint-Barthélemy, France. Contact: founder@glabtech.com.
Passengers: GO processes pickup details, destination, optional instructions, a temporary identifier and ride events to coordinate taxi requests. With your choice, it uses device location, browser notifications or an optional WhatsApp number. Pickup GPS data is removed upon boarding, completion or cancellation, or expires after two hours. The optional WhatsApp contact is removed from the temporary ride record after the arrival notice or as provided by the service flow. Other expiry periods: notification subscription, up to 24 hours; boarding code, 24 hours; temporary identifier and technical cookie sbix_go, 7 days.
Drivers: GO processes professional registration and ride information, including name, contact, vehicle, registration plate, taxi authorization, availability, offers, responses and ride events. A driver's first name may be visible through their personal QR code. A driver may freely choose, from their driver space, to allow publication of their WhatsApp number so that their passengers can reach them, for example about a lost item. With this explicit consent, the number is available from the driver's personal card (link or QR code) and from the ride page of passengers they have driven, for up to 7 days after the ride, within the limit of the passenger's own follow-up period. This consent is separate from admission to GO: without it, the number is never displayed. It can be withdrawn at any time; the number then stops being displayed, but a number already viewed or saved by a passenger may remain known to them. Operational WhatsApp notifications require prior explicit agreement, which may be withdrawn. A ride link expires after 48 hours; the driver space link remains valid until revoked.
Invitations between drivers: a driver may invite a colleague by entering their first name and, optionally, their phone number. This information is used only to present the invitation to the invited person; the number is not shown again to the person who sent the invitation. The invited person freely decides whether to accept. If they accept, they enter their own first name and number, confirmed by a WhatsApp code, and may state their taxi authorization (ADS). A declared ADS is not a verified authorization: admission to GO remains a human decision after review. When an invitation expires or is declined, the first name and number entered by its sender are deleted after expiry, during a later processing of the service; the invitation itself remains recorded without them. For an accepted invitation, the number entered may be kept with the invitation.
Legal bases: performance of the requested service (matching and ride follow-up); consent (WhatsApp and browser notifications, publication of the driver's WhatsApp contact); legitimate interest (service security, handling of complaints or disputes).
Recipients: the solicited driver sees the pickup point, destination and request instructions. No data is sold or used for advertising. Data necessary to operate the service is shared only with the recipients and service providers described below, or where required by law.
Service providers: Meta/WhatsApp processes information needed to deliver selected messages, possibly outside the European Union; browser push services deliver encrypted notifications. GO also maintains technical logs, including IP addresses and requested paths, for operations and security.
Retention: temporary records have varying technical expiry periods. Ride journals and driver records are not yet subject to automatic deletion. GlabTech has set retention targets of up to 12 months after each ride and 12 months after the end of a driver's professional relationship, except where a legal duty or justified need requires longer retention. The target for technical logs is no more than 30 days, subject to checking and configuring actual log rotation. These targets do not represent automatic deletion already in place. Invitations between drivers: see the paragraph above; no fixed deletion period.
Your rights: subject to applicable law, request access, correction, erasure or restriction at founder@glabtech.com. You may also contact the French data protection authority (CNIL).
🍪 4. Cookies & Tracking
- glabtech.com: Plausible Analytics (cookie-less, GDPR-compliant)
- certify.sbix.io: Plausible Analytics (cookie-less)
- Essential cookies: Session management only (no tracking)
- gcmob.sbix.io: one technical cookie,
sbix_go, valid 7 days, to follow a taxi request without an account (no tracking, no analytics)
We do not use Google Analytics, Facebook Pixel, or any third-party advertising tracking.
🔗 5. Third-Party Services
- Stripe: Payment processing (PCI-DSS Level 1)
- AlfaSign / AlfaTrust: eIDAS Qualified timestamps (EU Trusted List)
- Plausible: Privacy-first analytics (EU-based)
- Tezos: Blockchain anchoring (public, decentralized)
- Aleph.im: Decentralized storage backup
- Formspree: Contact form handling
- Meta Platforms (WhatsApp Business): delivery of GCMOB / GO messages to drivers and, if requested, to passengers
- Browser push services (Google, Mozilla, Apple): delivery of encrypted GCMOB / GO notifications
⚡ 6. Security & Sovereignty
- Hashes only: We never store your original files or images
- Own infrastructure: ASN 30077 — self-managed, EU jurisdiction
- No cloud dependency: On-prem deployments available for enterprise
- Encryption: TLS 1.3 in transit, Ed25519 signatures
- Location: St-Barthelemy, France (French law, CNIL jurisdiction)
📜 7. Terms of Use
Access to GlabTech services is provided "as is". SBIX Certify certificates are cryptographic proofs anchored on public blockchains — they cannot be modified or deleted once created. Ensure you have rights to certify any content before using the service.
SBIX Verify API results are informational. Decisions (BLOCK/REVIEW/SAFE) are based on indexed fingerprints and probabilistic scoring. They do not constitute legal advice or definitive copyright determination.
🗑️ 8. Data Deletion
You can request deletion of your personal data at any time, whether that data was collected directly by GlabTech or received through a connected platform.
How to request deletion
- Email: founder@glabtech.com, subject "Data Deletion Request"
- Include: the email address, account identifier or platform identifier used with the service
- Processing time: within 30 days of receipt
- Confirmation: written confirmation is sent once deletion is complete
What cannot be deleted
- Blockchain-anchored proofs: once anchored on a public chain a proof cannot be modified or removed. It contains a cryptographic hash only — never your file, never personal data
- Legal and accounting records: invoices are retained for the period required by French law
❓ FAQ
Do you store my images?
Never. We only process perceptual hashes (pHash/dHash/aHash). Your images are never stored on our servers.
Do you sell my data?
No. Never. We do not sell, rent, or share your personal data with third parties for marketing purposes.
How do I request a POC for the Verify API?
Email contact@sbix.io with your use case. Enterprise POCs are available under NDA for image archives of any size.
How do I delete my account?
See section 8 — Data Deletion. Requests are processed within 30 days.
📧 Contact
- General / Legal / GDPR: founder@glabtech.com
- Verify API / POC: contact@sbix.io
- Address: GlabTech SARL, Anse des Cayes, 97133 St-Barthelemy, France