Privacy Policy
Last updated: 12 November 2026
This policy applies to the Venory service at https://venory.jimmyqrg.com (the “Service”). The Service is operated by JimmyQrg under that public name (“Venory,” “we,” “us,” or “our”). For privacy questions or requests, contact ikunbeautiful@gmail.com.
1. Information we handle
- Account and sign-in information. Your name and email address; account and sign-in records; and, if you set a password, a salted password hash rather than the password itself. If enabled and you choose an external sign-in, Google provides us with your verified email and name; JimmyQrg sign-in may provide an account identifier, username, display name, and email. We do not receive your Google password. If you add a profile photo, we store that image.
- Chats, prompts, and drafts. Messages you send, Venory's replies, chat titles, settings, unsent composer text, and references to uploaded files attached to a draft. For signed-in accounts on this service, these are stored on our server and synchronized across sessions on the same account, then cached in each browser.
- Tools and shared content. Tool code, prompts used to create or edit it, title, description, tags, category, settings, cover image, imported-site address and related metadata. A share link lets anyone who has the link open the saved tool and its code. Do not include information in a tool that you do not want to share.
- Files. File names, sizes, types, and the contents of supported files you attach. The Service accepts certain image, PDF, text, and short audio files; videos are refused. Uploaded bytes are stored in the configured object store or, if none is configured, on the server.
- Usage and billing. AI usage counters and plan information. This service offers Stripe subscriptions; we store Stripe customer and subscription identifiers, plan, subscription status, and related dates. Stripe collects and processes payment details on its checkout pages; Venory does not store your card number.
- Live rooms. If you join a live game, we handle the room code, player name, connection status, game state, and messages or answers sent through the game. Room data is held in server memory; an inactive room is removed after about 30 minutes, and rooms reset when the server restarts.
- Technical information. Our server receives ordinary connection and request data. The application uses a visitor's network address transiently in memory to rate-limit requests; it does not add that address to the account record. The host, network, and service providers may create their own operational or security logs under their terms.
Venory uses an essential sign-in cookie that lasts 30 days and is marked HttpOnly and SameSite=Lax (and Secure when served over HTTPS). Google or JimmyQrg sign-in uses a separate HttpOnly, SameSite=Lax state cookie that lasts up to 10 minutes. The browser also stores appearance and interface preferences in local storage, and keeps a local chat copy. Venory does not include an advertising or analytics service in this codebase. The Service loads web fonts from Google Fonts, so your browser requests resources from Google and sends the connection information needed to make that request. See Google's Privacy Policy.
2. How we use information
- To provide accounts, sign-in, chats, saved tools, file attachments, live rooms, and sharing.
- To create AI responses and tools, read attachments you choose to send, search or fetch public information when requested, and apply plan limits.
- To provide optional subscriptions, process payments, send verification codes, and respond to account or support requests.
- To protect the Service, enforce limits and these terms, prevent abuse, troubleshoot errors, and meet legal obligations.
Where applicable law requires a legal basis, we rely on providing the Service you request, our legitimate interests in operating and protecting it, your consent where required, and compliance with legal obligations.
3. AI, files, and public-source features
Venory sends requests to the provider for the model or feature being used: OpenAI for GPT models and Anthropic's Claude API for Claude models. When OpenAI is configured, OpenAI's Decisions API using GPT-6 Luna receives the latest request text and current tool title to classify whether the assistant should edit the current tool. To answer a prompt or build, name, categorize, search for, or update a tool, the Service may send the relevant chat messages, the code of a tool you ask it to change, and contents of supported text, image, or PDF attachments. A tool's own AI feature also sends the prompt and conversation it supplies, plus files you select in that tool; Venory asks before a tool first uses AI, and those requests count toward the signed-in account's usage limits. The model can also request additional file data through a file-reading tool, including binary bytes; audio is not automatically transcribed. Smart Search also sends your query, up to six short recent chat messages, and titles, categories, tags, and descriptions of your saved tools. Venory makes stateless API requests rather than saving a separate conversation with the provider. OpenAI says API inputs and outputs may be kept in abuse-monitoring logs for up to 30 days by default and are not used to train its models unless the customer opts in; see its API data controls documentation. Anthropic's API retention and use depend on its current terms and the operator's account settings or agreements, including any approved zero-data-retention arrangement; see Anthropic's Privacy Center. A different compatible API endpoint configured by the operator also receives the data sent to it and processes it under its own policy.
When a request uses web search, page reading, a public file link, GitHub importing, or a public-data source, Venory sends the relevant search query, address, repository reference, or lookup parameters to the service that provides that information. Depending on what is enabled, providers may include Brave or Tavily; Google Drive; GitHub; jsDelivr or unpkg; Wikipedia/Wikidata; Reddit; X; and public weather, mapping, reference, research, or data services. Venory's server fetches pages, public files, or repository files you ask it to open or import. Imported sites may also make their own requests from your browser to external services. Those providers receive the information and connection data involved in the request and process it under their own policies.
Please do not send passwords, secret keys, payment-card details, or another person's sensitive information in a prompt or file unless you have permission and understand that the selected AI and other providers may receive it.
4. When we share information
We share information with service providers only as needed to run the Service, or when you choose a feature that involves them:
- AI providers: OpenAI for GPT models and Anthropic for Claude models when those server-side API keys are configured, or another compatible API provider configured by the operator, as described above.
- Hosting and file storage: the current deployment uses Fly.io hosting in iad and a private Tigris object-storage bucket for uploads. The bucket's connection uses Tigris's automatic placement setting; Venory does not have a fixed region or backup-expiration period to report. A self-hosted installation may use different providers or local storage.
- Sign-in and email: Google or JimmyQrg when you choose that sign-in option; the email provider configured for the service sends verification messages and receives the destination email address and message contents.
- Payments: this deployment has Stripe subscription checkout enabled. Stripe receives the information needed to create and manage a subscription and collect payment details.
- Search, file, source, and import services: the relevant provider when a feature uses it, as described in section 3. This may include Google Drive, GitHub, jsDelivr, or unpkg when you provide a supported file or repository link.
- Apps you authorize: if Venory sign-in for another app is enabled, and you approve it, we send that app your Venory account identifier, display name, and email address for sign-in.
- Legal and safety disclosures: authorities or other parties when we reasonably believe disclosure is required by law or needed to protect people, rights, or the Service.
We do not sell personal information or share it for another company's advertising. Providers may process information under their own privacy notices and may be located in other countries.
5. Storage, location, and international transfers
The active Fly.io deployment runs in iad (Ashburn, Virginia, United States). The attached volume uses Fly's default encrypted daily snapshots with five-day retention; Fly says snapshots are stored in AWS S3 in us-east-1. Upload bytes go to a private Tigris object-storage bucket. Venory signs storage requests with the auto region identifier and does not configure a fixed region restriction for the bucket. This service does not expose Tigris's exact data placement, versioning, or backup expiration settings, so no specific Tigris location or deletion deadline is promised here. Other providers may process or store data in the United States or other countries, depending on their services and configuration.
6. Retention and deletion
We keep account information, chats, unsent drafts, tools, uploads, and usage records while the account remains open, unless you delete the relevant item or account. We do not currently set an automatic expiration date for inactive accounts. You can delete chats and tools in the app, export chats and tools from Settings, or delete your account in Settings. Account deletion removes the account, sessions, avatar, chats and drafts, saved tool records, uploads, and usage counters from the active application stores, and asks Stripe to cancel an active subscription. A limited list of deleted chat identifiers is retained with the account to stop an offline device from restoring a deleted chat; account deletion removes that list.
Your browser may still have a cached copy of chats after account deletion. The account-deletion flow does not clear browser local storage; clear Venory's site data in your browser to remove that local copy.
Unsaved runs are held temporarily in server memory and may disappear when the server restarts or the in-memory run limit is reached. Live-room data is removed after about 30 minutes without activity or when the server restarts.
Some limits apply to deletion in the current implementation. Deleting a chat does not remove its uploaded files; those files are requested for deletion when the account is deleted. Downloaded GitHub import files are removed automatically after about three days when no saved tool references them. A saved imported tool keeps its files available through its share link until that reference is removed and the cleanup period expires.
Deleted information may remain temporarily in backups until those copies expire. Fly states that volume snapshots are stored in AWS S3 in us-east-1 and kept for five days by default; see Fly.io’s security and data-location information. This does not establish the deletion or backup behavior of the separate private Tigris upload bucket. OpenAI and other providers may also retain information under their own policies, as summarized above. We retain billing or other records for longer only where needed for accounting, legal compliance, dispute resolution, or security.
7. Your choices and privacy rights
- Access and portability. Settings → Export downloads your chats and saved tools, including tool code. It does not currently export profile photos, uploaded file bytes, account records, or usage and billing records. Contact us to request other information.
- Correction. You can change your profile photo and edit or delete chats and tools. Contact us if account information needs correction.
- Deletion. Delete your account in Settings. The current deletion behavior and its limits are described in section 6.
- Other rights. Depending on where you live, you may have rights to access, correct, delete, restrict, object to, or receive a copy of personal information, and to complain to a data-protection authority. Contact us at ikunbeautiful@gmail.com to exercise a right. We may need to verify your request and may retain information when the law allows or requires it.
8. Security
We use safeguards in the application such as salted password hashes, hashed session tokens, request limits, and a separate sandbox origin for generated tools. These safeguards reduce risk but cannot make an online service completely secure. Storage encryption, backups, access controls, and incident handling also depend on the hosting and storage providers and the operator's configuration.
9. Children
Venory is not intended for children under 13, and they may not create an account. If we learn that we collected personal information from a child under 13, we will take steps to delete it. If you believe this has happened, contact ikunbeautiful@gmail.com. If you are under the age of majority where you live, you may use Venory only with the permission and involvement of a parent or legal guardian where required by law.
10. Changes and contact
We may update this policy as the Service changes. We will post the updated policy here and change the date above. If a change requires direct notice under applicable law, we will provide that notice.
Privacy contact: JimmyQrg, ikunbeautiful@gmail.com.