Effective and last updated: August 21, 2026
Privacy Policy
A practical explanation of the personal data IPPO processes and the choices available to you.
In short: we use personal data to provide, secure, support, and bill for IPPO. We do not sell personal data or use it for targeted advertising. When you ask IPPO to generate or improve a guide, selected customer content is sent to Google Gemini for AI processing.
1. Scope and roles
This Policy applies to the IPPO website, application, browser extension, waitlist, support communications, and controlled guide-sharing features (together, the Service). “IPPO,” “we,” and “us” refer to the operator identified as IPPO in your subscription record, order form, or other service agreement.
IPPO is generally the organization responsible for deciding how personal data is used for the public website, waitlist, account administration, security, support, and billing. When an employer or other organization provides your workspace and decides what material is recorded or uploaded, that organization may be the controller and IPPO may process customer content on its behalf. In that case, your organization’s privacy notice also applies, and requests about customer content should normally be directed to that organization first.
This Policy covers personal data. It does not govern anonymous or aggregated information that cannot reasonably identify a person.
2. Data we collect
| Category | Examples |
|---|---|
| Waitlist and contact data | Work email, name, company, use case, request status, and support or sales messages. |
| Account and profile data | Authentication identifier, email, name, profile image, job title, department, workspace, role, memberships, invitations, and onboarding state. |
| Customer content | Screen or tab recordings, uploaded videos and documents, screenshots, page titles and URLs captured during a workflow, interaction timing and element signals, guide text, annotations, redactions, brand assets, versions, exports, and share settings. |
| Collaboration and administration data | Project permissions, invite history, approvals, audit activity, enterprise domain and policy settings, notifications, and records of actions taken in a workspace. |
| Billing and usage data | Plan, subscription status, billing cadence, credit grants and consumption, measured AI cost, Stripe customer and subscription identifiers, checkout status, and transaction metadata. IPPO does not store full payment-card numbers. |
| Device, security, and service data | Request timestamps, route and error information, browser or device details made available with a request, IP-derived rate-limit signals where configured, queue and processing status, security events, and performance metrics. |
| Preference data | Theme, layout and view preferences, recent searches stored on your device, onboarding progress, and similar usability settings. |
Recordings and screenshots can contain personal, confidential, or sensitive information visible on the recorded screen. The person or organization initiating a recording is responsible for having permission to capture and use that material. IPPO provides editing and redaction tools, but those tools do not replace appropriate recording practices.
3. Where data comes from
- From you, when you join the waitlist, create or update an account, record or upload material, edit a guide, configure sharing, purchase a plan, or contact us.
- From your organization or collaborators, when they invite you, assign permissions, upload content involving you, or administer a workspace.
- From connected providers, including Clerk for authentication and Stripe for subscription and payment status.
- Automatically from the Service, when IPPO records security, usage, audit, processing, and operational events needed to run the product.
- From the browser extension, only when it is used to record or import an authorized workflow and send the resulting capture to IPPO.
4. How and why we use data
| Purpose | Typical legal basis where applicable |
|---|---|
| Provide accounts, workspaces, recording, guide creation, editing, export, and controlled sharing | Perform our contract or take steps you request before entering a contract |
| Authenticate users and enforce tenant, project, role, and sharing permissions | Contract; legitimate interests in protecting users and the Service |
| Process content with AI and create requested outputs | Contract; your organization’s instructions; consent where required by local law |
| Operate plans, trials, credits, invoices, checkout, and subscription management | Contract; legal obligations; legitimate interests in administering the Service |
| Send verification, invitation, access-decision, security, billing, and service messages | Contract; legal obligations; legitimate interests |
| Prevent abuse, investigate incidents, troubleshoot failures, and maintain reliability | Legitimate interests; legal obligations |
| Improve product usability and performance using service metrics and feedback | Legitimate interests; consent where required |
| Comply with law, resolve disputes, and enforce agreements | Legal obligations; legitimate interests |
If we rely on consent, you may withdraw it for future processing. Withdrawal does not affect earlier lawful processing and may prevent us from providing a feature that requires the data.
5. AI processing
IPPO uses Google Gemini to analyze authorized workflow material and help generate, rewrite, localize, validate, and organize guide content. Depending on the requested operation, IPPO may send selected video frames or screenshots, extracted interaction context, page information, existing guide text, user instructions, and technical prompts to Google.
AI output can be incomplete or inaccurate. IPPO presents generated material for human review and editing; it is not intended to make decisions that produce legal or similarly significant effects about a person.
Google’s handling and retention of API requests is governed by the applicable Gemini service terms and the production account configuration. Paid Gemini services state that prompts and responses are not used to improve Google products, while limited logging may still occur for abuse monitoring. We do not represent that a third-party AI service provides zero retention unless that control is specifically enabled and confirmed for the applicable deployment.
Do not record or upload credentials, payment-card data, health information, government identifiers, or other highly sensitive material unless your organization has approved that use and appropriate safeguards are in place.
6. Sharing and processors
We disclose personal data only as needed for the Service, at your or your organization’s direction, or as required by law. Current product integrations include:
| Recipient | What it does |
|---|---|
| Clerk | Authentication, session management, account identity, and user-management services. |
| Stripe | Checkout, subscription management, payment processing, invoicing, fraud prevention, and related billing operations. |
| Google Gemini | AI processing of selected customer content and prompts for requested guide operations. |
| Microsoft 365 / Microsoft Graph | Delivery of transactional messages such as invitations and waitlist decisions when configured. |
| Infrastructure operators | Hosting, database, object storage, queues, backups, monitoring, and network services selected for the deployment. IPPO’s application is designed to use Convex-compatible data storage, S3-compatible object storage, and Redis-compatible queues. |
Workspace administrators and authorized collaborators can access data according to their roles. Anyone receiving an active share link may access the linked guide subject to its password, expiry, download, and print settings. Removing a share link can preserve a limited audit record while disabling access.
We may disclose information to professional advisers, authorities, or counterparties when reasonably necessary to comply with law, protect rights and safety, investigate misuse, or complete a corporate transaction subject to appropriate safeguards. We do not sell personal data or disclose it for cross-context behavioral advertising.
7. International transfers
The Service and its providers may process data in countries other than where you live. The location depends on the deployment, the workspace agreement, and provider infrastructure. We do not publish a specific hosting region unless it has been confirmed for that deployment.
Where transfer safeguards are legally required, we use the mechanism applicable to the relationship, which may include contractual protections, recognized adequacy decisions, or other lawful safeguards. Contact us if you need information about safeguards applicable to your workspace.
8. Retention and deletion
We retain personal data only for as long as reasonably needed for the purposes described above. Instead of promising unsupported universal periods, we apply these criteria:
- Account, workspace, and customer content are generally retained while the relevant account, project, or service relationship remains active, and then for the time needed to complete deletion, recover from accidental loss, or resolve disputes.
- Deleted files can remain temporarily in backups, caches, processing checkpoints, or provider systems until normal deletion cycles complete.
- Billing and transaction records are retained as required for accounting, tax, fraud prevention, chargebacks, and legal compliance.
- Security, access, audit, and version records are retained according to operational, contractual, and compliance needs. Deleting content does not necessarily erase a minimal record that an action occurred.
- Waitlist and support data are kept while a request is active and for a reasonable follow-up period, unless earlier deletion is requested and no overriding obligation applies.
Workspace administrators can delete supported content through the Service. For account-level deletion or a privacy request, contact us using Section 13.
9. Security
IPPO uses administrative, technical, and product safeguards intended to reduce unauthorized access, alteration, disclosure, or loss. Source-backed controls include authenticated route protection, tenant and project authorization, role-based administration, hashed extension tokens, hashed share-link passwords, HttpOnly share-access cookies, rate limiting, server-side secrets, audit records, and user-directed screenshot redaction.
No internet service is completely secure. Customers should limit access, review generated guides and share settings, remove unnecessary links, redact sensitive screenshots, and report suspected incidents promptly. Additional details are available on the Security page.
10. Your choices and rights
Depending on where you live and the role in which IPPO processes your data, you may have rights to request access, correction, deletion, restriction, portability, or objection; withdraw consent; and complain to a data-protection authority. Rights can be limited by law, another person’s rights, security needs, or a customer organization’s instructions.
Singapore residents may have access and correction rights and may withdraw consent under the Personal Data Protection Act. People in the EEA or UK may also have rights under the GDPR or UK GDPR. If your workspace is managed by an organization, we may direct the request to that organization or assist it in responding.
Send requests to [email protected]. Describe the account and request without sending passwords or unnecessary sensitive data. We may verify your identity and authority before acting. Singapore residents can also learn about complaints and rights from the Personal Data Protection Commission.
11. Cookies and local storage
IPPO uses essential authentication and share-access cookies, plus browser storage for preferences and product continuity. The current application does not intentionally set advertising cookies or app-controlled analytics cookies. Clerk and other infrastructure used for authentication may set cookies necessary to provide and protect their services.
See the Cookie Policy for the current categories, examples, purposes, and browser controls.
12. Children
IPPO is a business workflow service and is not directed to children. You must be at least 18 years old, or the age required to enter a binding service contract where you live. If you believe a child has provided personal data without appropriate authorization, contact us.
13. Changes and contact
We may update this Policy when the Service, providers, or legal requirements change. The effective date at the top identifies the current version. If a change materially affects how we use personal data, we will provide additional notice where required.
Privacy and data-protection requests: [email protected]
General support: [email protected]
This Policy is designed to be accurate to the current product, but it does not replace the workspace agreement, order form, or data-processing terms that may apply to an organization’s deployment.