Privacy Policy

• We collect what we need to open and run your account, bill you, keep it secure and meet the law. We do not sell personal data and we do not share it with advertisers.
• Your shoppers' data belongs to your store; we hold it for you, on your instructions, and use it for our own purposes only in the narrow cases in section 5.
• You can see, correct and delete your data, withdraw any consent you gave, nominate someone to act for you, and complain to us and then to the Data Protection Board of India. Section 10 says how.
• Some of the companies that help us run the service are outside India. Section 6 lists them.
• We keep data for the periods in section 7 and then delete it, unless the law makes us keep it longer.

This policy is issued by TECHNOSTAT LABS LLP (LLPIN ADC-0087), a limited liability partnership registered in India, registered office at No. 347, 41st Cross, 8th Block, Jayanagar, B Sk II Stage, Jayanagar, Bangalore South, Bangalore – 560070, Karnataka, India, trading as RaxCube ("we", "us"). We run the RaxCube platform, the raxcube.com website, the Studio, and the stores at raxcube.shop. This policy covers RaxCube wherever we run it, including our test and review environment at raxcube.net and raxcube.store (for example api.raxcube.net and raxcube-demo.raxcube.store), which is the same service operated by the same operator and is not open to the public for trading.

It applies to:

• merchants: people and businesses who sign up for a store or a Studio account, and the staff they give access to;
• visitors to raxcube.com and the Studio website;
• anyone who writes to us: support, sales, legal, or a complaint.

For this data we are the Data Fiduciary under the Digital Personal Data Protection Act 2023: we decide what is collected and why.

If you are a shopper on a store built with RaxCube, the store's own privacy notice applies to you, linked from that store's footer. The merchant who runs the store decides what is collected and why; we process it on their behalf as their Data Processor, under Schedule 1 of our Merchant Terms. If you write to us about a store, we pass your message to the merchant unless the law requires us to act ourselves. Section 5 explains the few things we do with shoppers' data for our own reasons.

This policy does not cover our own partners, employees and contractors, who receive a separate notice.

Indian law lets us process personal data either with your consent or for a "legitimate use", which includes data you give us voluntarily for a purpose you can see, and processing the law requires. Each item below says which applies. Where the basis is consent, you can withdraw it (section 10) and we tell you what happens if you do.

3.1 When you sign up for a store or the Studio. Your name and email address; your store or business name, legal name, business address, GSTIN and any seller identification number you give us; the customer-care phone number you publish for your store; the pickup phone number you give for couriers, which goes to the courier with your pickup address and may receive its one-time codes; and, if you sign in with Google, the Google account you use (section 4). Where the signup asks for a mobile number, we verify it by a one-time code sent by text message and use it only to help you get back into your account and to tell you if the number on it changes; never to sign you in, and never for marketing. Purpose: to open and run your account, invoice you, send notices under the Terms, publish the seller details the law requires on your store, and identify you when you contact us. Basis: you give these voluntarily for that purpose; we cannot open an account without them.

3.2 When your store is checked against the government register. A store in India opens only once its GSTIN or, without one, its company's CIN, its LLP's LLPIN or its Udyam Registration Number has been checked: a GSTIN, CIN or Udyam number is looked up in the government register through our verification provider, Cashfree Payments, and an LLPIN is checked by our team by hand against the register, with a note of how. You tick a box agreeing to the look-up first, and we record that you did, when, and which wording you were shown. From the register's answer we keep the legal and trade name, the type of organisation, the registration's status and dates, the principal address, the kind of GST registration and, for Udyam, the enterprise size, which are the details your invoices and your store's legal page print, with when we asked, who asked, the provider's reference, and a fingerprint (a one-way hash) of the answer so that it can be proved without being kept. We do not keep the phone number, email address, social category or certificate link that a register returns, nor the answer itself. We ask the register again ourselves, weekly for a GSTIN or CIN and monthly for a Udyam number, and tell you if anything has changed. Your store's legal name and registered address are taken from what the register holds. Basis: voluntary provision for the purpose of opening the store, and our legal duty to display accurate seller details.

3.3 When you confirm a number is yours. A register confirms that a business exists, not that the person asking is that business, so before a number becomes your store's we confirm it is yours. A sole proprietor, or a director of a company, does this through DigiLocker, the Government of India's document service, reached through Cashfree Payments: you sign in on DigiLocker's own page with your Aadhaar number or mobile and a one-time code, which we never see, and share your PAN record; DigiLocker also shares your name, date of birth and gender. We compare your PAN with the one your GSTIN was issued on, or ask the Udyam register whether your number was made on it, or for a company compare a director's name and date of birth with the company's record at the Ministry of Corporate Affairs. We keep only your PAN partly hidden, whether it matched, when, the matching director identification number, and your consent with its wording version and a fingerprint of the exact text. We do not keep your name, date of birth, gender or the document; a director's details are held only as one-way fingerprints for the length of the check. Otherwise we email a code to the address the register holds for your business, use that address only to send the code, and do not keep it. Basis: consent, given on DigiLocker's page and recorded by us, for the single purpose of confirming ownership.

3.4 When you sign in. If you choose a password, we keep only a one-way hash of it, which nobody here can turn back into the password, and the secret that links your authenticator app to your account, kept encrypted. We keep a record of password resets and of requests to remove an authenticator, with the date and time and the address they came from, because those records are how we notice, and can later show, that somebody else tried to get into your account. There are no backup codes; a request to remove a lost authenticator is announced to every owner of the store and carried out only after 72 hours. We also keep a record of every sign-in event on your admin account, successful or refused: the time, what was attempted (a Google sign-in, a password, a code, an authenticator step, a password or authenticator reset, a reused session, a sign-out), the outcome and a reason code, your IP address and browser, and a one-way keyed hash of your email address rather than the address itself. The IP address is kept in full for 90 days and then shortened to its network prefix, and the records are kept for 24 months, with a copy in write-once storage in India so that they cannot be altered. The owner of a store can see the sign-in history of the store's admin accounts, with the time, the device and a city estimated from the network address, which can be wrong. Basis: voluntary provision for the purpose of securing your account, and our legal duty to keep security logs; the password and authenticator secret are sensitive personal data under the SPDI Rules and are handled as section 8 describes.

3.5 When you accept the Terms. The version you accepted, the date and time, your IP address and browser. Purpose: to prove what was agreed. Basis: voluntary provision; retained for the life of the account plus three years.

3.6 When you add a payment method or pay us. Your card or bank details go directly to our payment processor, Razorpay; we never see or store a card number, and Razorpay's own privacy policy applies to what it holds. The ₹1 signup check is paid by card or UPI. Razorpay gives us a fingerprint of the card, or we take the UPI ID; we keep only a one-way keyed hash of either, made with a secret held outside the database, and a record of which signups used the same instrument, so that our team can review repeated free trials and misuse. It does not block a signup on its own. Autopay mandates and refunds are handled by Razorpay against your mandate; to register a mandate the gateway needs your mobile number, which we collect for that purpose and pass to it, and we keep the record of your agreement to automatic payments with its wording, version, amount and time. We keep the invoices, credit notes and payment references the law requires. Basis: voluntary provision for the purpose of paying us, and, for invoices and tax records, a legal obligation. The instrument hash is deleted three years after signup. Signup is also rate-limited per email address and account (codes, guesses, payment attempts and domain searches per hour or day), which is a security measure and keeps no more than counts.

3.7 While you use the platform. Activity and audit logs: which account did what in the admin, and when; which features you use and how much; and the operational telemetry described next. Purpose: to run the service, keep it secure, investigate problems, bill credits, apply the Terms, and meet our legal duties as an intermediary. Basis: voluntary use of the service for these purposes, and legal obligation for the security logs the law requires us to keep.

3.8 Operational telemetry. Our servers send Microsoft Azure Application Insights, in its Central India region, the timings of requests and of calls to other services, the names of those calls, the text of database commands with placeholders in place of every value, and warnings, errors and exceptions. The pages of your admin, our platform desk and the Studio also report page views, route changes and browser errors; the storefront pages your shoppers see report nothing and load nothing for this. What is sent carries your store's internal identifier, never its name or address, and no user or shopper identifier; it sets no cookie and uses no browser storage. Before anything leaves our servers, web addresses lose their query strings and fragments, email addresses are masked, phone numbers, tokens and keys found in text are replaced, and request and response bodies, headers, database values, Studio prompts, briefs and media, and the recipients and subjects of our emails are never included. IP addresses are masked by the service's default, except that a refused sign-in to the Studio's operator desk records the caller's IP address and an error code in that telemetry as a security record. All of it is deleted after 30 days. Basis: legitimate use for the security and operation of the service.

3.9 When you upload pictures or video. The file itself; the result of the automated safety check every upload passes through (section 6 says who runs it); and, if a file is refused, a record of the refusal: the category and score the check reported, the account and staff account that uploaded it, and the time. A refused file is destroyed at the moment of refusal; we keep no copy of it, blurred or otherwise, only what the check said about it. Purpose: to keep unlawful and unsafe material off the platform and to be able to explain and review our decisions. Basis: legal obligation as an intermediary and voluntary use of the service.

3.10 When you tell us whether AI made a file. We record your answer against the file, with the email address of the account that answered, the date and time, which version of the question was asked, and whether it was answered at upload or later from your Gallery, so that the label on your store can be traced to who declared it. Basis: legal obligation, under the rules on synthetically generated content.

3.11 When you use the Studio, the assistant or other AI features. The prompts you give, the images you upload, and what is generated. These are sent to the AI model providers listed in section 6 to generate the output, and to safety checks before delivery. Before anything you type into the help box or an assistant is sent to a model, you are shown a notice naming the models and asking you to keep passwords, card numbers and customers' details out of it, and your agreement is recorded with its wording version. We do not keep what you typed or the prompt built from it: on the platform they exist only while a job runs and are blanked when it finishes, and the Studio keeps no copy of the output once it is delivered to your gallery. The Studio service that runs a job keeps the prompt and brief, and a storyboard with its brief, in memory only, for 24 hours after the job last changed, so that a failed job can be retried; it holds generated files for 30 minutes unless you save them to your gallery, and writes none of this to disk. What we keep is a record of each job: when it ran, what it cost, whether it was refused and, if so, the safety category. Drafts the assistant writes for you, such as product descriptions, are kept in your admin for six months unless you delete them sooner. Your conversations with the setup assistant are kept for 30 days, your conversations with the store assistant for 90 days, and your help-chat history for 90 days. Purpose: to provide the feature, check output against our safety rules, bill credits, and investigate misuse. Basis: voluntary use of the feature. If you upload a photograph of a person, you are responsible for having their agreement (Terms, clause 8.2).

3.12 When we check what your store shows the public. Our automated checks read your published listings, pages, images and store name (Terms, clause 15). Where a check raises something serious we may keep a capture of the page as it looked at that moment, as the record of that review. Purpose: to meet our duties as an intermediary and to be able to explain a decision afterwards. Basis: legal obligation.

3.13 When you connect Google, Instagram, Facebook or WhatsApp. Section 4.

3.14 When we register a domain for you. The owner's name as it appears on their government identity document, which the registrar may verify, with their address, email and phone, go to the registrar and registry as the registrant's details, because the domain is registered in your name, and registries require them; we do not pre-fill the name from your Google account. For .in domains the registry may verify them. The authorisation code you give us for a transfer is passed to the registrar and then deleted. Basis: voluntary provision for that purpose; the registrar's and registry's own policies then apply to what they hold.

3.15 When you write to us. Your message, the name and email address you wrote from, its subject, and the record of how we answered, kept as a support record so that the next person who answers you knows what was said. A picture you attach to an email is kept with that record for our support staff to see, re-drawn as a fresh image so that its hidden details, such as a location, are not kept; other kinds of file are not taken from the email and stay only in our mailbox. Pictures are deleted 90 days after they arrive, or, where they belong to a grievance or a data request that is still open, when that matter closes if that is later. A draft of our reply may be prepared with the help of the AI model provider named for it in section 6, which receives your message for that purpose; a person on our team reads, edits and approves every reply before it is sent, and an unsent draft is deleted when your matter closes. One reply is automatic: where your message is about not being able to sign in, we may answer at once with standard instructions that are the same for everyone and contain no link and nothing about your account; a person handles anything further. If your message reports a fault in the platform, a person on our team may file it with our bug tracker (GitHub, section 6) once they have approved it: the summary, and the words of your report, go with email addresses and long numbers removed; the record of which fault your message reported is kept with your support record. Purpose: to answer you, to keep a record of what was agreed, to fix faults, and to improve support. Basis: voluntary provision for that purpose.

3.15a When you write to us from the enquiry form on raxcube.com. Your email address (which we do not verify), a phone number if you want a call, the country you choose (pre-filled from the country our network reports for your connection, which we also keep; we keep no IP address), the category or product you ask us to add, your question, anything else you choose to tell us, and the page you wrote from. Purpose: to reply to you, and to count which countries and products people ask us about. Your question, with email addresses and numbers removed, is sorted automatically by category and intent by TypeSafe, and our staff may have Anthropic's model summarise recent questions in the same stripped form; neither receives your email address or phone number. Enquiries are deleted 12 months after they last changed, and the phone number 90 days after the enquiry is settled. Basis: voluntary provision for that purpose.

3.16 When you visit raxcube.com or the Studio site. raxcube.com counts visits without cookies and without any third-party analytics: your browser keeps a random id for the length of your visit, which is hashed with the day and the site before it reaches us, so we can count visits and pages but cannot recognise you across days. The Studio site does not count visits at all. The network that carries our traffic (Cloudflare, section 6) sees your IP address in order to deliver the page and protect the site, and tells us your country. Where it is switched on, the signup page, the sign-in help form and the enquiry form are guarded by Cloudflare Turnstile, which tells us whether a person or a script is sending the form; your browser's answer to its challenge and your IP address go to Cloudflare, and we keep only the result. We do not use advertising or tracking cookies on our own sites. Basis: legitimate use for the security and operation of the site.

3.17 Marketing. We do not send marketing email, SMS or calls to merchants or visitors. Emails about your account, such as invoices, renewal reminders, reminders about setup steps still to do while your store is being set up, security alerts and notices under the Terms, are not marketing, carry no unsubscribe link, and keep coming while you have an account. Our support desk can see a store's setup progress (which steps are done, put off or waiting, and when the owners were last reminded) to help you; it cannot change your choices. If we ever start product news by email, it will be opt-in, separate from everything else, with a link to stop it in every message, and saying no will never limit your account. We name you as a customer only with your consent (Terms, clause 18.2).

3.18 Your staff. When you give a member of staff access to your admin, we hold their name, email address, the record of their sign-in events described in section 3.4, the records of their password resets and authenticator removals, and their activity on your behalf, under Schedule 1 of the Terms: you are the Data Fiduciary for your staff and we are your processor. We use those security records for our own security purposes in the same way as yours (sections 3.4 and 3.7).

3.19 What we do not collect. Your password itself (only the one-way hash described above). Card numbers. Your Aadhaar number, ever. Your full PAN: we keep it partly hidden after the ownership check in 3.3, and otherwise only as part of a PAN-based GSTIN you give us for invoicing. Precise location. Anything about your shoppers for our own purposes beyond section 5.

3.20 Keeping data accurate. Most of what we hold about you can be corrected by you in your admin, and the law expects you to keep it accurate where it is used to make decisions about you or to invoice you. Tell us if something else is wrong (section 10).

Google sign-in. If you sign in with Google, Google tells us your email address, that Google has checked it, and the name on your Google account. We use them only to sign you in and to match you to your store or to an invitation from its owner. We do not ask Google for your contacts, your files or anything else, and we do not post anything to Google. You can remove our access at any time from your Google Account (Security → Your connections to third-party apps and services); after that you cannot sign in with Google, but you can still sign in with your email address and a password if you set one.

Instagram, Facebook Pages and WhatsApp. On plans that include social features you can connect your store's Instagram professional account and your Facebook Page, and, where we have switched it on for your store, your WhatsApp Business account. Connecting takes you to Facebook's own sign-in dialog at facebook.com, where you choose what to allow. Facebook and Instagram are not ways to sign in to RaxCube; the dialog is used only to connect these accounts.

What we ask Meta for. Only what each connection needs:

• Instagram: to see the Pages you manage (pages_show_list, pages_read_engagement, business_management), the Instagram account linked to one (instagram_basic), to publish posts to it (instagram_content_publish) and to manage the posts we published (instagram_manage_contents);
• a Facebook Page: to see your Pages (pages_show_list, pages_read_engagement, business_management) and to post to one (pages_manage_posts);
• advertising: to read and manage campaigns in your own ad account (ads_read, ads_management);
• WhatsApp: to manage your WhatsApp Business account, send and receive its messages, and manage its catalogue (whatsapp_business_management, whatsapp_business_messaging, catalog_management, business_management);
• catalogues: to manage a catalogue in your own Meta business (catalog_management);
• advertising measurement: where your plan includes it and you turn it on, to send your shoppers' consented events to your own Meta dataset through Meta's Conversions API (ads_management and the dataset's own access), using a business system-user key you grant through Facebook Login for Business.

What we keep from Meta. The name and identifier of each connected account, Page, ad account, catalogue, advertising dataset and WhatsApp number, and the identifiers of the audiences created in your ad account; the keys Meta gives us to act for your store, including the long-lived user key used for advertising, stored encrypted and never shown on a screen, with the date they expire so that your admin can remind you to reconnect 14 days before; our record of each post composed in your admin, with when and where it was published and a link to open it on the network, because it is the only account of what went out in your name; the campaigns you create through us, with their budget, dates and audience settings; the identifiers of your catalogues and of the products synced to them; and, where WhatsApp is connected, the messages your customers send to your WhatsApp number, with the sender's number and WhatsApp name, so that you can answer them and turn a basket they send into an order. Meta fetches the pictures and videos you post from public addresses on our servers, and once a day we ask Meta whether each post still exists. We use the keys only when you, or a schedule you set, ask us to post, send, sync or advertise, in your name. A campaign is created paused in your own ad account and starts only when you confirm its spend; Meta bills your own card. We manage only campaigns created through RaxCube.

How long. Keys until you disconnect or the account closes. WhatsApp messages 90 days, then deleted. Post records, campaign records and catalogue identifiers while your store is open, then on the schedule in Terms clause 14. If your plan stops including social features, nothing is disconnected or deleted; publishing pauses, your connections and records are kept, and you can still disconnect and delete at any time.

Deleting what Meta gave us. Disconnect an account from Social in your admin, which deletes the key at once; or remove our access at Meta (Business integrations, RaxCube, Remove): Meta tells us at once and we delete our copy of the key then, and if that message does not reach us our daily check finds the removal and deletes it within a day. "Delete my Meta data" in Social deletes the connections and their keys, our record of the posts made through them (with the option of taking those posts down on the networks first) and the WhatsApp messages sent to your connected number; it does not yet remove your catalogue listings, collection sets, catalogue choices, message-template records or the domain tag, which go when your store's data is deleted. Both work while your store is unpaid or closed. If you remove RaxCube under Business integrations in your Facebook settings and then, under Removed, send a data-deletion request, Meta sends us a signed request and we delete every connection made with your Facebook account that we can match to it (a connection made before 28 September 2026 or through Meta's embedded signup may not match, so use the Social page or write to us for those), its keys, the post records and the WhatsApp messages, then show you the outcome on a status page on our servers whose address Meta gives you with a confirmation code; a request that concerns a store under a legal hold waits until the hold lifts, and the page says we are working on it. Our data deletion page, raxcube.com/data-deletion.html, sets this out step by step. Nothing we do deletes anything from your Facebook or Instagram.

For your shoppers' personal data you are the Data Fiduciary and we are your Data Processor. We process it only to run your store, on the instructions in the Terms, your settings and your admin, and we do not use it for our own purposes, with these exceptions, which the law allows or requires and which we tell you about here:

5.1 Safety checks. Photographs shoppers attach to reviews pass through the same automated safety check as your uploads (section 3.9). A photograph the check cannot clear is not published, and we keep the refusal record described there. The text of published reviews is also read by the automated content check that reads your listings (section 3.12); a review the check flags is not removed by the machine, but you are told, and a person on our team decides.

5.2 The complaints system. Our team sees the status of a shopper's complaint (answered or not, and when) to apply the Terms; it reads the content of a complaint only where a court or authority requires it, where you ask us to, where the complaint is about the platform, or to investigate abuse of the complaints system; the actions our team takes on a complaint are recorded with who took them. We keep our own log of complaint numbers, times and statuses, not the content.

5.3 Shoppers' WhatsApp requests. Where a store uses WhatsApp, a shopper's STOP and DELETE MY DATA messages are answered whatever the merchant's plan, and after the store has closed; they never depend on the merchant's subscription.

5.4 Messages from shoppers to us. If a shopper writes to us about your store, we keep their message and our reply as a support record, tell them that you run the store, and, once a person on our team has approved it, forward the message to the email address of your store's owner with the shopper in copy. We do not forward a message that is about RaxCube itself, that the sender marked confidential or asked us not to forward, that contains a card number, or whose sender we could not verify. If you have not replied within three days, we remind you, without the shopper in copy.

5.5 Material involving a child. If an upload from any source is flagged as sexual material involving a child, it is refused and destroyed like any other refused upload, the refusal record is kept, and we report the matter to the authorities as the Protection of Children from Sexual Offences Act requires. We do this because the law requires it.

5.6 Aggregated statistics. We use data in aggregated or anonymised form, from which nobody can be identified, to operate and improve the platform.

5.7 Legal claims and abuse. We may use data we hold to establish, exercise or defend legal claims, and to investigate fraud or abuse of the platform.

5.8 Sign-in and order look-up records. When a shopper signs in to a store, signs out everywhere, or looks up an order without an account (tracking, order details, a cancellation code), we keep a record of the attempt for the store's security and ours: the time, what was attempted, the outcome and a reason code, the order number looked up, the IP address and browser, and one-way keyed hashes of the email address or phone number used, never the address or number itself. The IP address is kept in full for 90 days and then shortened to its network prefix; the records are deleted after 180 days. A shopper's erasure does not remove them inside that period, because they are security records kept under a legal duty.

5.9 Legal holds. Where a court, an authority or a legal notice requires us to keep a store's records, we put the store under a legal hold: nothing of that store's is deleted, by a schedule or by request, until the hold lifts, and a shopper who asks for erasure meanwhile is told that we are required by law to keep the store's records for now. The erasure is carried out when the hold lifts.

5.10 Advertising measurement on a store. Where a merchant turns it on and a shopper has given the separate consent shown on the store, we send that shopper's views, bag additions, checkout starts and purchases, with their hashed email or phone, network address, browser and advertising-link code, from our server to the merchant's own Meta dataset. The merchant may have Meta build audiences in the merchant's own ad account from those events, including people who looked or bought and people who resemble its buyers, and we keep only the identifiers of those audiences. We do this as the merchant's processor and for no purpose of our own: we build no profiles or audiences for ourselves, combine nothing across stores, and send no customer lists. Each event is deleted from our outbox the moment Meta accepts it, and within seven days in any case; daily counts without personal data are kept for 90 days.

We share personal data only with the companies that help us run the service, each bound by a written contract to use it only for that purpose and to protect it at least as well as we do, and with authorities where the law requires. The current list:

We keep this list current here. We tell merchants at least 30 days before we add a provider that will process their shoppers' data, and a merchant may object under Schedule 1 of the Terms.

Outside India. Some of the providers above process data outside India. We transfer data only where the law allows, and not to any country the Central Government restricts by notification.

Authorities. We disclose personal data where a court, a government authority or the law requires it, and to protect the platform, our users or the public from fraud or harm. Where the law allows, we tell the account holder.

Business transfer. If our business is sold or merged, the data moves with it, under this policy, and we tell you.

We do not sell personal data, and we do not share it with advertisers.

Every period here is carried out by a scheduled job on our servers. A store under a legal hold (section 5.8) is skipped until the hold lifts.

When a period ends we delete or anonymise the data; a copy can remain in our database backups for up to seven days after that, until those backups are overwritten. Where the law requires us to keep something longer, we keep only that. When your account closes, the Terms (clause 14) say what is exported, what is deleted and when; before the eight-year removal of order details we tell the store's owners twice, about 90 and 30 days before, with an export of that year.

We protect personal data with the safeguards the DPDP Rules describe: encryption in transit and at rest; access controls so that only staff whose work needs it can reach it; a record of the changes our staff make, and monitoring of sign-ins and of the service to detect unauthorised access; backups so that the service and your data can be restored; written contracts with every provider in section 6; and the operational telemetry and audit logs in section 7, from which a breach can be detected and investigated. We review these measures regularly. No system is perfectly secure, and we do not promise that ours is.

If a breach of security affects your personal data, we will:

• tell you without delay, with what happened, what data was involved, what it may mean for you, what we are doing about it, what you can do, and who to contact;
• tell the Data Protection Board of India without delay, and give it the detailed report the Rules require within 72 hours;
• report the incident to CERT-In within the time its directions require (currently six hours); and
• where the breach affects your shoppers' data, tell you within 48 hours so that you can make your own notifications as their Data Fiduciary (Terms, clause 14.7).

Three things on the platform are decided automatically. An uploaded file that our safety check cannot clear is refused at upload; you are told the category and score, and you can ask for a person to review it (section 10). A card or UPI fingerprint that matches an earlier signup is flagged for a person to review; it never blocks a signup on its own. A store whose business registration the government register no longer shows as active stops taking new orders until the position is put right (Terms, clause 9.12). We do not otherwise make decisions about you by automated means that have a legal or similarly significant effect.

You can:

• see the personal data we hold about you, and get a copy, with a summary of what we have done with it and who we have shared it with;
• correct it (most of it you can change yourself in your admin) and have incomplete data completed;
• delete it, where the law allows us to (we keep invoices and tax records for as long as the law requires, and acceptance records for the period in section 7);
• withdraw any consent you gave, as easily as you gave it, by unticking the box where there is one, by disconnecting the account concerned, or by writing to us; withdrawing does not undo processing already done lawfully, and we tell you what stops when you withdraw (for a connected account, publishing stops; for a register check, the store cannot open until it is done);
• nominate someone to exercise these rights for you if you die or become unable to, under "Your nominee" at the bottom of Billing in your admin or by writing to us with their name and contact details; we ask the nominee for proof before acting;
• raise a grievance with our grievance officer (section 16) about anything in this policy or our handling of your data; and
• complain to the Data Protection Board of India if you are not satisfied with our answer, or if we do not answer in time.

To use a right, write to privacy@raxcube.com from your account email, or use the options in your admin. We acknowledge within 24 hours and answer within seven days, which is within the period the DPDP Rules allow. There is no fee. We may ask you to confirm your identity first, and we answer only to the account email or through your admin, so that nobody can obtain your data by pretending to be you. The law asks you, in turn, not to impersonate anyone, not to suppress material facts when you give us data, and not to make a false or frivolous complaint.

We do not use a registered Consent Manager at present. If we do, we will say so here.

Your whole account. Write from your account email to legal@raxcube.com; our support desk closes the store, and we confirm the request with you before acting. What is deleted, and what the law makes us keep (invoices and tax records in particular), is set out in the Terms and in section 7.

One piece of information. Most of what you gave us you can change or remove yourself in your admin. For anything else, write to privacy@raxcube.com.

What Google gave us. Remove our access from your Google Account, then ask us to close your account as above.

What Meta gave us. Disconnect the account from Social in your admin, which deletes the key at once; or remove our access in the account's settings at Meta, which deletes it as soon as Meta tells us, and within a day at most. "Delete my Meta data" in Social deletes the rest: the account names and identifiers, the post records and the WhatsApp messages. Removing RaxCube in your Facebook settings does the same for every store you connected, and Meta gives you a status page to follow it. Section 4 and raxcube.com/data-deletion.html explain each path.

If you are a shopper, the store's own notice and raxcube.com/data-deletion.html say what you can delete yourself on the store, and how to delete WhatsApp messages with DELETE MY DATA.

We answer within seven days and tell you what we deleted and what we had to keep, and why.

Our services are for adults and businesses. We do not knowingly collect personal data from anyone under 18. If you believe a child has given us data, tell us and we will delete it.

Our marketing site and the Studio site set no cookies of their own, and load no fonts or scripts from other companies as a page opens. The signup page loads Google's sign-in script only when you press Continue with Google, and Razorpay's checkout script only when you press Pay; each of those may then set its own cookies under its own policy. Your store admin keeps you signed in with a cookie that only our server can read (it lasts 14 days without use and 30 days at most) and is revoked when you sign out; the admin keeps only a sign-out marker and your dismissed notices in local storage. Shoppers on a store are kept signed in by a token in their browser's local storage, which is removed when they sign out, and a store also sets a cart cookie and may remember checkout details in local storage if the shopper asks it to. Visit counting on raxcube.com uses a temporary id in your browser's session storage, as section 3.16 describes. Stores built on RaxCube have their own cookie notice, set by the store. Where a store has connected Google Analytics, it runs only if the shopper presses Accept on the store's cookie bar: nothing from Google loads before an answer or after "Only what's needed", withdrawing later stops it at once, and its cookie is confined to that store's own address so shoppers are not linked across stores.

Because we do not track you across sites, there is nothing for a browser's "Do Not Track" setting to switch off on our own sites.

The IT Rules require us, as an intermediary, to remind our users at least once every three months of this policy, the Terms and the rules on what may not be published, and of what happens if they are broken. We do that by email to your account email, and whenever this policy changes in substance.

We process your data in India under Indian law, as this policy describes. If the law of your country gives you further rights, for example under the EU or UK General Data Protection Regulation, you have them in addition, and you can exercise them through the same contact in section 16. Where your law requires a specific legal basis or transfer safeguard for sending data to India or to the providers in section 6, we rely on your consent given at signup and on the contracts with those providers, and we will put in place any further safeguard your law requires on request.

Grievance officer: Anuradha, a partner of TECHNOSTAT LABS LLP, who is our Grievance Officer under the IT Rules 2021, the SPDI Rules 2011 and the DPDP Act 2023.

grievance@raxcube.com · Monday to Friday, 10:00 to 19:00 IST

Data requests (a copy, a correction, a deletion): privacy@raxcube.com

TECHNOSTAT LABS LLP, No. 347, 41st Cross, 8th Block, Jayanagar, B Sk II Stage, Jayanagar, Bangalore South, Bangalore – 560070, Karnataka, India

Messages that arrive outside those hours are still acknowledged within 24 hours. The grievance officer is also the person who can answer your questions about how we process your data.

Our sites send you to other websites: to stores built on RaxCube; to Razorpay when you pay; to Google when you sign in with Google; to DigiLocker when you confirm a business number is yours; and to Facebook (facebook.com) when you connect an Instagram account, a Facebook Page or a WhatsApp Business account, because Meta's own sign-in dialog is where you grant those permissions. The links in your admin to posts we have published for you open Instagram or Facebook. Each of those sites has its own privacy notice, and this policy does not cover what happens there. A store's own notice is linked from the foot of every page of that store.

When we change this policy in substance we publish a new version with a new date and tell account holders by email before it takes effect. We keep every earlier version, and will send you the version that applied on any date if you ask.

This policy is in English. You may ask for it in any language listed in the Eighth Schedule to the Constitution of India and we will provide it. Where the law requires, the notice you are given when you consent to something is available in the same languages.