Sign In
Skip to content
← Back to the workspace

Vikas Editor Privacy & Cookie Information

How Vikas Editor handles accounts, prompts, reference media, generation, payments and optional analytics.

Last updated: 2026-10-25

VikasEditor.io is operated by John Yan, based in Hong Kong. Contact support@vikaseditor.io for service or privacy questions.

Last updated: October 25, 2026.

Accounts and sessions

Google sign-in supplies your account identifier, name, email and profile image. We store account and session records in Cloudflare D1. Session records may include an IP address and browser information for security. We do not request Gmail or Google Drive access. Necessary cookies maintain and protect your session.

Prompts, reference media and generation

A submitted generation request sends your prompt, selected settings and any reference media to our server and the model provider through KIE. Reference uploads and generated outputs use Cloudflare R2 storage; task status, media references and credit accounting are stored in D1 so you can view results and history. Only upload material you are permitted to use. Do not include sensitive personal information. Providers process requests under their own terms; we do not promise a fixed deletion period, storage country or that all providers exclude inputs from model training.

Private visibility controls whether a result is offered for public display within our service. It does not mean the processing providers cannot access the input or that a copied media URL is protected by your login. Keep media links private if the content is not intended for sharing.

Payments and credits

Stripe hosts checkout and processes payment information. We retain customer, order, subscription, invoice and transaction identifiers and credit-ledger records needed to deliver purchases and resolve billing issues. Do not send card details to support. Sandbox purchases on restricted test sites are isolated from production purchases.

Website requests

Cloudflare hosts and delivers the website. Technical requests can include IP address, browser details, requested URL and request time. Logs help operate the service, investigate failures and prevent abuse. Retention varies with provider and operational settings.

Optional analytics

With your permission, Plausible at plausible.online measures visits to public pages and Microsoft Clarity records masked interactions. We exclude test origins, account/billing/history/generator routes and query-bearing pages from these projects. Homepage form text, account details and images/videos are masked for Clarity. We send public page paths rather than prompts, uploaded media links or payment identifiers to Plausible. Google Search Console reports search visibility and verifies our domain; it is not a session recording script.

Optional analytics starts only after you select Allow analytics. You can decline or withdraw using Analytics settings in the footer. Browser storage and a preference cookie remember this decision; withdrawal reloads the page to stop loaded recording scripts. Sign-in and security cookies are separate from optional analytics. No advertising analytics is enabled by this integration.

Support, disclosures and requests

Support email is handled through Migadu. Send only information needed to explain the issue, not credentials or sensitive photographs. Providers may process information outside your country. We may disclose information to comply with legal obligations or protect rights and security.

Contact us to request access, correction or deletion of information we hold. We may need enough information to identify the relevant records, and some billing or security records may need to be retained. We update this notice when relevant processing changes.

About · Terms and credit policy

Private generation requires paid access. Review the public-visibility setting before submitting a task.