Last updated June 17, 2026
1. Scope and controller
This Privacy Policy explains how Informon handles personal data when people visit the website, sign in, use Scout Loops, submit topic requests, update profile settings, send feedback, or contact us. Informon is responsible for the product experience at informon.com and for deciding why and how application data is used.
The service is currently designed for invited professional and adult users. It is not intended for children, and users should not submit sensitive personal data, secrets, regulated client data, or confidential company material unless Informon explicitly supports that use in a later plan or agreement.
2. Data we collect
Informon may collect account and access data such as email address, authentication identifiers, invitation status, workspace membership, role, sign-in events, and session metadata. If profile features are used, Informon may also store preferences such as professional role, goals, interests, platforms, tools, skill level, preferred time commitment, and learning context.
Product data may include submitted topics, saved Scout Loops, notes, outcome choices, feedback signals, generation request status, generated learning content, page context connected to feedback, and contact messages. Technical data may include device, browser, IP-derived network information, log entries, diagnostic data, and security events needed to operate and protect the service.
If paid plans are introduced, Informon or its payment processor may collect billing contact details, plan information, tax information, transaction metadata, and payment status. Informon does not store full card numbers directly.
3. How we use data
Informon uses data to provide the product, authenticate users, enforce invite-only access, maintain workspaces, display Scout Loops, store topic requests, remember outcomes, respond to support messages, and keep the service secure.
Informon also uses profile settings, selected topics, learning preferences, and feedback signals to personalize Scout Loops and recommendations. This personalization is meant to make a first pass more relevant to the user's role, tools, current skill level, platform, and available time.
Aggregated or de-identified product signals may be used to understand which loops are useful, improve product quality, prioritize features, debug failures, and measure whether the service is working as intended.
4. Legal bases for processing
Where privacy law requires a legal basis, Informon processes data to perform the service requested by the user, including account access, workspace access, Scout Loop delivery, topic requests, support, and product settings.
Informon may also rely on legitimate interests to secure the service, prevent abuse, diagnose errors, improve the product, understand usage, and communicate about service-related changes. Consent is used where required for optional cookies, marketing, or optional communications. Some processing may be necessary to meet legal, tax, accounting, or security obligations.
5. AI-assisted personalization
Scout Loops and recommendations may be generated or assisted by AI systems. Informon is designed to use only the information needed to shape a useful learning session, such as the requested topic, relevant profile preferences, and practical constraints. Informon reduces unnecessary identifiers in generation workflows.
Users should not put secrets, credentials, private client data, regulated data, or highly sensitive personal information into topic requests, notes, feedback, or prompts. AI-assisted content can be incorrect or incomplete, so users should verify commands, code, claims, and sources before relying on them.
6. Processors and infrastructure
Informon uses third-party infrastructure providers to run the service. Current core providers include Vercel for hosting and deployment and Supabase for authentication and application data. Informon may also use email delivery, analytics, observability, payment, security, and AI providers as the product grows.
These providers may process data in locations outside the user's country. When international transfers require safeguards, Informon uses appropriate transfer mechanisms made available by those providers, such as standard contractual clauses, adequacy decisions, or equivalent safeguards.
9. Retention
Informon keeps account, workspace, profile, learning, request, feedback, billing, and security records for as long as needed to provide the service, preserve user history, maintain security, resolve disputes, meet legal obligations, and support legitimate product operations.
Retention periods vary by data type. Some data can be deleted when an account or workspace is closed, while logs, billing records, security records, backups, and legal records may be retained for longer where necessary.
10. Security
Informon uses safeguards appropriate for a profile-aware learning product, including encrypted transport, hosted authentication, access-controlled databases, row-level data policies, deployment controls, operational logs, and least-privilege handling of production secrets.
No internet service can guarantee perfect security. Users should keep their email accounts secure, avoid sharing sign-in links or codes, and avoid submitting secrets or confidential material that the product is not designed to protect.
11. User rights
Depending on location, users may have rights to access, correct, delete, export, restrict, or object to certain processing of their personal data. Users may also have the right to withdraw consent where processing is based on consent.
Requests can be submitted through the Contact page. Informon may need to verify the requester's identity and may keep limited records of requests to meet legal, security, and audit obligations. Users in the European Economic Area or similar jurisdictions may also have the right to complain to a local data protection authority.
12. Changes to this policy
Informon may update this Privacy Policy as the product, providers, features, or legal requirements change. Material changes will be reflected by updating this page and, where appropriate, notifying users through the product or by email.
13. Contact
Privacy questions, data requests, and security concerns can be submitted through the Contact page.