Privacy notice

Rewalto is a product of Avuvo AI Pvt Ltd, a company registered in India at 309, Tower A of SAS Tower, Medicity, Gurugram, Haryana - 122001 (CIN U47411HR2025PTC128454). For the purposes of India’s Digital Personal Data Protection Act, the company is the data fiduciary for everything described below.

Where Rewalto processes data on a client’s behalf under a signed engagement, analytics connectors, for instance, it acts as a data processor for that client instead, and the client’s own notice governs. That relationship is set out in the engagement, not here.

From this website: page views and clicks, through Google Analytics 4. It records which pages you open, which buttons you press and which of our two doors you enter, never your name, email, phone number or the domain you search on /domain. There is no advertising pixel, no ad-targeting signal (Google Signals is switched off for this property), and no tag manager beyond GA4 itself.

When you use the enquiry form on /talk we store your name and phone number, the brand, its website, its category and your work email, because those are what a data sample or a call needs. Your role, what you feel you lose ground to, and a list of SKUs are optional and stored only if you type them.

If you sign up for the newsletter in the footer, we store your email, whether you have confirmed it, and whether you have unsubscribed. Nothing else is asked for. A confirmed address is kept, with no automatic deletion date, until you unsubscribe or ask us to delete it, §8 states the identical retention shape for a demo sign-in, and this is the same shape applied here.

To stop the form being abused we keep a submission count keyed to a salted hash of the calling IP address, never the address itself. The schema comment says why in one line: an abuse counter must not become a visitor log. Those counters are deleted after two days.

If you hold a login to a Rewalto console, your authentication identity is held by Clerk (§5) and the console records which account took which consequential action, because an audit trail with no actor is not an audit trail.

When you accept data and report use terms, we keep the policy version and its exact wording, your account, workspace and role, and the date and time of acceptance. For a purchase, the record is also linked to that purchase request. This records what you agreed to and is separate from any choice about marketing messages.

How we measure getting started.

When you use Rewalto, our own servers note four moments for your account: when you first sign in, when you first search, when we first show you data, and when you first make a purchase. We record only the date and time of each against your account, not your IP address, device, browser, searches or the pages you visit. We use these times only to see how long new customers take to get useful data and to shorten it, and we keep them while your account exists. This is first-party only: no third-party tracker, analytics or advertising service receives it.

To answer you, to run the engagement you asked for, to stop the form being abused, and to measure and shorten the time it takes new customers to get useful data. We do not profile you, we do not build a marketing segment, and we do not enrich what you gave us against a third party.

[LAWFUL BASIS, COUNSEL] The characterisation of each purpose under DPDP’s consent and legitimate-use provisions is the one part of this notice that is a legal opinion rather than a description of the system, and it is deliberately not drafted here.

Rewalto measures public retail and search surfaces. We crawl what is publicly reachable. Nothing behind a login. We do not create accounts, we do not use a device farm, we do not spoof geolocation, and we do not mystery-shop competitors covertly.

When we test a client’s own channels we test only channels that client has contracted us to test. Personal data does not normally appear in that material; where a public page happens to contain some, it is held as part of the timestamped artefact and is subject to the same deletion route as anything else here.

We do not sell your data, we do not share it for anyone else’s marketing, and we do not enrich it. It is processed by six service providers, each doing one job:

• Supabase : the database the enquiry record is stored in.
• Vercel : hosting and delivery of this website.
• Resend : sending the email that replies to you.
• Cal.com : the scheduling embed, if you book a call.
• Clerk : authentication, for console accounts only.
• Google Analytics : page views, clicks and the two doors you choose between; Google Signals off, no advertising use.

None of them is an enrichment or data-broking provider, and that is a standing constraint rather than a current fact: adding one would contradict the sentence above and both would have to change together.

We will disclose data where the law requires it. If that happens and we are permitted to tell you, we will.

Enquiry records are stored in Supabase’s Postgres on AWS in Mumbai (ap-south-1), in a database schema that is deliberately fenced from the measurement data: nothing in the observation store or the evidence archive is permitted to join to it.

An enquiry is deleted 180 days after you send it. That is not a policy statement, the expiry is stamped onto the row when it is written and a scheduled job deletes on it. Stamping at write rather than computing at deletion is deliberate: a later change to the period applies to enquiries received after it, never retroactively to ones already held.

Abuse counters are deleted after two days. Evidence artefacts from client engagements carry their own retention, set in the engagement.

Under DPDP you may ask us for the personal data we hold about you, ask us to correct or complete it, ask us to erase it, and nominate someone to exercise these rights if you cannot. You may withdraw consent at any time, and doing so is meant to be as easy as giving it.

In practice: email the address in §11 and say what you want. We will not ask you to prove a legitimate interest and we will not route you through a form. If your enquiry is more than 180 days old there will be nothing to return, because it has already been deleted.

[PLANNED, NOT YET LIVE] Rewalto plans a self-serve demo dashboard, reachable without an appointment, so a visitor can see the product on mock data before talking to anyone. This section describes how it will handle your email once it exists; it does not exist on the site today.

Signing in is handled by Clerk (§5), today with your Google account; we never see your Google password. Any sign-in or verification email comes from Clerk, not from us, and it is not a marketing message.

Service terms and marketing choices are separate. Accepting the data-use terms does not sign you up for marketing messages. An optional newsletter or product-update choice requires a separate opt-in.

Two separate boxes, both starting un-ticked. Accepting the terms of use and this notice is required, sign-in is blocked until it is ticked, because that is what makes the sign-in itself lawful. A second, separate box, “send me product updates and the newsletter”, is optional, and sign-in works whether or not you tick it. One box does not gate the other: ticking the required box never enrols you in marketing mail, and declining the marketing box never blocks you from the demo.

If you tick the marketing box, your email joins the same newsletter list this site’s footer signup already uses, sent through Resend, the same provider §5 names, with the same confirmation step and one-click unsubscribe that list already has. Unsubscribing stops the mail; it does not remove your demo sign-in itself.

Your demo-signup email is kept, with no automatic deletion date, until you ask us to delete it, the same “retain until asked” shape a login naturally needs, since we cannot let you back in with an email we have already forgotten. Deleting it on request is a right under DPDP and equivalent regimes (like GDPR), not merely a courtesy, and asking is the same route as §7 above: email the address in §11 and say what you want deleted.

This section states the SHAPE of a client’s own data retention; the signed engagement remains the governing document, per §1 above.

Data collected under an engagement is kept for the life of the relationship, with no automatic expiry timer. This applies to both halves of the product: what Rewalto measures from public retail surfaces (unchanged, and already the case, see /security), and, once a client connects a system of their own, what that connector reads. Historical comparison is the reason, a figure aged out after some fixed period cannot be compared against, and that comparison is a large part of what a client is paying for.

A client can end this at any time, from inside their own account, without needing to ask us to do it for them. [PLANNED, NOT YET LIVE] That self-serve deletion route does not exist in the product yet. Until it does, the same request by email (§11) is honoured by hand.

[WHAT SURVIVES CLOSURE, COUNSEL] What Rewalto is obliged to keep despite a deletion request, billing records, audit logs, anything a statute or an accounting obligation requires, and whether an irreversibly anonymised, aggregated derivative of a closed account’s data may still be retained for cross-brand benchmarking are both open questions for counsel, not decided here. If an anonymised-derivative right is ever granted, it would be disclosed in the signed engagement itself, agreed to knowingly before any data is collected under it, never introduced afterward.

Everything above describes this website, the planned demo, or the shape of a signed engagement’s own retention. A connector is a separate, later decision : a brand’s own team choosing to connect a system like Shopify or Google Analytics inside the product, not something this website does on its own. This section covers that decision.

One connector is built and used today: the source-control connector that opens a pull request against a repository you name. It reads that repository’s contents; it never merges. Nothing else is read through a connector today, a Shopify, Meta Ads, Google Ads, Google Analytics 4 or Google Search Console connector is not yet live, and we took each of those pages down rather than publish a scope for something nobody can yet connect. When one goes live its exact scope, what it can never do, and how to revoke it is published on its own page under /integrations, not invented here a second time.

Retention per connector is not yet a published number. [RETENTION PER CONNECTOR, P7-05] P7-05, the plan that sets a retention clock for every connector’s payload classes, is itself not started. When a connector goes live its retention is published on its own /integrations page and enforced by a job, the same clock-not-intention rule §6 above states for this website’s own data. It is not invented here ahead of that plan existing.

There is no peer benchmark at launch. We took down the page describing it: there was no data behind it, and we only describe what works today. If a pooled benchmark is built later, this section will describe it the same way it would any other opt-in, never a raw figure belonging to another brand, and no pooled figure published, sold or shown to a brand that has not opted in.

Deletion. Revoking a connector in the product stops it reading immediately. Full instructions, what a request removes, what is kept as public record or audit history and why, and how to ask, are on their own page, /data-deletion, published there because at least one platform (Meta) requires a standalone data-deletion URL independent of where else it is written down. This section and that page state the same facts; the page is the canonical one.

If you are unhappy with how we have handled your data, the grievance officer is Varun Mahajan (vm@rewalto.com). DPDP gives you the right to escalate to the Data Protection Board of India if we do not resolve it.

For a security issue rather than a privacy one, the route is security@rewalto.com : the same one /security publishes.

This notice is dated at the top and every previous version is in the repository’s history, so a change is visible rather than announced. If a change materially affects what we do with data you have already given us, we will email you rather than rely on you re-reading this page.