Privacy notice

How Insighta handles information

This notice describes the information the Insighta application processes to operate researcher and participant accounts, publish studies, match participants, track responses, communicate with users, and administer payments or rewards.

Last updated: July 17, 2026

Information you provide

Depending on how you use Insighta, the application may collect account details such as your name, email address, phone number, login credentials, and OAuth account identifiers. Participant profiles may include age range, education, field, status, location, language, participation preferences, lifestyle or experience tags, and other eligibility information you choose to provide.

Researchers may provide study titles, descriptions, forms, targeting criteria, scheduling details, images, reward information, and study materials. Participants may submit study responses, answers, booking selections, feedback, and support messages.

Information collected during use

The application may record technical and activity information such as IP address, user agent, device-related identifiers, page path, referral source, login events, listing views, study starts, completion timestamps, response duration, and quality-review signals. Cookies are used for login state, authentication return paths, OAuth state, and participant application preferences.

How information is used

• Provide, secure, maintain, and troubleshoot the platform.
• Create accounts, authenticate users, and remember session state.
• Publish and display research opportunities.
• Match participants to studies using profile and eligibility information.
• Track study progress, review response quality, and administer reward status.
• Send verification, account, study, support, and follow-up communications.
• Analyze product usage and improve platform functionality.
• Detect fraud, abuse, duplicate participation, or security incidents.

Service providers and external study tools

Insighta may rely on service providers that process information on its behalf, including hosting and database providers, Stripe for payment-related workflows, email delivery providers, Google or LinkedIn for optional OAuth login, and Anthropic-powered features when those integrations are enabled. A researcher may also link to an external survey or meeting tool. Information you submit directly to that external service is governed by its operator and the researcher’s own disclosures.

Information shared with researchers

Study responses and participation records may be made available to the researcher who published the study. Profile attributes may be used to determine eligibility or matching. Researchers are responsible for describing their own data collection, consent process, retention, and research purpose. Do not assume a study is anonymous unless the study materials expressly say so.

Data retention and security

Information is retained for as long as reasonably necessary to operate accounts and studies, keep business and payment records, resolve disputes, enforce platform rules, and meet legal obligations. No system can guarantee absolute security; the deployment operator should use appropriate access controls, encrypted transport, secret management, backups, monitoring, and deletion procedures.

Your choices

You may choose not to join a particular study. You can update supported profile fields through the application. For access, correction, deletion, or account questions that are not available in-product, contact insightacom@gmail.com. Some records may need to be retained where required for security, payment, dispute, or legal purposes.

Age requirement

The current participant onboarding flow requires participants to be at least 18 years old. Insighta is not designed for children to create participant accounts independently.

Changes to this notice

This notice may be updated as the product, integrations, or legal requirements change. The date above identifies the current version.

Deployment and legal review

This page documents the application’s current technical behavior and is not a substitute for deployment-specific legal advice. Before a public production launch, the operator should identify the legal entity, jurisdiction, retention periods, subprocessors, user-rights process, research compliance requirements, and any institution-specific obligations.