Privacy Policy (Mobile App)
Last updated: November 8, 2026
This policy applies to the Linesol mobile app for participants, available on iOS and Android. For the Linesol Dashboard (customer web app), refer to the Dashboard Privacy Policy.
Definitions
Participant: A "participant" refers to any app user with an account, regardless of whether they answer any surveys. Participants are governed by this Privacy Policy for all actions within the app, including account creation, data management, and answering surveys.
Study: A "study" refers to a complete research project created by a customer through the Dashboard, consisting of multiple question and/or user feature variations. From the participant perspective, "studies" are presented as individual survey questions that participants may answer with yes/no responses or skip. An answer may also create a profile-linked targeting feature consisting of the study number and the participant's yes/no answer. That feature does not include the specific question-card variation shown. Separately, the response record used to operate and analyze a study may include the question-card variation and response. Study responses, along with selected user features, may be processed, aggregated, and included in reports delivered to the customer, as described in this policy.
0. Scope
This policy applies exclusively to the Linesol mobile app used by participants for answering surveys. It does not cover the Linesol Dashboard, which is used by business customers to create studies. The Dashboard has a separate privacy policy.
1. Who We Are
We operate the mobile app "Linesol" (the "App"). We are committed to protecting the privacy of participants and collect only the data necessary to provide our services. In this policy, "user data" refers to the personal data collected from participants, as detailed in section 2 below.
2. Personal Data We Collect
- Username and password – required for account creation and authentication.
- User features – profile data used to match participants to studies. This can include self-reported demographic category-feature pairs, verified referral-code category and feature values, and study-answer pairs consisting of a study number and a yes/no answer. The study-answer targeting pair does not contain the question-card variation shown. Profile-linked feature data can be removed using Delete User Data or by deleting the account. Anonymized versions already incorporated into reports or datasets may be retained as described below.
- Payout details – for Revolut withdrawals, this may include payout identifiers needed to process payment through Revolut. For USDC withdrawals requested through https://dashboard.linesol.online/usdc, this may include a participant-provided Solana wallet address submitted for the payout, limited payout record data stored in Firebase (such as amount, transaction identifier or on-chain transaction signature, and user ID), and payment-processing data handled by Coinbase or another payout infrastructure provider we use to execute the transfer.
- Survey response records – including the study identifier, answer, question-card variation, and response time – used to administer studies, maintain data quality, and produce research outputs. Sharing anonymized response data with clients for research or AI training requires the participant consent described below.
- Firebase installation ID, push token, and last active timestamp – used for delivering notifications (if enabled) and account management.
- OneSignal-related notification data (for users who enable push notifications), such as device/app instance identifiers, push subscription status, and message delivery metadata – used only to send and manage push notifications.
- Service activity and quality-control metadata – including response timestamps and account activity used to verify response authenticity, detect fraud, and maintain data quality.
- IP address – sent to IP-based location and currency providers to infer approximate country eligibility and currency, and to exchange-rate providers when converting displayed study prices. The app does not access GPS for these functions. During signup, Linesol also stores a hashed IP signal to limit repeated signups and help prevent abuse; the hash is not a precise location.
- External websites or apps opened from links in study cards may receive your IP address and other information normally sent by your device when you visit them. Those destinations are operated by third parties and are subject to their own privacy policies.
- Hashed installation identifiers and signup timestamps — We use these identifiers and timestamps to help detect suspicious account activity, prevent abuse, and protect the integrity of the platform.
3. How We Use Participant Data
- Username and password: to create and secure participant accounts.
- User features: anonymized for generating reports; profile-tied for account management. User features may be aggregated, combined, or transformed into composite variables for analytical purposes, calculated and updated on a 24-hour basis. Participants have visibility over composite features in the app and may opt out by selecting "rather not say" or equivalent opt-out options. Referral-code category/feature values and study-number/answer pairs may be used to match participants with studies that target those features. The study-number/answer feature does not identify the question-card variation shown.
- Study response records: to record and process answers, the question-card variation shown, response timing, and related study information for study operations, quality control, and research outputs. These records are distinct from the profile-linked study-number/answer feature.
- Payout details: to process, execute, and track Revolut and USDC withdrawals, including USDC withdrawals requested through https://dashboard.linesol.online/usdc.
- Anonymized survey responses: used for anonymized reports commissioned by companies for AI (LLM) model training and market research (only with explicit consent).
- Firebase data (installation ID, push token, last active): for notifications and account management.
- OneSignal notification data: to deliver push notifications when enabled, monitor delivery status, and manage notification preferences.
- Response metadata and activity patterns: to verify authenticity of accounts and responses, detect fraud, maintain data quality, and ensure compliance with our Terms of Service.
- Infer your approximate location and currency from your IP address so survey prices can be displayed in a currency appropriate for your location. We use currency-code detection providers and exchange-rate services for this purpose. If detection is unavailable, the app defaults to USD; if an exchange-rate lookup fails, the price may remain in its original currency.
- User-feature category/feature nomenclature and related account activity: to enforce platform and legal compliance, which may include modifying or renaming nomenclature, removing/deleting or rejecting non-compliant elements.
- Profile update records (including frequency and patterns of changes): to match participants with relevant studies, maintain dataset integrity, and detect/prevent abusive profile manipulation.
3A. Profile Data and Updates
We collect and store records of changes participants make to user features (demographic, behavioral, and preference information participants self-report). This information is used to:
- Match participants with relevant studies.
- Maintain the statistical integrity of our research datasets.
- Detect and prevent abuse, such as excessive or manipulative profile changes.
We track the frequency and patterns of profile updates. If we detect suspicious activity, we may review the account and take appropriate action, including suspension or deletion. This processing is necessary for our legitimate business interests in providing high-quality data to clients and operating a fair platform.
4. Legal Basis under GDPR
- Account and core features → performance of contract.
- Processing and sharing anonymized response data for client research/AI use → explicit consent (via app checkbox agreeing to this Privacy Policy and the Terms of Service).
- Authenticity verification and fraud detection → legitimate interests (maintaining service integrity, preventing fraud, ensuring data quality for clients).
- Tracking profile update frequency and patterns for abuse prevention and platform integrity → legitimate interests.
- Where data is effectively anonymized and no longer relates to an identifiable person, we may also rely on legitimate interests and the position that such anonymized data may fall outside GDPR personal data scope.
5. Sharing & Third Parties
We do not sell participant data. We share data only with:
- Google Firebase (authentication, database).
- OneSignal (push notification delivery and related messaging infrastructure, where notifications are enabled).
- IP-based location and currency services: ipwhois.app is contacted during sign-up to infer a country for service availability checks. When displaying survey prices, ipwhois.app and, if needed, free.freeipapi.com are contacted to infer a currency from the device's IP address. These providers receive the IP address as part of each request.
- Exchange-rate services: api.frankfurter.dev is tried first to convert a displayed survey price to your detected currency. If that lookup fails, open.er-api.com may be queried as a fallback. These services receive the device IP address as part of normal network traffic; Linesol does not send your GPS location to them.
- Revolut (payment processing for Revolut withdrawals).
- Coinbase and, where applicable, related blockchain or wallet infrastructure (for USDC payout processing and transaction settlement).
- Paying clients (anonymized reports and anonymized raw response datasets for research and analytics, with participant opt-in).
- Internal teams and limited third-party service providers, solely as necessary for fraud/abuse prevention and platform integrity safeguards.
- Sub-processors listed here: firebase.google.com/terms/subprocessors
5A. Sharing of Anonymized Data
With participant consent, Linesol may share anonymized raw response data with paying clients. This can include one-hot encoded yes/no survey answers, associated user feature vectors, and the study/question-card variation needed for analysis, without direct identifiers. Feature vectors may include referral-code category/feature values and study-number/answer pairs used for study targeting.
This sharing supports market research, AI training, and custom statistical/modeling work (including multiple correspondence analysis (MCA) for latent dimensions and composite variables), in addition to aggregated reporting.
Shared anonymized datasets do not include direct personal identifiers such as names, email addresses, precise locations, financial account/payment details, or similar direct PII. However, participants acknowledge that a theoretical re-identification risk can still exist in rare cases where unique combinations of features appear.
Client access to anonymized datasets is provided only under contractual restrictions that prohibit: (i) attempts to re-identify participants, (ii) resale or redistribution of the data, and (iii) use beyond the client's internal analysis, research, and modeling purposes.
6. Data Retention
Participants can use Delete User Data to clear profile-linked user features, including referral-code category/feature values, referral verification details, and study-number/answer pairs. Deleting an account also removes its profile data. This does not erase separate study response records already collected, referral-code redemption records retained to prevent reuse, or anonymized data already incorporated into reports or datasets. Such records may be retained for study operations, security, legal compliance, or research as described in this policy.
Participants may also choose to delete their profile-tied user features while keeping their account active. In this case, only the profile-linked feature data used for matching is cleared. This includes referral verification details and study-number/ answer pairs. The referral code itself may remain marked as redeemed so it cannot be reused. Separate response records and anonymized versions already incorporated into reports or datasets may be retained.
If a participant deletes their account while having a non-zero balance, the remaining balance will no longer be withdrawable and will be forfeited. Participants are encouraged to withdraw their earnings before initiating account deletion.
7. Participant Rights (GDPR / CCPA)
Participants have the right to:
- Access their personal data.
- Correct inaccuracies in their personal data.
- Delete their accounts and associated personal data: username and password, profile-linked user features (including referral-code features and study-number/answer pairs), Firebase ID, push token, and last active timestamp are deleted or cleared. Separate study response records, referral-code redemption status, and payout records may be retained for study operations, security, accounting, compliance, fraud prevention, or transaction tracking. Anonymized or aggregated response data already incorporated into reports or shared datasets may also be retained.
- Withdraw consent for future AI training by not participating in surveys or deleting their accounts (consent for past survey responses cannot be revoked).
- Request data portability for their personal data in a machine-readable format by emailing us.
Contact us at: hello@linesol.com
8. Children
The App is strictly for users aged 18 and above. We do not knowingly collect data from individuals under 18.
9. Changes to this Policy
We may update this Privacy Policy from time to time. If we make material changes, we will notify participants in-app (and may also notify by push notification via OneSignal (if enabled) or email where available) before or when the changes become effective, and we may require re-acceptance before continued use.