Your private life admin should stay private.

What IOOK may hold

When you use IOOK, your account may contain information you choose to give it, including tasks, reminders, Memory entries, financial records you import into Accounts, traveller profile information, Watch rules and history, notification preferences, profile details, beta qualification progress, and product feedback.

How IOOK uses it

IOOK uses your information to provide the feature you asked for: understanding a request, saving private workspace data, monitoring a Watch or Autopilot condition, searching travel, sending reminders or alerts, maintaining your account, and measuring whether required founding-beta tests were actually completed. Some AI-assisted features send the content you ask IOOK to analyze through IOOK's server to the configured AI provider, including OpenAI where that integration is used.

Career Intelligence and résumé privacy

Career Intelligence accepts text-based PDF, Word (DOCX) and TXT résumés. The upload is parsed in temporary server memory and the working text is returned to your browser tab. IOOK does not automatically store résumé files, extracted text, AI analyses or tailored drafts in your account database. Closing or reloading the tab clears the working copy. If you explicitly consent, extracted résumé text, your target role and a pasted vacancy description are sent to the configured AI provider to generate the analysis or draft. The AI provider handles the information under its own applicable privacy terms and retention policies; IOOK cannot promise that the provider retains nothing. You may edit extracted text before analysis. Verify every AI-produced résumé before sending it to an employer.

Money, cards and credentials

Do not give IOOK banking passwords, PINs, OTPs, CVVs, UPI PINs or other secret credentials. IOOK is designed not to store raw card credentials or banking login secrets. Payment, bank-consent and booking providers may handle sensitive credentials on their own controlled surfaces.

Beta integrations

Some integrations are explicitly marked BETA, SANDBOX, DEMO or LOCKED. Those labels are functional boundaries. A sandbox provider may use test data; a locked action cannot execute live money movement or ticket issuance.

Notifications and Watch

If you enable email or in-app notifications, IOOK uses your account details to deliver those alerts. IOOK Watch stores the URL, condition and observations needed to perform the Watch. V1 is intended for publicly reachable pages and may not work on login-protected, CAPTCHA-protected or heavily anti-bot pages.

Analytics and beta qualification

IOOK uses limited operational and product analytics to understand whether features work and how the beta is being used. The founding-beta qualification uses successful product-event counts such as “Accounts question succeeded,” “Watch created,” or “notification opened” to verify progress. The qualification does not need the text of your private prompt, merchant name, financial amount, travel route or Memory content simply to count a completed action. Founder analytics are designed around events and limited metadata rather than raw prompt, financial, card or Memory content.

Your controls

• You can remove tasks, Memories, Watches and supported account records from their respective IOOK surfaces.
• You can change profile and notification preferences in Profile & settings.
• You can download a JSON export of your core private IOOK workspace from the in-app beta qualification data controls. The export excludes authentication tokens, provider secrets and provider-controlled credentials.
• You can request deletion of your IOOK account from the in-app data controls or by emailing contact@theiook.com.

Beta reality

IOOK is still a private beta. We are actively testing reliability, provider behavior and product design. We may change this notice as the product and company structure mature; material changes will be reflected on this page.