How the document model works
- The global Terms and global Privacy Notice are the master documents.
- The regional sections below supplement them. Mandatory law of your habitual residence prevails over conflicting contract language.
- Meinivo supports accounts worldwide across the 249 ISO 3166-1 countries and territories. Surveys, KYC and individual payout methods are shown for a residence country only when provider, sanctions, transfer and local-law requirements are satisfied.
Store availability and account registration are international. They do not promise that surveys or every payout method are available at all times in every country.
EU/EEA and Germany
AT, BE, BG, CZ, DE, DK, ES, FI, FR, GR, HU, IE, IT, LT, LU, LV, NL, NO, PL, PT, RO, SE, SI and SK follow GDPR/EEA rules plus national consumer, tax, advertising, prize and youth rules. Germany additionally applies BDSG, TDDDG, DDG, MStV and VSBG. Local language, transparent choices, rights operations, processor contracts and documented transfers are required.
United Kingdom, Switzerland and Serbia
GB requires UK GDPR/Data Protection Act and PECR review plus UK transfer instruments. CH requires FADP transparency and Swiss transfer review. RS requires local privacy, representative and transfer review. Mandatory consumer rights remain unaffected.
North and Latin America
US: State privacy, biometric, youth, advertising and incentive rules are reviewed for each target state. Rights, Global Privacy Control and the Financial Incentive Notice apply where relevant; Didit stays blocked in states requiring additional biometric writing/retention until implemented.
CA: PIPEDA and applicable provincial laws, especially Quebec, require meaningful consent, transparency, access/correction, safeguards and cross-border accountability; English and French are release gates.
AR, BR, MX and PE: Local Spanish/Portuguese notices, rights routes, transfer mechanisms and any registration must precede launch. BR follows LGPD/ANPD rules; MX requires its local privacy-notice and ARCO process.
Asia-Pacific
AU and NZ: local privacy principles, overseas accountability and breach operations. JP: APPI, Japanese notice and foreign-recipient information. IN: DPDP Act/Rules according to the commencement phase actually in force at launch, language, consent and grievance route. SG: PDPA, DPO contact, purpose/consent, transfer and breach rules. ID, MY, PH and TW: local PDP/PDPA law, language, registration/DPO/representative where required and transfer review. BD, LK and PK: current law and commencement must be refreshed immediately before release.
MENA and Turkey
AE, BH, OM, QA and SA require Arabic or bilingual transparency, local controller/registration/DPO requirements, transfer approval or assessment, sanctions screening and a separate review of every crypto payout. TR requires KVKK-compliant Turkish notice, consent/transfer route and any registration/representation.
Current product-country scope
Account registration and core account functions are intended for all 249 ISO 3166-1 countries and territories. The operational provider target matrix currently covers around 70 markets; actual survey supply depends on profile, sponsor, quota and provider coverage. Payout methods are filtered server-side by residence country, currency, KYC, sanctions screening and provider availability. Provider marketing or store visibility does not replace these feature-specific gates.
Conflict and contact
If a regional supplement conflicts with mandatory law of your country of residence, that mandatory law controls. Send questions, rights requests or appeals to colin-mario.koese@bitora.de.