How OmniKit handles your data.

Browser utility tools process your files, text, JSON, generated passwords, QR contents and results locally. Account and shared-room features use the server as described below.

Server video downloads

Instagram Reels Downloader sends the selected video ID to a separate server worker. It stores the account ID, video ID, title, quality and job status, and temporarily stores the generated media file. Files expire after the configured retention period, normally 15 minutes. Job records are scheduled for deletion about 24 hours after expiry. Instagram receives worker requests; OmniKit does not request your Instagram password or cookies. Quota counters use hashed account IDs and expire after two days. Download links are single-use and expire after 60 seconds.

What this browser remembers

IP Address Finder contacts ipify to check IPv4 and IPv6 separately when you choose Find my IP. It contacts GeoJS for location and network details when you choose either lookup button. Both services receive your connection address. GeoJS receives your connection address and the public IP you search to return approximate location, network and optional reverse DNS details. OmniKit does not save or log searched addresses or returned details. Results stay in page memory until you copy or download them. Choosing the map link opens Google Maps with the approximate coordinates. See the GeoJS privacy policy for its handling of requests and error logs.

Screenshot → Developer Info reads colors, measurements and English text locally. Text recognition downloads its runtime and model from OmniKit; it sends neither your screenshot nor the extracted text to a server. Results stay in page memory until you copy or download them. Recognition does not save a screenshot or text in browser storage.

We store your theme, favorite tool identifiers, and your last 20 opened tool identifiers in local storage. Clearing this site’s browser data removes them. Browser utility inputs and results are processed locally. Any tool-specific storage or sharing is explained on its page.

Daily tool allowances

YouTube Watch Room, Temporary Static Site, Bulk File Renamer, Bulk QR Generator and Cross-Device File Drop require sign-in. Free accounts receive 3 uses per tool per day; Plus removes these daily count limits. OmniKit checks your current plan and stores daily counters and hashed action identifiers until midnight India time. This check does not upload filenames, file contents, QR text or room identifiers. Other tool-specific sharing still happens as described on each tool page.

Feedback

Submitting feedback sends your message, chosen feedback type, related tool and optional reply email to OmniKit. Messages are visible only through the admin inbox. Deletion is scheduled after 90 days. Short-lived network rate limits help prevent spam. Feedback is not sent automatically, and the form does not upload your tool inputs, files or results. Sharing a tool sends only its public page link through the sharing option you choose.

Analytics and service logs

Recent tools includes an optional activity summary for this browser. Local storage holds daily completed and unsuccessful action counts by browser tool identifier. The summary covers the last 30 UTC calendar days; older counts are removed on the next activity write. Inputs, results, filenames, account identifiers and exact action times are not recorded. Counts are never uploaded, synced or used for billing. You can turn recording off or clear the counts from Recent tools. Activity is shared by people using this browser profile and remains after sign-out.

Account sync is manual by default. When you choose “Save this device to account”, we store your favorite tool identifiers, recent tool identifiers and theme in your account. Restoring on another device replaces that browser’s preferences. Tool inputs and results are never included. Restored preferences remain in browser storage after sign-out.

You can enable automatic preference sync for this browser on your account page. While OmniKit is open, favorites, recent tool identifiers and theme are saved and restored automatically. You choose whether to start with this device or your saved account preferences. Competing changes pause sync until you choose which copy to keep. Signing out or changing accounts turns it off. The browser stores the account identifier, sync setting and last synced preferences to retain unsynced changes across reloads. You can turn sync off at any time; tool inputs and files are never included.

No third-party analytics provider is enabled. The backend records request IDs, route patterns, status codes, and timing. It does not log tool contents. Hosting providers may maintain their own access logs.

Accounts and sessions

When Google sign-in is enabled, the sign-in page loads Google's sign-in button. Choosing it lets Google share your account identifier, name and email with OmniKit. We verify the signed identity on the server and store the Google account identifier with your profile. Google identity tokens are not saved in browser storage or service logs. Google also handles the sign-in interaction under its own privacy policy. A Google-only account can use an emailed recovery link to add a password.

Signing up sends your name, email and password to the account service. We store a salted password hash, profile information and hashed session tokens. An HTTP-only cookie keeps you signed in for up to 30 days. Access tokens stay in page memory. Signing out revokes this session. Verification and password recovery send single-use links to your email address. The database stores only link hashes and expiry times. Resetting a password invalidates existing sessions. From your account page, you can change your display name or delete your free account using your current password and explicit confirmation. Deletion removes your account and saved account preferences and invalidates all sessions. Browser preferences remain until you clear this site's browser data. Existing backups, service logs and previously sent email messages are not removed by this action.

Your account page lists active sessions with an approximate browser and operating-system label, sign-in time, latest refresh time and expiry. We do not store raw browser user-agent strings or IP addresses for these labels. You can sign out individual sessions or your other active sessions. Changing your password requires your current password and signs out all existing sessions. Local browser preferences remain available.

Admin settings

Availability checks load public tool settings and planned prices; they do not upload your tool inputs or results. Settings changes by an administrator are recorded with the administrator account identifier, time and changed settings. Only administrators can read this history. The last 50 changes are retained until newer entries replace them; deleting an administrator account does not erase that shared history.

Billing retention

Optional Pro payments are processed by Razorpay. Card details, payment contact details and bank authentication are entered directly in its checkout. OmniKit does not store your card number, CVV or OTP. We send the payment amount, an opaque account reference and a checkout receipt to Razorpay.

For manual Pro purchases, we retain account identifiers, checkout and order references, amounts, status and access dates to reconcile payments, handle refunds and prevent duplicate access grants. The account's access history is deleted with the account; checkout recovery records can remain afterwards and do not recreate a deleted account. Processed webhook records expire after 90 days. Pending deliveries and unresolved attempts remain until they can be safely resolved. Razorpay keeps its own records under its privacy policy.

For legacy recurring billing, expired checkout URLs are removed, completed event records expire after 90 days, and confirmed terminal checkout records are retained for 90 days before being replaced with minimal hashed request and subscription receipts. Those hashes remain to block repeated checkout requests and recognize late events. Unresolved attempts and pending events are retained until they can be safely resolved. Account deletion does not erase these recovery records or hashed receipts; active or unresolved billing blocks deletion. Provider records follow the provider's own retention policy.

Watch rooms

When real email delivery is enabled, our email provider receives your email address and the account message. In local development, messages may instead be saved to a private local outbox. Links expire after 24 hours for verification and 30 minutes for password reset.

Room IDs, YouTube video IDs, playback state and connection identifiers are shared with the room server and participants. The embedded YouTube player connects to YouTube and is subject to its privacy policies.

Rooms store their state and temporary participant identifiers in Redis. State expires after one hour without activity. Anyone with the room link can join, and an active participant takes over host controls when the host leaves.

File drop, collaboration and study rooms

File-drop rooms last 30 minutes; collaboration and study rooms last two hours. Redis stores room identifiers, a hash of the access key, temporary connection identifiers and display names until the room expires. Collaboration notes, tasks, timer state and selected music video are stored on the server and shared with anyone holding the complete invite. They are not encrypted at rest by this feature. Unsaved note drafts stay in page memory. No account is required.

Study rooms also store the latest focus completion time, sequence and temporary connection identifiers eligible for that completion. Personal progress stays in page memory by default. If you choose to remember it, this browser stores completion identifiers and dates for up to 90 days and 500 sessions. Old entries are removed when the study room is opened or progress is saved. No task text, names or invite keys are stored in personal progress; it is never uploaded or included in account sync. Turning saving off removes saved history. You can also clear it from the room.

File Drop sends filenames and file bytes through an encrypted WebRTC data channel after the recipient accepts. OmniKit relays connection details, including network candidates, but does not store the files. Devices exchange network addresses; the configured STUN service helps them discover a route. A configured TURN relay may carry the encrypted connection when a direct route is unavailable; it sees network addresses and traffic timing but cannot read the encrypted file contents. Received files remain in page memory until saved or the page closes. Smart File Toolbox inspects, hashes and transforms files locally without uploading them.

One-time secret links

Secret Text Share encrypts text with AES-GCM in your browser. The server stores only encrypted text and its nonce for up to 10 minutes. The decryption key stays in the link fragment and page memory; it is not sent to our API. Anyone with the complete link can view it. Opening the page does not consume the message; clicking View secret atomically removes it before decryption. Reopening, reloading or an interrupted response cannot restore a consumed message.

Creating links requires an account. Server creation counts are kept by UTC day in your account for about 31 days and removed with account deletion. Redis holds temporary quota counters and retry receipts with hashed account identifiers for up to two days. Receipts contain request fingerprints and counts, not plaintext or encryption keys. Encrypted links expire independently of account deletion. Clearing browser activity does not reset server allowances. Browser tools remain without action quotas.

Temporary file links

Temporary File Share encrypts the file and its filename with AES-GCM before upload. The server stores encrypted bytes, an owner identifier, a retry fingerprint and expiry times. The key stays in the complete link's fragment and is never sent to our API. Anyone with that link can download until it expires after one hour. Opening the page does not download the file; you choose when to download and save it.

File links support up to 10 MB and 10 new links per UTC day. Retrying the same upload does not use another allowance. Expiry immediately prevents new downloads; automatic cleanup removes encrypted bytes about once a minute while the service is running, and on startup. Small retry records expire after 24 hours. Recent daily counts and admission markers remain privately in the account until pruned by a later upload or account deletion. Deleting a link removes its stored bytes; deleting the account disables all its links and removes its file records. Files already downloaded by recipients cannot be recalled.

Tool workflows

Workflow Builder processes text and data locally, without server requests. Inputs, intermediate results, final results and workflow definitions stay in page memory and are not automatically saved or included in account sync. Workflow export includes only its name and supported steps. Result downloads include the result you choose to save. Imported definitions cannot run scripts or request external services.

Shared code snippets

Code-to-Share encrypts the code, title and language in your browser. Redis stores encrypted bytes and a fixed expiry of one, six or 24 hours. The secret stays in the complete link's fragment and is never sent to the API. Optional passwords are used locally to derive an encryption key and are never uploaded. Anyone with the complete link and any required password can copy the code. Copied content cannot be recalled.

Expiry and early removal delete stored snippet bytes. Hashed network counters enforce ten new links per UTC day; retry fingerprints and hashed removal keys are retained for up to 48 hours. Drafts, passwords and keys stay in page memory and are excluded from account sync. Password protection does not prevent someone with encrypted bytes and the complete link from trying passwords offline; use a strong password.

Temporary static sites

HTML, CSS and JavaScript files are uploaded without encryption and are public to anyone with the hosted link. Redis stores them for the selected one to 24 hours. Expiry and early removal delete the stored site and stop new requests. Copies already downloaded or open in a browser cannot be recalled. No-index and no-cache headers do not make a site private.

Creation limits use a hashed network identifier until the next UTC day. Hashed upload fingerprints and removal-key hashes support safe retries for up to 48 hours. The early-removal key stays in this page's memory; it is never saved in browser storage or account sync. Hosted JavaScript runs without access to OmniKit account cookies or browser storage.

Background removal

Background Remover downloads its processing model and runtime from OmniKit and runs them in your browser. Your image is not uploaded. The browser may cache processing files, but your image and result are held only in page memory until you choose to download the result.

Operational error reports

When enabled, the browser reports a fixed error category to OmniKit to help identify failures. Reports contain no tool inputs, filenames, page URLs, error messages or stack traces. API logs record request identifiers, route patterns, status codes and timing. Reports are rate limited and do not use analytics cookies.

Future tools

Cloud history and server-based AI services are not enabled. Their data handling will be explained before launch.