app-docs.md

InferencePort App Documentation

This document gives the assistant a structured reference for the public web interface, the main settings surfaces, account and media flows, and the current privacy and terms policies. Use the section list tool first, then read only the section that answers the user’s question.

Pages

• index.html is the main app experience. It includes the chat workspace, bottom composer, welcome screen, sidebar, media panel, settings access, authentication entry points, and share-import banner.
• admin.html is a separate administrator page and is not part of the normal end-user workflow.
• privacy.html explains what data the app collects, how it is used, and what the user can expect from storage and third-party services.
• terms.html explains acceptable use, prohibited use, account expectations, and service disclaimers.

Chat Workspace

• The welcome view is the landing state before a session has visible history. It exposes the centered input for starting a chat.
• The chat view shows the active conversation, message variants, tool calls, generated media, and message actions like copy, edit, regenerate, and continue.
• The main composer supports plain text, markdown-style input, attachments, tool toggles, and prompt editing.
• User message editing creates a new version of the prompt. Follow-up turns continue from the active branch instead of the original branch.
• Assistant responses can have multiple versions. Users can switch between versions, regenerate a reply, or continue generating from the selected assistant message when appropriate.

Sidebar And Media Library

• The sidebar contains the chat session list, deleted chat access, media library access, settings access, and account shortcuts.
• The media library shows folders and saved files, including text documents, rich text documents, images, video, audio, and assistant-generated assets.
• Signed-in users can upload files, create folders, create notes, rename items, move items, edit text documents, restore trashed items, and permanently delete files.
• Signed-out or guest users are restricted to download and delete behavior in the media area. Upload and creation actions require sign-in.
• The three-dot item menu exposes contextual actions like download, rename, move, trash, restore, and delete forever depending on item state and the user’s authentication status.

Settings And Account

• The Chat settings tab controls theme and tool toggles for web search, image generation, video generation, and audio generation.
• The Chat settings tab also shows tool usage progress bars, including the free-plan daily web search limit and other tool quotas returned by the usage service.
• The Personalization tab lets signed-in users edit a private system prompt that is stored for their account and sent before chats.
• The Memories tab lets users save, edit, and delete persistent short memories that can influence future chats.
• The Account tab lets signed-in users edit usernames, review the active subscription plan, inspect current device sessions, revoke other sessions, open billing, and delete the account.

Modals

• Auth modal: sign in, sign up, or continue with supported OAuth providers.
• Confirm modal: generic confirmation for destructive or sensitive actions.
• Text prompt modal: used for naming files or folders, entering URLs, and other short-form prompts.
• Image modal: full-size image preview.
• Device session modal: details for a logged-in device session with revoke controls.
• File viewer modal: view or edit attached text files from messages.
• Tool call modal: shows details of tool arguments and results from assistant tool usage.
• Media picker modal: choose saved media items to attach into a draft.
• Folder picker modal: choose a destination folder when moving library items.

Tool Limits And Credits

• Usage data is fetched from https://sharktide-lightning.hf.space/usage.
• The app shows quota progress when that endpoint returns usage metrics such as daily chat credits, image generations, video generations, audio generations, and free-plan web searches.
• Free accounts have a local limit of 15 web searches per day inside the app. When the limit is reached, the web search tool should explain that the user has hit the daily free-plan search cap and suggest waiting for reset or upgrading.

Data Collection

When a user visits the site, the app may collect or process:

• Basic connection metadata such as IP address, browser user agent, and timestamps for security, session tracking, rate limiting, and device session management.
• Turnstile verification state to confirm the visitor is human before using protected routes or WebSocket actions.
• Authentication tokens and account identifiers when a user signs in.
• Chat content, uploaded media, saved memories, settings, personalization prompts, and device session records when those features are used.
• Usage and subscription information returned by the billing and quota services.
• Temporary guest identifiers and client identifiers stored in local storage so guest sessions and per-device usage can work.

The app should not claim zero collection. It stores and processes the data needed to provide chats, uploads, settings synchronization, abuse prevention, and billing-aware limits.

Privacy Policy

InferencePort uses data to operate the service, store chats and media, apply user settings, enforce limits, detect abuse, and support account management. If a user signs in, account-linked data can be synchronized across devices. If a user stays signed out, temporary identifiers may still be stored locally so guest sessions and limits continue to work.

Uploaded files, chat messages, saved memories, and personalization prompts may be stored on the service so the product can retrieve them later. Generated assets may also be stored so they can be re-opened or downloaded. Third-party services may process requests for authentication, verification, billing, quota tracking, web search, and model execution.

The privacy policy should explain that:

• Users should avoid submitting highly sensitive personal data unless they understand the risks.
• The service may log operational metadata for debugging, billing, moderation, and abuse prevention.
• Third-party providers may receive request data needed to fulfill product features.
• Users can delete chats, media, memories, or accounts through the interface, but operational backups or logs may persist briefly where required for reliability or security.
• No guarantee of absolute security should be stated.

Terms Of Service

Ethical, legal use is permitted. Users may use the service for ordinary personal, educational, creative, and business tasks so long as their use is lawful and does not harm others or the service.

The terms should make clear that users must not:

• Use the service to break the law, violate contracts, infringe intellectual property, or bypass security controls.
• Upload or distribute malware, credential theft content, destructive payloads, or instructions intended for abuse.
• Harass, exploit, impersonate, defraud, stalk, or intentionally harm other people.
• Attempt to overload, disrupt, scrape, reverse engineer, or misuse the service infrastructure beyond normal permitted use.
• Use the service to generate or automate clearly illegal activity.

The terms should also explain that:

• Users are responsible for the content they submit and the actions they take using the service.
• Service availability, quotas, model behavior, and features can change over time.
• The service may suspend access for abusive, unlawful, or dangerous use.
• Outputs can be wrong, incomplete, or unsafe and should be reviewed before relying on them.
• InferencePort AI disclaims responsibility for losses or damages resulting from misuse of the service or from users choosing to run risky content.

Troubleshooting

• If uploads are disabled, check whether the user is signed in.
• If web search stops working, check the daily free-plan search limit.
• If a message edit seems to branch incorrectly, make sure the current selected message version is the one the user expects before sending the next follow-up.
• If a response shows a retry button, the assistant request or tool flow failed before completion and can usually be retried directly from the conversation.