Privacy policy

1. Who we are

"Zoorik", "we" and "us" mean Zoorik Private Limited, a company incorporated in India, CIN U62011KA2026PTC228102, with its registered office at Vaishnavi Signature, No. 78/9, Outer Ring Road, Bellandur, Bangalore South, Bangalore 560103, Karnataka.

Zoorik makes two products: Coral, which rebalances Kubernetes clusters on Azure and AWS, and Amoeba, which rightsizes block storage on Azure. You can reach us at founders@zoorik.com. Section 15 names our grievance officer.

2. What this policy covers

• zoorik.com, including zoorik.com/login and zoorik.com/assessment. www.zoorik.com and our other domains only redirect to zoorik.com.
• Coral: the service and its console, currently at dev.zoorik.com/coral.
• The Coral agent and its node daemon, which you install in your own clusters.
• Amoeba: the service and its console; the Amoeba agent, which Amoeba installs on the Azure VMs you choose; and Amoeba's set-up script, which you run in Azure Cloud Shell.
• zoorikctl, our command-line tool, downloaded through get.zoorik.com.
• The free assessment scripts at zoorik.com/assess/k8s and zoorik.com/assess/disks.
• Email you send us, calls you book with us, and leads that reach us from Microsoft Marketplace.

What other companies do for themselves. When you sign in with Microsoft or Google, book a call through Cal.com, download from GitHub, visit zoorik.com while Microsoft Clarity records the visit, or reach a film that YouTube's player shows on zoorik.com, those companies also use your data for their own purposes, under their own privacy policies. This policy covers what reaches Zoorik and what those companies do for us (section 7). It does not cover LinkedIn or X, which we only link to.

3. Our two roles

We decide how the data is used (controller). This covers your Coral account, your Amoeba organisation's records, our website, email you send us, calls you book, Marketplace leads, assessment files you send us, and our own logs. India's Digital Personal Data Protection Act, 2023 (the DPDP Act) calls this role a "Data Fiduciary"; the GDPR calls it a "controller".

We act for our customer (processor). When an organisation connects a cluster, the Coral agent sends us data about that cluster (section 4.2). When an organisation connects Amoeba, Amoeba reads data about its Azure VMs and disks, and the Amoeba agent sends us data about those VMs (section 4.3). The customer organisation is the controller of that data. We use it only to provide Coral or Amoeba to that customer, under the customer's agreement with us.

If your personal data appears in a customer's cluster or VM data, that customer's privacy notice applies, so please contact them. If you contact us instead, we will refer you to them.

4. What we collect, and why

Legal basis in India. Under India's DPDP Act, we use the data in sections 4.1, 4.3 (your Amoeba organisation), 4.4 and 4.7 because you, or the person who connected your organisation, gave it to us or let our products read it for that purpose (section 7(a) of the Act). If you tell us you no longer want us to use it, we stop. We do not rely on your consent for anything else. The "Legal basis" entries below are the bases under the GDPR (section 11.3).

4.1 Your Coral account

You sign in with Microsoft (a work, school or personal account) or Google. Your browser goes to them, they check your password, and they send us a signed sign-in token. We ask only for your basic profile and email address (the openid, profile and email scopes). We keep only the facts in that token, and no Microsoft or Google token.

Your organisation

• When your first cluster connects, Coral creates an organisation and makes you its Owner. It is named after your email domain, or "[your name]'s organization" if your email is unverified or on a consumer domain such as gmail.com.
• If someone later connects a cluster from an Azure subscription or AWS account your organisation already holds, they join your organisation as a Viewer.
• Other members can see your display name on rebalancing runs you started, and your person id on workload events you started.

4.2 Cluster data the Coral agent sends (we act for the customer)

How the agent connects. Inside your environment, the agent reads from the Kubernetes API, each node's kubelet and your cloud's instance metadata. It also calls your cloud's API to look up and remove nodes, using a node-removal identity in your own account. The only place outside your cluster and cloud account it sends data to is Zoorik, over outbound HTTPS. It fetches Coral's instructions from Zoorik and accepts no inbound connection.

If the agent cannot reach us, it keeps usage summaries for later in a buffer of up to 1 GiB inside its own pod, in your cluster.

Most of this data describes machines and software, not people, but it can contain personal data: a namespace, label, node name or message might include a person's name. Members of the customer's organisation see this data in the Coral console.

4.3 Amoeba

Amoeba rightsizes block storage on Azure. It moves the data on a VM's data disks onto a pool of new managed disks sized to what you use, then grows and shrinks that pool. Your Amoeba organisation is separate from any Coral organisation.

Connecting Amoeba. You run a set-up script in Azure Cloud Shell, signed in to your own Azure account. It adds Zoorik's Amoeba app (one Microsoft Entra app, registered by Zoorik and used for every customer) to your directory, creates a custom role called Zoorik Storage Operator, and gives that role to the app on the current subscription. You then enter your directory (tenant) id in Amoeba. When a directory id is entered, Amoeba creates an organisation for it, even before the set-up script has run, and checks every 15 seconds whether the directory has connected. Amoeba acts in your subscription only through that app, with the role you gave it. We never receive your Azure password or a token for you.

What the role allows. It lets Zoorik's app read the settings of every resource in the subscription, change VMs and run commands on them as root (as SYSTEM on Windows VMs), and create, change and delete managed disks and snapshots. The set-up script also grants permissions to manage VM extensions and resource locks and to download disks; Amoeba does not use them.

Choosing a VM is an instruction. Choosing a VM in Amoeba is your organisation's instruction to us to:

• install the Amoeba agent on it;
• copy its data disks onto a pool of new disks, inside the VM;
• 48 hours later, once each original disk's snapshot has succeeded, delete the original disks;
• delete those snapshots 7 days after that;
• grow and shrink the pool, deleting pool disks it no longer needs.

What Amoeba reads from your subscription (we act for the customer). The VMs it can manage and their data disks: ids, names, resource group, region, zone, size, operating system type and image, power state, and each disk's name, type, size and performance. Also your subscriptions' and directory's display names, and Amoeba's own tags on disks and snapshots. It reads nothing from billing, Cost Management, Azure Monitor, the Activity Log or Microsoft Graph. Prices come from Microsoft's public price list (prices.azure.com).

To keep your onboarded VMs current, Amoeba also checks every VM in your connected subscriptions every 60 seconds (its resource id, size and power state), and every data disk attached to a VM in any subscription that holds a VM you onboarded. It keeps only the rows for VMs you onboarded. The list of VMs you can onboard includes Windows and stopped VMs, and is kept only in our server's memory.

The Amoeba agent. Amoeba installs the agent on each VM you choose by running a short command as root through Azure Run Command. The installer may install curl, Java 17 and a few system packages from your distribution's mirrors, and it downloads the agent from GitHub, which sees your VM's IP address. The agent runs as root as a systemd service, opens no port, and connects out only to Amoeba. It acts only on commands Amoeba signs with that VM's own key.

What the agent sends us (we act for the customer).

• Every 15 seconds, a storage report for each data mount: its path, filesystem type, the managed disks and devices behind it, total and used space, read and write performance, and the name of the systemd service writing to it, such as postgresql.service. To find that service, the agent looks at which mount each open file is on; file paths are not sent.
• The VM's resource id, the agent's version, the kernel release and a few filesystem facts.
• Replies to Amoeba's commands, which can include device names, mount points and error messages that quote paths on your VM.
• Copy progress during a migration.
• If an install, restart or update fails, the last lines of the agent's log from the VM's system journal (keys removed, up to 300 characters). These can name mount paths, devices, services and files.

The agent's reports contain no hostname, IP address, user names or process lists, and the contents of your files are never sent to us. Our servers and Cloudflare still see the public IP address your VM connects from. The rest of the agent's log stays in the VM's journal.

What we store. Your organisation's record is ours (section 3); we hold the rest for your organisation. Legal basis for our part: to provide Amoeba under our contract with your organisation, and our legitimate interest in security. We store your organisation (a random id, your directory's id and name, your subscriptions' ids and names, and when Amoeba lost access); the VMs and disks you onboard; usage history (6-hour peaks, daily savings and an hour-of-week activity profile); each VM's agent key, status and version; pool and migration records, including mount paths, plans and errors; an audit log of the actions Amoeba takes; and recent reports in a cache for up to 72 hours. Names of your directory, subscriptions, resource groups, VMs, disks, mounts and services are kept as you wrote them, and any of them might include a person's name. Everyone who opens Amoeba for your organisation sees this data.

What Amoeba changes. In your subscription, it creates pool disks named zoorik-amoeba-pool-…, tags and detaches your original disks, snapshots them as zoorik-amoeba-snap-…, and deletes them as described above. On the VM, the agent formats the new disks as a btrfs pool, copies your files into it with rsync, rewrites /etc/fstab after backing it up, and stops and restarts the services that use a mount while it switches the mount over.

4.4 zoorikctl and downloads

• zoorikctl sends us your connect token and a user agent naming the zoorikctl version, your operating system and your architecture. We use the token to connect your cluster to your organisation, and the user agent to see which versions are in use and fix problems. Legal basis: to provide Coral, and our legitimate interest in supporting the versions people run.
• zoorikctl cluster disconnect does not contact Zoorik.
• Cloud set-up runs under your own az or aws sign-in, so we never receive your cloud credentials.
• When you download zoorikctl through get.zoorik.com, Cloudflare and GitHub see your IP address and your download tool's user agent. When you install it from our Homebrew tap (getzoorik/tap), or your cluster pulls the Coral agent images from GitHub's registry, GitHub sees them.
• zoorikctl's region is labelled "us". That is only a label: it points at the Coral service hosted in Central India (section 8).

4.5 Our logs

• Coral's backend identifies organisations, clusters, people and requests in its logs by id, not by email address. Some lines contain cluster names, node names and cluster resource ids.
• Coral's backend, and the gateway in front of it, do not log your IP address or your browser's user agent.
• Amoeba's backend logs directory, subscription and VM ids, the names of the disks it creates, attaches and deletes, the agent's install progress, and the reasons the agent gives for refusing a command, which can include mount paths, device names and error messages. It logs the IP address of an agent connection it refuses or that fails while connecting.
• Cloudflare sits in front of our servers and handles every request, including your IP address (section 7).

We use logs to run the service, keep it secure and fix problems. Legal basis: our legitimate interest in doing those things.

4.6 zoorik.com

What the site itself does

• It has no forms. The choices on zoorik.com/assessment stay in your browser, and the Copy button writes the command only to your clipboard: Clarity learns that you copied it, not what (below).
• Its own code sets no cookies and uses no browser storage. It serves its own fonts.
• It has no advertising, no chat widget and no embedded maps. Its one analytics service is Microsoft Clarity, and its one embedded video player is YouTube's, on two pages (both below).

Microsoft Clarity. Every page of zoorik.com, this one included, loads Microsoft Clarity once the page has finished loading. Clarity records how the page is used, so that we can see what helps visitors and what gets in their way. While you are on a page, it sends Microsoft:

• your clicks, taps, scrolling and mouse movements, and the size of your window;
• when you copy the command on zoorik.com/assessment, click a link to book a demo, or click our email address: the name of that action, so that we can count how often each one happens and on which pages. It is only the name: not the command, and nothing you then do on Cal.com or in your email app;
• the page's address, the page you came from, and what the page showed and how it changed, so that we can replay the visit and see heatmaps. Clarity hides what you type into a field, and the numbers and email addresses on the page, in your browser before anything is sent;
• your browser, operating system, device type and screen size;
• page-speed measures and script errors.

Microsoft receives your IP address with each upload and uses it to work out your country. On zoorik.com, Clarity sets no cookies and uses no browser storage, so it does not link one page you view to the next, or one visit to the next. Microsoft also uses this data for its own purposes, including Microsoft Advertising, as the Microsoft Privacy Statement describes (https://privacy.microsoft.com/privacystatement (opens in a new tab)). To stop Clarity recording your visits, turn on Global Privacy Control in your browser, opt out of Microsoft at https://optout.aboutads.info (opens in a new tab), or block scripts from clarity.ms.

YouTube. zoorik.com/coral and zoorik.com/amoeba each show a 2-minute film in YouTube's player, in its privacy-enhanced mode (youtube-nocookie.com). The player loads when you scroll to the film, and the film then starts by itself: with its sound if you have already clicked, tapped or typed on the page, otherwise muted until you do. If your device asks for reduced motion, the player loads only when you press play or a chapter. Once it loads, your browser connects to YouTube, which is Google: Google receives your IP address, your browser and device details and how you use the player, and the player may set cookies and use browser storage. Google uses this under its own privacy policy (https://policies.google.com/privacy (opens in a new tab)). No other page of zoorik.com loads anything from YouTube. To avoid it, block youtube-nocookie.com in your browser, or leave the page before you reach the film.

What Cloudflare adds. Cloudflare hosts zoorik.com and adds three things to every page:

• Web Analytics: a script that sends Cloudflare the page address and the page you came from (without query strings), your browser's user agent and client hints, and page-speed measures. It sets no cookies and uses no browser storage.
• Bot detection: a script that sends Cloudflare signals about your browser, sets the cookies cf_clearance and __cf_ob, and stores _cfPre_tabId in your browser's session storage (section 6).
• Network error reports: if a page fails to load because of a network problem, your browser may report the failure to Cloudflare.

We use this to deliver the site, protect it from bots, see how fast it is and how it is used, and improve it. Legal basis: our legitimate interest in running a secure, working website and making it better.

4.7 Email, calls and Marketplace leads

• Email. When you email us at founders@zoorik.com, we receive your email address, your name if you give it, your message and any attachments, such as an assessment file. Google Workspace hosts our email. We use it to answer you and to work out what Coral or Amoeba could do for you. Legal basis: steps you asked us to take before a contract, or our legitimate interest in answering you.
• Calls. When you book a call at cal.com/zoorik/talk (opens in a new tab), you give your details to Cal.com and the booking reaches us. We use it to hold the call. Legal basis: steps you asked us to take.
• Microsoft Marketplace leads. If you ask to be contacted from Coral's Microsoft Marketplace listing, Microsoft sends us the details you gave, such as your name, email address, phone number, country, company and job title. We use them to contact you about Coral. Legal basis: our legitimate interest in answering your request.
• Coral itself sends no email.

4.8 The free assessment

• You run it with npx -y zoorik assess coral or npx -y zoorik assess amoeba. npm and PyPI, which serve it, see your IP address and your tool's user agent. The older links zoorik.com/assess/k8s and zoorik.com/assess/disks redirect to the public scripts on GitHub; when you fetch one, Cloudflare and GitHub see the same.
• It runs on your machine or in your Cloud Shell, with your own signed-in az, aws and kubectl tools. It never contacts Zoorik. Its only other network call fetches public prices from Microsoft (prices.azure.com); AWS prices come through your own aws tool.
• It writes one PDF report on your machine and uploads nothing. If you email it to us, it contains the names of your clusters, node pools, namespaces and workloads, with machine sizes and counts, CPU and memory requests and peak use, and prices (Coral), or the names of your Azure subscriptions or AWS accounts and your VMs, with their sizes, disk sizes, used space and prices (Amoeba). Coral's --anonymize option replaces namespace and workload names with hashes, and --anonymize-clusters also replaces cluster names. Node-pool names are kept.
• If you allow it, the Amoeba assessment runs one read-only command inside your Linux VMs through Azure Run Command or AWS Systems Manager Run Command. Your cloud keeps a record of it in your own account; we do not receive it.

5. What we do not collect

• Sensitive personal data as listed in India's SPDI Rules: passwords, financial details, health, medical or biometric data, or sexual orientation.
• Your password, or any Microsoft or Google token. We read the sign-in token once to get the facts in section 4.1, and keep no Microsoft or Google token.
• Your cloud credentials. Set-up runs under your own sign-in. Coral's node-removal identity lives in your own cloud account, and Amoeba acts through Zoorik's app with the role you give it.
• Your Kubernetes Secrets and ConfigMaps. The Coral agent can read only Zoorik's own Secrets and ConfigMaps, and the cluster autoscaler's status ConfigMap. Coral's node daemon runs as root and can reach anything on its node, including mounted Secrets, but it has no connection to Zoorik.
• Your pod logs, or a shell in your pods. The Coral agent has no permission to read pod logs, or to exec into, attach to or port-forward to pods. It reads kubelet metrics through the Kubernetes node proxy, which could also reach the kubelet's log and exec endpoints; Coral never calls them.
• Environment variables, commands and image names. The Coral agent reads pod specs to size and place workloads, and, inside your cluster, looks at environment variable names, Java option values, commands, arguments, image names and annotations to spot Java workloads. None of these is sent to us. The only annotation sent is coral.zoorik.com/configuration.
• The memory of your pods. To move a running pod, Coral's node daemon runs as root on each Linux node and checkpoints the pod. The checkpoint holds the pod's memory, which can include secrets the program holds. It stays inside your cluster, moves between the two nodes over mutual TLS, and is deleted when the move ends. The node daemon has no connection to Zoorik.
• The contents of your files (Amoeba). They are never sent to us. The Amoeba agent copies them only between disks attached to the VM, and the original disks and their snapshots stay in your subscription until Amoeba deletes them (section 4.3). The agent's regular reports carry no file names, but an error message or a failed-install log extract can quote a path on your VM.
• Anything from the assessment scripts, unless you email us the file.

6. Cookies and browser storage

On the Coral console

The two cookies are needed to sign in; both are Secure and HttpOnly, use SameSite=Lax, and are sent only to the address the console is served from. The console's own three storage items only remember your choices; _cfPre_tabId is Cloudflare's, for bot detection. None is used for analytics or advertising. The console's own code loads no analytics, tracking or third-party script, and its security policy blocks Cloudflare's Web Analytics script.

On the Amoeba console

The cookie is Secure and HttpOnly and uses SameSite=Lax. The Amoeba console loads no analytics, tracking or third-party script. It puts the open VM's resource id in its page and API addresses, so the id appears in your browser history and in any access logs Cloudflare or our gateway keep.

On zoorik.com

All three are Cloudflare's, for bot detection (section 4.6). cf_clearance is set for zoorik.com and its subdomains, so your browser also sends it to the Coral and Amoeba consoles. zoorik.com's own code sets no cookies, and Microsoft Clarity is set to use no cookies or storage here. YouTube's player on the Coral and Amoeba pages may set its own cookies and browser storage once it loads (section 4.6).

You can block or clear cookies and storage in your browser. If you block the consoles' cookies, you cannot sign in to Coral or open Amoeba.

7. Who we share data with

We do not sell personal data and do not use it for advertising. We disclose personal data to a government body or court only when the law requires it.

These companies help us run Zoorik. When one of them handles personal data for us, we stay responsible for it. For the cluster and VM data we process for customers (section 3), our sub-processors are Microsoft Azure and Cloudflare.

Inside your organisation, other members see what section 4.1 describes and the cluster data your organisation connected. In Amoeba, everyone who opens it for your organisation sees its VM data (section 4.3).

8. Where data is stored, and international transfers

• Coral's and Amoeba's databases, backups, key vault and container registry are in Microsoft Azure, Central India. Backups are not copied to another region. Sessions are held in memory only, inside our cluster.
• Our email, sign-in, hosting, download, website analytics and video providers may process data in other countries, including the United States. Microsoft Clarity stores what it records in Microsoft's cloud.
• If you are outside India, your data is transferred to India, where Coral and Amoeba are hosted. Some providers in section 7 handle data outside India. From about May 2027, India's DPDP Act allows this except to countries the Government of India restricts. India has no EU adequacy decision. Where the law requires a safeguard for such a transfer, such as standard contractual clauses for data from the EU or UK, we put one in place; email us for a copy.

9. How long we keep data

Set by how Coral and Amoeba work

• Sign-in cookie: 10 minutes, or until sign-in completes.
• Session: ends after 30 minutes idle, 12 hours, or sign-out; the server-side record is kept in memory only until then.
• Current inventory of namespaces, autoscalers, node pools and placements: replaced every 5 minutes.
• Short-lived workload signals: 24 hours.
• Database backups: 7 days.
• Amoeba's cache of recent agent reports: up to 72 hours; copy progress: 2 hours; Amoeba sessions: 24 hours, in memory only; the list of VMs you can onboard: in memory only, until the next check replaces it.
• Your original disks after an Amoeba migration: deleted 48 hours after the copy, once their snapshot has succeeded; the snapshots: deleted 7 days later (section 4.3).

Set by us

• Your account, organisation and connect token records: while your organisation uses Coral, and for 30 days after it closes its account or you ask us to delete your data.
• Amoeba organisation, VM, usage and migration records, and the audit log: while your organisation uses Amoeba, and for 30 days after it stops or asks us to delete them.
• Cluster data (usage history, inventory, events): while the cluster reports to us, and for 30 days after it stops reporting or the customer asks us to delete it.
• Logs: 1 year. Logs the law requires us to keep longer stay for the period it sets.
• Email, assessment files and bookings: 2 years after our last exchange with you.

Set by Microsoft Clarity (zoorik.com)

• Recordings of visits: 30 days. Recordings we mark as favourites, and a random sample Microsoft keeps: up to 9 months.
• Heatmaps: up to 9 months.

Disconnecting a cluster. zoorikctl cluster disconnect removes Coral from your cluster and offers to remove the cloud identity it created. It does not delete the data we already hold; to have it deleted, email founders@zoorik.com.

10. How we protect data

• In transit: every connection to Zoorik from the internet uses HTTPS. Plain HTTP is redirected, and browsers are told to use HTTPS only (HSTS). Inside our cluster, the session store accepts connections only from Coral's backend. Cloudflare re-encrypts traffic to our servers and checks their certificate, and our web gateway accepts connections only from Cloudflare. Coral reaches its database over TLS 1.2 or later.
• At rest: Microsoft Azure encrypts our database and disks.
• Coral sign-in: no passwords; OpenID Connect with PKCE and a nonce; Secure, HttpOnly cookies; anti-forgery tokens; sessions end after 30 minutes idle or 12 hours. The console cannot be framed by other sites, and it loads scripts only from its own address, which is also where Cloudflare serves its bot-detection script (section 6).
• Separation (Coral): row-level security in the database keeps each organisation's data apart, and every agent upload is tied to the organisation of its authenticated credential.
• Credentials: connect tokens and cluster credentials are stored only as SHA-256 fingerprints. A connect token works once and expires after 60 minutes; a cluster credential lasts 90 days and is replaced automatically before it expires. We hold no customer cloud credentials. Coral acts through an identity in your own cloud account. Amoeba acts through Zoorik's app, which your admin approves and gives a role; Zoorik proves the app's identity to Microsoft with a credential that only Zoorik's servers can use. Each Amoeba agent has its own key, which signs Amoeba's commands to it.
• Access: only a small number of people at Zoorik, and the automated tools we use to build and deploy our products, can access or change the systems that run them.

If a breach affects your personal data, we will tell you, and the authorities the law requires us to tell. To report a security problem, email founders@zoorik.com.

11. Your rights

11.1 How to use them

Email founders@zoorik.com from the address you sign in with, or the address you used to contact us, and tell us what you want. For Amoeba, include your directory id. We may ask you to confirm that you control that address. We reply within 30 days; if a request is complex, we will tell you within those 30 days why we need more time. If your data is part of a customer's cluster or VM data, ask that customer (section 3).

11.2 If you are in India

We honour these rights now. India's DPDP Act makes them legal rights from about 13 May 2027. You can:

• get a summary of your personal data, what we do with it, and who we share it with;
• have your data corrected, completed, updated or erased;
• tell us that you no longer want us to use data you gave us (section 4): email us from the address you sign in with or, for Amoeba, include your directory id. We will stop, and tell you if that means you can no longer use Coral or Amoeba. This does not affect what we did before;
• nominate someone to use your rights if you die or cannot act: email us their name and contact details;
• raise a grievance with our grievance officer (section 15). If our answer does not resolve it, you can complain to the Data Protection Board of India.

11.3 If you are in the EU or UK

You can ask for access to your data, correction, erasure, restriction, and a machine-readable copy (portability). You can withdraw consent at any time where we rely on it, and object, for reasons about your own situation, to processing based on our legitimate interests; we will then stop unless we have compelling reasons that outweigh your interests or need the data for a legal claim. You can complain to us, to your country's data protection authority, or in the UK to the Information Commissioner's Office.

11.4 Elsewhere

Your local law may give you similar rights. Email us and we will help.

11.5 Do you have to give us data?

You can browse zoorik.com without giving us your name or email address; Cloudflare and Microsoft Clarity still receive what section 4.6 describes, as does YouTube once its player loads on the Coral and Amoeba pages, and section 4.6 says how to stop Clarity recording your visits. To use Coral, you must sign in with Microsoft or Google. To use Amoeba, your admin must connect your Azure subscription (section 4.3).

11.6 Automated decisions

We make no decision that has legal or similarly significant effects on you based only on automated processing. Coral does make some account decisions automatically: for example, it adds you to an organisation as a Viewer when you connect a cluster from a subscription or account that organisation already holds (section 4.1). You can ask us to review any of them.

12. Children

Zoorik is a service for businesses and is not meant for anyone under 18. We do not knowingly collect data from anyone under 18. If you think someone under 18 has given us personal data, email founders@zoorik.com and we will delete it.

13. Changes to this policy

When we change this policy, we post the new version here and update the date at the top. Before we use your personal data for a new purpose, we will tell you and update this policy first. Amoeba keeps no contact details, so for Amoeba we will show the notice in the Amoeba console. Earlier versions are available on request from founders@zoorik.com.

14. Language

This policy is in English only.

15. Contact us and grievance officer

Email: founders@zoorik.com · Post: our registered office (section 1).

Grievance officer and privacy contact (India). This person handles grievances and answers questions about how we process your personal data. Every reply we send to a rights request includes these details.

• Name and title: Sheldon, CXO
• Email: founders@zoorik.com
• Postal address: Zoorik Private Limited, Vaishnavi Signature, No. 78/9, Outer Ring Road, Bellandur, Bangalore South, Bangalore 560103, Karnataka

We acknowledge a grievance within 2 working days and resolve it within 30 days.