01Information we handle
When you create an account, Firebase Authentication handles your phone number, verification details, account identifier, and any name you provide. If you link a recovery email, it also handles that email address and its verification status.
If you join the early-access list, we collect your email address and signup time to manage your request and send relevant updates. Our hosting and authentication providers may also process technical information such as IP addresses, browser details, and security logs to deliver and protect the service.
02Support tickets and chat
When you contact support, we store your name, email, topic, and conversation in Firebase so our authorised team can answer and manage your ticket. An automated support bot uses the message text to provide general help; it does not access your account or payment records. A temporary token in this browser tab allows you to follow replies. Avoid sending passwords, verification codes, or payment card details. You may request deletion of support records by emailing genie@ruksar.in.
03Public library and safety screening
When you submit a creation to the public library, Ruksar sends the optimized image and any animation you submit to Sightengine to check for nudity, sexual content, violence, and gore before publication. This screening also applies to images exported from the editor when you choose to publish them. Editing videos locally does not submit them for screening.
Accepted creations, your displayed creator name, title, and description are stored in Firebase and made public. Safety decisions, confidence scores, the policy version, and the checked image identifier are stored privately to support moderation. Rejected submissions are not stored as public creations. Contact genie@ruksar.in to report content or request review of a rejected image.
04AI conversations
When you use signed-in AI chat, conversation text, replies, feedback, and attachment names and metadata are saved privately in Firebase under your account so you can continue on another computer. Existing browser chats are uploaded when account sync connects. A browser cache supports temporary connection failures. Uploaded attachment bytes, generated image files, and temporary media previews are not included in chat-history sync.
Deleting a chat removes its cloud conversation content when sync succeeds. A deletion marker prevents an older browser cache from restoring it. Offline changes sync when you reconnect. Simultaneous edits may be preserved as separate chats. Your selected files are sent to the self-hosted AI when needed to answer your request. For web searches, only the search query is sent to DuckDuckGo. You may request account data deletion by contacting genie@ruksar.in.
05Videos and saved projects
Video Framer processes selected videos locally in your browser rather than uploading them to Ruksar for editing. Project media and settings can be saved in your browser’s IndexedDB and local storage. Projects are specific to this browser and device, and do not sync with your account.
If you load a video from a URL, your browser contacts that external host. That host may receive your IP address and request information under its own privacy practices.
06How information is used
We use account information to verify your identity, sign you in, support recovery, and determine authorised feature access. Early-access information is used to manage the signup list and send confirmation or launch communications. Technical information helps operate the website and prevent abuse. On phone sign-in and signup forms and the pricing page, we use approximate IP-based country information to suggest a calling code or billing currency. This uses country information supplied by our hosting network, with your browser region as a fallback. You can change the suggested country.
07Cookies and browser storage
Ruksar uses a session cookie to keep you signed in. Authentication may use verification and anti-abuse mechanisms provided by Firebase. Local storage remembers your theme, manually selected phone and pricing countries, and project settings; IndexedDB stores saved project media.
You can remove cookies and local data through your browser settings. Removing session cookies signs you out. Removing project storage can permanently erase saved projects, so export or back up your work first.
08Service providers
We use Google Firebase for authentication, including phone verification and recovery email. Where configured, Resend sends early-access confirmation emails. Infrastructure providers process information needed to deliver the website. These providers may process data outside your country under their applicable terms and safeguards.
We do not sell your account details or creative files. We may disclose information where required by law or necessary to protect users and the service.
09Retention and security
Account information is retained to maintain your account and meet applicable security or legal obligations. Early-access information is retained while managing the list. Retention may depend on the purpose and provider involved; there is no single fixed period for all records.
We use safeguards such as secure session cookies in production and verification checks. No storage or transmission system can guarantee complete security. Local projects remain on your device until deleted or cleared by you or your browser.
10Your choices and requests
You can manage saved projects in the tool, clear browser data, and choose whether to provide a recovery email or join the early-access list. Depending on applicable law, you may have rights to request access, correction, deletion, or withdraw consent for relevant processing. Withdrawal does not affect processing already lawfully carried out.
To request account deletion, early-access removal, or exercise applicable privacy rights, email genie@ruksar.in. We may need to verify your identity before acting on a request. Some information may need to be retained to meet legal or security obligations.
11Audience measurement
We automatically count public page views and tool actions on our own server. These counts include a public page path or an action name and plan category, plus a random identifier for each action to prevent duplicate counting. These counters do not identify a visitor or session. Uploaded videos, filenames, account identifiers, query strings and session recordings are excluded. Server infrastructure separately maintains ordinary access logs.
Where optional analytics is enabled, we ask for a new choice before Google Analytics or PostHog measures public-page visits and tool actions using browser identifiers. You may decline or withdraw through Analytics preferences. Private pages, private prompts, generated content and payment details are excluded from these analytics events. Browser do-not-track and global privacy signals disable optional collection.
Optional analytics choices expire after 90 days. Provider data retention depends on the analytics account settings. Withdrawing stops future optional collection and removes accessible local analytics identifiers; it does not automatically erase previously collected provider data. Contact us using the privacy-request details below for deletion requests. Our own stored daily counters have a configurable retention period, normally 90 days, and duplicate receipts are short-lived.
12Policy updates
We will update this notice when our data practices change, including before introducing payments or new data collection. The date above shows the latest revision. Material changes will be communicated where required.