Privacy Notice

1. Controller and scope

Email: colin-mario.koese@bitora.de · Phone: +49 151 72406356

Bitora is the controller for the Meinivo app, API and first-party account, profile, ledger, points, referral, payout, support, notification, analytics and security processes. A survey sponsor or provider may be a separate or joint controller for its environment and responses. Meinivo is for persons aged 16 or older.

2. Data and sources

• Account: user ID, email, name, avatar, authentication provider, login/token metadata.
• Matching profile: date of birth, gender choice, residence country, postal code, language, education, work, industry, role, employer size, household, children, income band and purchase responsibility. The profile is encrypted at rest.
• Surveys: pseudonymous provider ID, offer/click/correlation data, status, reward and reversals. Meinivo ordinarily does not receive full survey answers collected in the provider or sponsor environment.
• Value and payouts: immutable ledger entries, points lots, bonuses, referrals including the 10% lifetime participation basis, rate, entitlement and reversal adjustments, method, destination, amount, fee, status, idempotency and fulfillment references.
• Identity check: the Didit workflow processes identity/age data, ID-document images/extracted fields, a selfie/passive-liveness capture, derived facial biometric characteristics and match/liveness results only after separate explicit consent. It enforces age 16. Necessary IP, browser, session, security and audit metadata may arise; AML/monitoring, NFC, proof of address, email, telephone and optional device/IP analysis are disabled. Meinivo stores only the account/session link, workflow and notice version, status/timestamps and an integrity hash, not document images, selfies, video, document numbers or the full decision.
• Support and communications: messages, attachments, preferences, push token, delivery and security email events.
• Technical and security: IP, user agent, timestamps, app/platform/build, request/error data, App Check integrity result, pseudonymized installation/network/payout entities and limited risk factors.
• Optional analytics and ads: consent state, coarse event names and performance buckets; if an ad feature is used, UMP/ad delivery, interaction, fraud and signed reward data.

Data comes from you, your device, authentication platforms, survey, identity and payout providers, signed callbacks and our server ledger.

3. Purposes and legal bases

We process data to create and secure your account, match surveys, record provider-confirmed rewards, operate points/referrals, fulfill payouts, communicate and support you, prevent fraud, comply with law and establish legal claims. In the EEA/UK/Switzerland, the bases are the Meinivo contract for integrated provider matching and core service delivery, consent for genuinely optional flows such as analytics, separate explicit consent for biometric processing where valid under applicable law, legitimate interests in secure reliable operations, and legal obligations. Analytics or marketing consent is never a condition for unrelated functionality. The biometric payout condition requires a separate necessity, proportionality and consent-validity review before release in each jurisdiction.

4. Survey providers and research data

Accepting the Terms activates provider connections integrated into Meinivo for your account. CPX Research (Make Opinion GmbH) is the intended active provider and may receive a provider-specific pseudonymous ID, IP, user agent, residence country, postal code, exact date of birth and gender choice to retrieve matching offers. CPX and survey sponsors may collect device/response metadata and answers under their own notices. See the CPX provider notice, CPX privacy policy and respondent terms.

TapResearch is code-prepared but remains disabled until contract, DPA, country, transfer and product gates pass. If released and not disabled by you, it may receive a separate pseudonymous ID, IP/device class, country and the qualification answers you provide. Some optional provider questions could reveal sensitive information; they require a just-in-time notice and, where required, explicit consent. See the Tap notice.

TheoremReach is code-prepared and its signed sandbox inventory has been verified, but production remains disabled until TheoremReach gives written permission for operation alongside similar rewarded survey offers and the country/transfer gates pass. If released and not disabled by you, it may receive a TheoremReach-specific pseudonymous ID, IP address, country code and, where available, age, binary gender mapping and postal code. See the TheoremReach notice.

You can disable a provider prospectively in Privacy settings. This stops new matching requests but does not undo processing already lawfully performed or signed reward/reversal records needed for the ledger and claims.

5. Recipients and services

• Google Firebase for authentication, App Check, push and technical platform services; Apple and Google for the sign-in/platform service you choose.
• CPX Research and, only after their respective activation gates, TapResearch and TheoremReach, plus survey sponsors.
• Sentry for scrubbed operational diagnostics in the configured EU region; no request bodies, survey answers, payout destinations, screenshots or session replay are intentionally sent.
• Resend for transactional email when live delivery is enabled.
• AppsFlyer only for the described referral attribution flow. For iOS deferred referral attribution, AppsFlyer OneLink may process the referral parameter, IP-derived approximate location, user agent, an AppsFlyer installation ID, install/app metadata and link/open events. Meinivo has disabled IDFA, IDFV collection, Apple Search Ads, SKAdNetwork and sharing with integrated ad networks or SRNs for this flow.
• Google AdMob/UMP only for the optional gated feature. Rewarded video is currently disabled. No rewarded ad request or ad reward occurs while disabled.
• Didit Identity Spain, S.L. and Didit Identity, Inc. for first-payout identity verification. Meinivo is controller; Didit is processor under its integrated DPA and a limited independent controller for security, abuse, legal, audit, claims and described anonymized/pseudonymized improvement purposes. Didit may use necessary group, hosting/cloud, communications, identity/document, fraud, analytics, audit, security and professional providers under its DPA.
• The selected payout/fulfillment service, including PayPal, a blockchain network or Tango Card.
• When enabled, the contractually documented encrypted support-object store plus private malware scanning/image re-encoding, and encrypted backup infrastructure solely for recovery and evidence.
• Other hosting, security and professional recipients where strictly necessary, and authorities where legally required.

See the Didit KYC notice before starting verification.

6. Security, fraud and automated support

Meinivo uses TLS, access controls, separated secrets, AES-256-GCM profile encryption, HMAC-pseudonymized risk entities, signed callbacks, idempotency and an append-only value ledger. Risk logic creates a limited recommendation. One heuristic does not impose a hold or permanent closure; material consequences receive human review. You may request human intervention, explain your position and appeal through support.

7. International transfers

Meinivo is operated from Germany. Some authentication, survey, email, diagnostics, attribution, advertising, payment or fulfillment providers may process data outside your country or the EEA. Depending on the route, safeguards include an adequacy decision, EU Standard Contractual Clauses, the UK Addendum/IDTA, a recognized certification framework, contractual/technical supplementary measures, or another lawful mechanism. Country release remains closed if the exact recipient country, role and mechanism have not been documented. A copy or description of applicable safeguards can be requested from us.

8. Retention and deletion

• Account/profile data: while the account is active, then deleted or anonymized subject to necessary exceptions.
• Optional first-party analytics: normally 180 days and deletable earlier in the app.
• Pseudonymous fraud entity links: normally 90 days; decisions/factors: normally 365 days unless a review, appeal or claim remains open.
• Pending referral tokens: no more than 30 days.
• Didit verification/feature data: the dedicated Meinivo application is configured to one month. Separate Didit control-plane audit logs are retained for 365 days according to the provider. Short-lived hosted URLs are cleared on a terminal status and Meinivo webhook-deduplication markers are normally deleted after 180 days. Switching routes first requests provider deletion of the old session and prevents its later events from approving a payout. Didit documents HTTP 204 as immediate and irreversible deletion of the session, decision, extracted data, related feature records and stored session media; a repeated request may return 404 for an unknown or already-deleted session. Separately created blocklist entries, issued hosted-flow share tokens, queued webhooks and a separate parent Didit user/business entity are not included according to the provider. Meinivo does not use the optional blocklist modules.
• Provider, support, email, ledger, payout and tax records: only for operations, reversals, evidence, legal defense and statutory retention. Financial records may need to remain in minimized form for the applicable statutory period.
• Legal acceptance and provider activation/deactivation events: retained as minimized evidence for the applicable limitation/contract period, then deleted or irreversibly detached.

Account deletion removes the Firebase login, anonymizes the Meinivo profile, revokes push tokens, removes provider profiles/links and instructs deletion of known Didit sessions before local KYC rows are removed. If the provider deletion fails, the request remains visibly pending/retryable rather than being reported as complete. Minimal ledger, fraud, acceptance or transaction evidence may remain where law, an open payout/reversal, abuse defense or a legal claim requires it. Use Delete account.

9. Your choices and rights

Use Privacy choices to manage provider activation, optional analytics, ads, push, marketing and deletion. Subject to local law, you may request access, correction, deletion, restriction, objection, portability or withdrawal of consent. We verify requests proportionately and respond within the applicable deadline.

EEA, UK and Switzerland

You have GDPR-style rights and may complain to your local authority. The Hamburg Commissioner for Data Protection and Freedom of Information is the authority for our German establishment. You may object to legitimate-interest processing and request safeguards for transfers.

United States

Depending on your state, you may have rights to know/access, correct, delete, obtain a portable copy, opt out of sale, targeted-ad sharing and certain profiling, limit certain sensitive-data use, appeal a refusal, use an authorized agent and receive non-discriminatory treatment. Meinivo does not sell personal information for cash. Because some laws define sale or sharing broadly, a disclosure to a survey or advertising partner could fall within those terms; disabling the provider or advertising choice stops new disclosures for that purpose. We honor applicable opt-out preference signals on our web surface, which has no non-essential trackers. Where rewards qualify as a privacy-related incentive, the Notice of Financial Incentive explains material terms, value method and withdrawal.

Brazil

LGPD rights include confirmation, access, correction, anonymization/blocking/deletion where applicable, portability, information about recipients and consent consequences, revocation and review of decisions. Brazilian transfers require the applicable ANPD mechanism and Portuguese transparency before release.

Canada, Australia and New Zealand

You may request access/correction and challenge compliance. Cross-border processing is disclosed and remains subject to contractual accountability; Australia and New Zealand releases require their cross-border disclosure/accountability gates.

Other regions

We apply equivalent access, correction, deletion and consent-withdrawal channels unless local law requires more. Country-specific language, local representative/DPO, registration, breach notice, localization or transfer steps are release gates, not assumptions.

10. Contact, complaints and changes

Send privacy requests to colin-mario.koese@bitora.de. You may also contact the relevant survey provider for data controlled in its environment. We will clearly notify material changes and request renewed acceptance/consent when required. Version privacy-2026-08-23-v5; bundle meinivo-global-2026-08-23-v5.