Privacy Policy
This policy explains how Techrewa, operated by Yash Retail and Services Private Limited, handles information in this early-access workspace.
Information you provide
When you create an account, we collect your name, email address and a securely derived password record. Project information can include prompts, titles, scene plans and metadata. Contact enquiries include the details you submit and your consent to be contacted. Please avoid uploading sensitive personal information unless a separate agreed service requires it.
Private recordings and voice permission
Voice Studio stores the original PCM WAV recording you choose to upload, together with its filename, size, duration, audio format, checksum and dates. It does not record your microphone. A voice profile records its name, whether the voice is your own or used with permission, your permission statement, and consent or revocation dates. When an available speech or cloning service needs the reference, a time-limited delivery link allows that provider to retrieve the approved recording. Limited cloning records also retain request status and provider references for reconciliation. Uploading a voice does not authorize model training.
Removing audio and revoking permission
You can delete an audio reference or revoke a voice profile in Voice Studio. Revocation blocks new TechRewa reference use and invalidates its delivery links. Deleting the recording also revokes dependent active profiles and removes the local audio file when deletion completes. Consent, request and deletion history remains to enforce withdrawn permission and support review. These actions cannot retract a file already obtained by a provider, an existing provider voice object or media already generated. Contact us for review of a provider-side deletion request; no automatic provider deletion is promised. Audio references do not use the seven-day saved-output expiry described below.
Private saved outputs
After a supported generation completes, TechRewa can save a private copy of its output, either from the completion workflow or your explicit Save in TechRewa request. This does not generate new content. A successfully copied file is available for seven days from the time the copy becomes ready, subject to the storage limits shown in Saved outputs. Download important work before the displayed expiry. An expired or deleted copy is no longer available through the workspace; a cleanup process removes the local file. This does not delete the original provider output or the job record. We retain associated status, size, type, checksum, expiry and storage-action history; protected backups have a separate retention process. Source-provider links can expire before copying succeeds, so this is not permanent archival storage.
Information stored on your device
The workspace stores your interface language and device drafts in browser local storage. Signing in uses a session cookie for authentication. Temporary checkout references and an opaque attempt identifier may be kept in browser session storage to retry an interrupted payment safely; this does not store card details or provider secrets. Local drafts remain on that browser until you delete them or clear site data. Export important drafts before changing devices.
How we use information
We use account information to provide workspace access; project data to save and retrieve your work; and enquiry information to respond to your request. Operational logs may be used for reliability, rate limiting and security. We do not sell your personal information.
Optional quality feedback
You can save private ratings and correction notes for your completed generations. These records help you review your own work. A separate workspace choice and a separate choice for each job can record permission for structured aggregate workflow evaluation; this release does not export a shared training dataset. Private notes, prompts and media are not included in that choice. You can withdraw shared eligibility in Quality & preferences and delete individual feedback records. Deletion removes active ratings and notes while a minimal deletion marker and consent history remain to prevent unintended reuse; protected backups follow the existing retention process. Model training is disabled: generation, uploads, feedback and purchases do not automatically authorize training.
Operational usage and learning summaries
TechRewa records daily counts of successful sign-ins (including the first signed-in session at registration), saved projects and requested generations to operate the service and show usage reports. These first-party counters contain an internal account identifier, UTC day, event category and count. They do not contain your IP address, browser fingerprint, prompt, media, session token or other-site browsing history. Active operational counters are retained for up to90 UTC calendar days and are pruned at startup and daily; protected backups follow the documented backup lifecycle. Counts are not public video views or advertising conversions. Private quality feedback stays private. Structured quality ratings enter operator model/language summaries only when both your workspace choice and the individual output permit it; small groups and rating subsets are suppressed below five distinct accounts. Withdrawal removes eligibility from subsequent summaries. Raw correction notes, prompts and media are not exposed through these shared summaries. This does not enable model training.
Account support information
Authorized support operators can review your account identity and operational records to help with access, credit expiry, orders and service issues. The customer overview includes credit totals, project titles and dates, generation model and status, order and allowance information, and feedback counts. That overview does not expose raw generation prompts, output media, private correction notes, passwords or provider secrets. These support records do not automatically authorize model training.
In-app reminders and their activity
Your private inbox can show informational reminders based on account age, saved-work activity, purchased-credit expiry or production payment status. We store the reminder, its eligibility reason, delivery and expiry, and your reminder preference. When a card is at least half visible in an active browser tab, or when you click or dismiss it, the inbox can record the reminder identifier, event type and time. Each event type is recorded once per reminder; these records are linked to your account through that reminder. They are workspace actions, not sales or evidence of advertising performance. Turning off reminders in your inbox hides the messages and stops later delivery; it does not erase existing delivery or event history. This reminder system does not send email or WhatsApp messages, award credits or make purchases.
Partner and referral records
If you apply to a referral, affiliate or solution-partner program, we store the information you submit, review decisions and your program status. A referral is attached only when the referred customer explicitly submits a code and agrees to attribution. We do not use hidden affiliate cookies or browser fingerprinting. Qualifying production payments, attribution terms, commission adjustments and separately recorded external payouts form an auditable financial record; recording a payout does not transfer money. Partner users see their own records. Authorized operators review applications and financial evidence. Do not submit another person’s private data without permission. Financial records may need longer retention than operational counters; contact support for access or correction.
Generation and connected services
The model catalog distinguishes available services from routes awaiting activation. When you submit a request through an active model or connection, the information needed for that request may be processed by the relevant service provider. This can include prompts, selected images, recordings or other references that you explicitly provide. Review the selected capability, cost and relevant usage or data-handling terms before submitting. A model listing or saved API key alone does not mean paid generation is available. Do not submit confidential material without understanding the selected service.
Retention and deletion
Device drafts can be deleted in My Projects or browser storage settings. Voice references and saved outputs have the controls and limits described above. Account, enquiry, voice-permission, reminder, job and financial history is retained as needed to operate the service, enforce withdrawn permission, resolve support requests and meet applicable requirements. Deleting a working record or file does not instantly remove it from protected backups. Contact us to request access, correction or deletion; some records may need to be retained for legal or security reasons.
Your requests and policy changes
Submit privacy questions or requests through the contact form using the email associated with your account. We may verify account ownership before acting. Changes to this policy will be posted here with an updated date.
Contact
Yash Retail and Services Private Limited
Plot No. 240, Royal Bhawani Enclave, Sohna Road, Gurugram, Haryana 122102, India.
CIN: U72900HR2020PTC086634 · GSTIN: 06AABCY2351G1ZJ