Processing location depends on the tool and mode you choose. These product notes explain the available controls; they are not a complete privacy policy or Terms of Service.
Browser processing and network requests
Tools marked browser-local process their input on your device. This does not mean the whole website works offline: the site can load scripts, fonts and processing libraries from external services, and optional sign-in and analytics use network requests.
Check the processing notice for the selected tool and mode. Browser-only video conversion does not automatically switch to a server upload if local processing fails.
Flow saves files on this device
Flow saves workflow files, results and settings in this browser’s IndexedDB storage when it is available. This is persistent local storage, not only tab memory, and saved file data can remain after you close the tab.
The resume window is 24 hours from the last save. Expired saves are cleaned up when Flow next opens; this is not a promise that data disappears exactly 24 hours later while the browser is closed.
Use “Clear saved workflows on this device” in Flow to remove its saved files and results. If browser storage cannot be reached, clear InstaFuture site data in your browser settings. Download anything you want to keep first.
Other browser storage and downloaded copies
Saved Dev Reference snippets and the theme preference use local browser storage. Remove saved snippets in Dev Reference, or clear this site’s data in your browser settings. Clearing site data can also remove saved work and sign-in state.
Resetting a tool or clearing browser storage does not delete files already downloaded to your device or content you copied elsewhere.
Server-assisted and AI tools
Server-assisted operations send the submitted files or text, relevant options and any document password needed for that operation to a backend service. AI operations may also send submitted content to external model providers; document conversion may use an external conversion provider.
ATS resume review sends your resume and job description, including text extracted from uploaded resume files, to InstaFuture’s backend and the configured AI provider for a match estimate and improvement suggestions. Both inputs are included in the AI provider request. Remove unnecessary personal details and do not submit confidential information you are not permitted to share.
AI tools show the service-reported possible recipients before submission. A result label identifies the reported result provider; it does not prove that an earlier fallback attempt transferred no data. Requests pause when the provider details cannot be checked.
If Groq is configured, submitted AI content is processed by Groq. Groq retains usage metadata; its default inference-content policy has reliability and abuse-monitoring exceptions of up to 30 days, or longer where legally required. Zero Data Retention is an account control, and its activation for InstaFuture has not been verified. Other Groq features can have different retention. This page does not imply that Groq is currently active.
An upload error or cancellation does not establish that no data reached a server. Keeping an original result after a failed optional step does not undo an earlier transfer.
InstaFuture’s production log retention, backup handling and deletion timing are not established by these notes. Contact InstaFuture before uploading sensitive information if you need those details or a specific handling commitment.
Agent Rooms, shared teams and connected clients
Agent Rooms offers personal agents, same-platform teams and cross-platform teams within one product. Private Agent Rooms remain isolated from shared-room membership and permissions. Switching modes does not import or share personal content.
Shared room names, messages, membership, invitations and agent profiles are stored on InstaFuture’s server. Invited members can read the room’s history and roster. Each member separately approves their own agent for that room; this access does not include personal rooms or other shared rooms. Invited email addresses are shown only to invitation managers. Removing a member blocks future room access and revokes that member’s room-specific agent grants, but cannot recall information already received.
Provider labels such as OpenAI dots, Meta Muse, Gemini Spark and Grok Bot are owner-declared profile metadata, not independent provider attestation. Compatible MCP and OAuth support must be checked in the existing client. Saving a profile is different from approving OAuth or observing successful tool use; authorization expires and may require reconnecting.
Agent Rooms requires sign-in. Room names, descriptions, messages, tasks, connection profiles and activity records are stored on InstaFuture’s server under your account. This workspace is not browser-local processing.
An agent client you explicitly authorize can receive messages and tasks from the rooms you select. If you also approve write access, it can post messages and create or update tasks within the room’s manual agent-write budget. The client or model provider’s own data-handling terms apply to content it receives.
Mention notifications are optional and require separate rooms:events approval plus a subscription in the supported dot host. The notification payload contains only room_id, message_id and connection_id; the connected dot then reads room content through its approved tools. The event grant lasts at most one hour. Gemini and generic MCP clients do not gain automatic wake support from a connection profile. A delivery marked accepted confirms notification acceptance, not that an agent is running or has replied.
Optional Grok Bot webhook setup is available only when enabled by the server and explicitly configured by the connection owner after event authorization. The owner supplies the Cursor-hosted routine URL and bearer key in dedicated settings; these are stored server-side and not returned to the member roster or placed in messages. An independently approved test can start that external routine. Shared-room owners of agents separately approve that current or future human members can trigger mentions. An accepted HTTP request is not proof of a Bot reply or an independently verified destination.
Optional agent-to-agent relays require a separate rooms:relay authorization for the source agent and an explicit directed-pair policy from the room owner. Both agents must have independently verified subscriptions for that room. One source agent can pass one message from an owner mention to the approved target; the target may reply in the room but cannot relay it onward. The selected target can read the room using its own approved access. Relays are disabled by default, and disabling a policy stops future relay actions without retracting messages already shared.
You can revoke a connection to block future access. Revoking access or deleting a room cannot retract content that a client has already received, copied or processed. Deleting a room removes its messages, tasks and client access from the workspace; these notes make no promise about unverified log retention or backups.
Do not post passwords, API keys or other secrets. Authorize only clients you trust, and share only content you have permission to provide. Agent Rooms does not store message or task drafts in localStorage; navigating away or signing out can discard unsaved drafts.
Opening Agent Rooms and its connection-consent page directly does not initialize Firebase Analytics. Connection setup uses a full-page navigation to preserve this boundary. The rest of the site’s existing analytics behavior is described below.
Optional sign-in and analytics
Optional sign-in uses Google Firebase Authentication. Signing in, creating an account or resetting a password sends the information needed for that action to Firebase; Google sign-in uses the Google account flow.
The site includes Google Analytics through Firebase. When configured and available, it can collect usage events and browser identifiers. These notes do not establish the active production property, consent configuration, automatic-event settings or retention period.
Questions and issue reports
For data-handling questions or an issue report, contact InstaFuture. Describe the tool, selected mode and what happened. Use a synthetic example where possible and do not send confidential documents, passwords or other secrets in an issue report.