FLOKK · SUB-PROCESSORS
Sub-processors
Last updated: 17 August 2026
This page lists the third parties that process personal data on behalf of Pallasite OÜ when you use Flokk. We keep it current: when we add a provider, we update this page.
| Provider | What it does | Personal data involved | Where |
|---|---|---|---|
| Pallasite identity service | Accounts, sign-in, sessions | Email address, account identifier, authentication events | Our own infrastructure — see Transfers outside the EEA |
| Pallasite application backend and storage | The app's database and file storage | Profile, roster entries, posts and comments, saved places, device records, verification photos, post images | Our own infrastructure — see Transfers outside the EEA |
| Google Places API | Place search and place details | Search terms and city context — sent from our servers; your device does not contact Google Places directly | EU / US |
| Mapbox | Map tiles and map rendering | Map tile requests made by your device | US |
| Apple | Sign in with Apple; app distribution | Authentication data | EU / US |
| Sign in with Google | Authentication data | EU / US |
Not used
For clarity, because people ask:
- No third-party analytics or attribution provider. The Flokk app contains no analytics SDK.
- No advertising network, and no advertising identifier.
- No data broker, and we do not sell personal data to anyone.
Transfers outside the EEA
Where a provider processes data outside the European Economic Area, we rely on the mechanisms in Chapter V of the GDPR — an adequacy decision where one applies, and otherwise Standard Contractual Clauses. For transfers concerning users in Türkiye we rely on the mechanisms in Article 9 of Law No. 6698.
Changes
We update this page before a new sub-processor starts processing your data. Questions: info@pallasite.net.