SwiftSoft Labs

Sidedoor Google Play Data safety

Version 1.0.0, effective 20 November 2026. Signature verified with key synlex-1.

Google Play Data safety

{
  "format": "synlex-android-data-safety",
  "formatVersion": 1,
  "note": "Compiled from the compliance plan. Enter these answers in Play Console under App content, Data safety, and check them against your app. processedEphemerally and required are not in the plan: answer them for each data type.",
  "collectsOrSharesUserData": true,
  "dataTypes": [
    {
      "category": "App info and performance",
      "type": "Crash logs",
      "collected": true,
      "shared": false,
      "processedEphemerally": null,
      "required": null,
      "purposes": [
        "Account management",
        "Analytics",
        "App functionality"
      ],
      "from": [
        "Crash reports and performance traces"
      ]
    },
    {
      "category": "Financial info",
      "type": "Purchase history",
      "collected": true,
      "shared": false,
      "processedEphemerally": null,
      "required": null,
      "purposes": [
        "Account management",
        "App functionality"
      ],
      "from": [
        "Purchase history: drink orders (items, prices, tip, fees, venue, pickup code)",
        "Purchase records (Kelviq customer ID, plan, subscription status, refunds)"
      ]
    },
    {
      "category": "Location",
      "type": "Precise location",
      "collected": true,
      "shared": false,
      "processedEphemerally": null,
      "required": null,
      "purposes": [
        "Account management",
        "App functionality"
      ],
      "from": [
        "Precise location (GPS) while the app is open, to find nearby venues"
      ]
    },
    {
      "category": "Personal info",
      "type": "Email address",
      "collected": true,
      "shared": false,
      "processedEphemerally": null,
      "required": null,
      "purposes": [
        "Account management",
        "App functionality"
      ],
      "from": [
        "Email address",
        "Google or Apple account ID and email (social sign-in)"
      ]
    },
    {
      "category": "Personal info",
      "type": "Name",
      "collected": true,
      "shared": false,
      "processedEphemerally": null,
      "required": null,
      "purposes": [
        "Account management",
        "App functionality"
      ],
      "from": [
        "Name and display name"
      ]
    },
    {
      "category": "Personal info",
      "type": "Other info",
      "collected": true,
      "shared": false,
      "processedEphemerally": null,
      "required": null,
      "purposes": [
        "Account management",
        "App functionality"
      ],
      "from": [
        "Account credentials (password hash, verification codes, sign-in sessions)",
        "Cover and line-skip passes",
        "Date of birth and age and identity verification result (from Sumsub)",
        "Merchant Portal venue and staff details (staff names, hashed PINs, POS tokens)",
        "Selfie face scan for the liveness check (taken and kept by Sumsub)",
        "Sign-in history and account security log"
      ]
    },
    {
      "category": "Photos and videos",
      "type": "Photos",
      "collected": true,
      "shared": false,
      "processedEphemerally": null,
      "required": null,
      "purposes": [
        "Account management",
        "App functionality"
      ],
      "from": [
        "Government ID document photos (taken and kept by Sumsub)",
        "Menu item photos uploaded by venues"
      ]
    }
  ],
  "security": {
    "encryptedInTransit": "Data is sent over HTTPS. Passwords and staff PINs are hashed with bcrypt, refresh tokens are stored as SHA-256 hashes, and sign-in tokens are kept in the device's secure storage (SecureStore) where the device supports it.",
    "deletionRequest": "Delete your account in the app (Profile > Delete account). For a copy of your data, a correction, deletion of the ID photos and selfie Sumsub holds, or if in-app deletion fails, write to legal@swiftsoftlabs.com."
  }
}

Check these documents

Checking the signature in your browser…

Your browser computes the SHA-256 of each document on this page and compares it with the hash in the signed release manifest.

DigiCert, Inc. timestamped the manifest hash at Fri, 20 Nov 2026 15:02:36 GMT. Synlex checked the authority's signature, the hash, and its certificate chain to DigiCert Trusted Root G4, a root pinned in Synlex. To check the token yourself, download it from the footer and run:

openssl ts -verify -in release-v1.0.0.tsr -digest 39261a297363948792c31c664dddb263ffff5f1b485605c8d407d9d0a839148b -CAfile /etc/ssl/cert.pem
Check the signature yourself with OpenSSL 3

The JSON API publishes the signed manifest bytes and the signature; the keys file publishes synlex-1's public key and its window. Then check that the manifest's signedAt falls inside that window and that its document hashes match the documents.

curl -s 'https://synlex.vercel.app/api/public/v1/swiftsoftlabs/sidedoor?version=1.0.0' | jq -j .signature.manifest > manifest.json
curl -s 'https://synlex.vercel.app/api/public/v1/swiftsoftlabs/sidedoor?version=1.0.0' | jq -r .signature.value | base64 -d > manifest.sig
curl -s 'https://synlex.vercel.app/.well-known/synlex-keys.json' | jq -r '.keys[] | select(.id == "synlex-1") | .publicKey' | base64 -d > key.der
openssl pkeyutl -verify -pubin -keyform DER -inkey key.der -rawin -in manifest.json -sigfile manifest.sig