Privacy

How Veloccy handles your data.

This policy explains what Veloccy collects, why, where it is kept, who else handles it and how to have it deleted. It covers veloccy.com and the Veloccy app at app.veloccy.com.

Last updated 31 October 2026

Who we are

Veloccy is made by Veloccy Private Limited, a company registered in India (CIN U62099WR2026PTC296365). In this policy, “we” and “us” mean Veloccy Private Limited.

Prithvish Baidya, co-founder (engineering and product), is responsible for how we handle personal data, and answers privacy questions and complaints. Write to contact@veloccy.com, or to him directly at prithvish@veloccy.com.

Your data and your company’s

When a company uses Veloccy, the data in its own systems belongs to that company. The company decides what Veloccy may read and what for, and we handle that data on its behalf and on its instructions. Under India’s Digital Personal Data Protection Act, 2023, the company is the data fiduciary and we are its data processor. Under the GDPR, the company is the controller and we are its processor.

If you are a shopper, an employee or anyone else whose details are in one of our customers’ systems, that company is the one to ask about them. We will help it answer you.

For the people who use Veloccy, and for visitors to veloccy.com, we decide what is collected, and this policy says what that is.

What we collect

When you visit veloccy.com

We use PostHog to see how people use the site: the pages you open, which parts you read and for how long, what you click, your kind of device and browser, and the rough location your IP address suggests. We also record what you type into the site’s forms, such as the question box and the early-access form, including text you do not send. PostHog keeps an identifier in your browser so it can tell one visit from the next.

If you send the early-access form, we keep what you entered, such as your name, work email, company and role, so we can reply.

When you use the app

  • Your account. Your name and email address, and how you sign in: a password (we keep only a one-way hash of it), a passkey, a two-factor secret (kept encrypted), or your Google or Slack sign-in.
  • Your organisation. The companies you belong to, your roles in them, and the invitations you send and receive.
  • Sign-in and safety records. When you signed in, changes to roles, support sessions our team opened with your company’s permission, and the network addresses of requests, which we use to stop abuse.
  • What you do in Veloccy. The messages you send to Veloccy, in the app or in Slack. The work Veloccy writes for your company, such as findings, plans, proposed changes and dashboards, and who approved each change. The full transcript of each conversation, including what Veloccy read and the results of its queries.
  • Usage. For each AI model call, web search and page fetch: which company and person it was for, the model, how much it used and what it cost. For a search we keep the search terms, and for a page fetch its address. These records never hold the text sent to a model.
  • Credentials. The keys, tokens and sign-ins your company connects, and AI model keys or subscription sign-ins. The next section explains how they are kept.

Your company’s systems

Veloccy reads the systems a company connects to it, such as Shopify, Google Analytics, Google Sheets, Gmail, Meta ads, Instagram, GitHub, PostHog and Slack. An owner of the company chooses which systems to connect, and can disconnect any of them in Settings at any time.

Read access first

Veloccy asks each system for read-only access wherever the system offers it. Where Veloccy is also able to make a change in a system, for example opening a pull request on GitHub, it can do so only after an owner of the company has turned that on in Settings.

Credentials stay with us, sealed

When you connect a system, its key, token or sign-in goes to Veloccy’s credentials gateway, which seals it with AES-256 encryption and adds it to each request as the request leaves. The AI never sees a credential, and the sandboxes where Veloccy’s work runs never hold one.

What is copied, and what is read live

So that answers come quickly, Veloccy keeps a copy of some numbers in a database of the company’s own: orders, products, stock, ad results and site traffic. From Shopify it copies no shopper’s name, email address, phone number or postal address, and each shopper appears only as a coded key that cannot be traced back to them.

Everything else is read live, when a piece of work needs it. What Veloccy read is kept in that conversation’s transcript.

Signed-in browsers

For a system with no API, a person at the company can sign in to it in a browser that Veloccy uses. We keep that signed-in browser sealed in our own storage, and use it only for that company’s work.

Google user data

When you sign in to Veloccy with Google, we receive your name and email address, and use them only to sign you in.

When an owner connects a Google account to their company, Veloccy asks Google for read-only access to what the company chooses to connect:

  • Google Analytics, to read the reports of the company’s properties;
  • Google Sheets, to read the company’s spreadsheets;
  • Gmail, to read the connected mailbox;
  • and the Google account’s email address, to show which account is connected.

We use this data only to provide the features the company uses in Veloccy: answering its people’s questions and doing the analysis and work they ask for. To do that work, Veloccy sends the data a task needs to the AI model provider the company has chosen, and nowhere else, except where the law requires it or as part of a merger or sale of our company, which we would tell you about first.

We do not sell Google user data, use it for advertising, or use it to decide anyone’s creditworthiness. We do not use data from Google Workspace APIs to develop, improve or train generalized AI or machine-learning models. No one at Veloccy reads it, unless you ask us to, it is needed to investigate abuse or a security problem, or the law requires it.

Veloccy’s use and transfer to any other app of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements.

You can disconnect Google in Veloccy’s Settings, or remove Veloccy’s access at any time from your Google account’s third-party connections.

How we use data

  • To run Veloccy for your company: read your systems, answer your questions, do the work you ask for and keep it for your team.
  • To keep Veloccy secure, and to find and stop abuse.
  • To help you. When you report a problem or ask for help, we may look at the conversation it is about, and with your company’s permission our team may open your company in Veloccy.
  • To bill your company, and to keep accounts and tax records as the law requires.
  • To improve Veloccy, from how people use the site and the app.

We do not sell personal data, we do not show ads, and we do not use one company’s data in another company’s work. We do not train AI models on your company’s data.

Who else handles it

These companies handle data for us, each only for the job named here.

WhoWhat they do for VeloccyWhere
HetznerRuns our servers: the app’s back end, each company’s files and database, and the sandboxes where Veloccy’s work runs.Germany
PlanetScaleHosts our database of accounts, organisations, roles, usage records and sealed credentials.Frankfurt, Germany
CloudflareCarries all traffic to veloccy.com and the app, runs the web app (Workers), stores our backups and the sealed transcripts and browser sign-ins (R2), sends our email, and relays the live view when you watch Veloccy’s browser (Realtime).Cloudflare’s global network; backups in the EU
OpenAI, AnthropicThe AI models that read what a task needs and write the answer. Your company chooses the provider, and whether calls go through our account, your company’s own API key, or a person’s own ChatGPT subscription, which only that person’s requests use.United States
Tavily, BraveWeb search. They see the search terms.United States
SlackIf your company connects it: messages between your team and Veloccy in your own workspace.Slack’s regions
PostHogAnalytics for veloccy.com.United States

The AI model providers handle data under their API terms, which do not let them train on it. When a person connects their own ChatGPT subscription, OpenAI handles their requests under that person’s own ChatGPT terms and settings.

The systems your company connects, such as Shopify, Google, Meta or GitHub, are your company’s own. They see Veloccy’s requests under your company’s agreement with them.

Some of these companies are outside India. We send data to them only to provide Veloccy, and we will give your company a data processing agreement if it needs one.

How we keep it safe

  • Your company’s files and database, and the sandboxes where its work runs, are on our own servers in Germany. Each piece of work runs in a sandbox of its own, made for it and deleted when it ends.
  • Credentials, transcripts and browser sign-ins are sealed with AES-256 encryption. Our credentials gateway opens them only for that company’s own work.
  • Backups of your company’s files are encrypted before they leave our servers.
  • Our servers take no connections straight from the internet: the public reaches them only through Cloudflare, and our team only over a private network.

If we learn that your company’s data has been exposed, we will tell your company promptly, say what happened and what we are doing, and help it meet its own duties to tell others. Our security page says how to report a security problem.

How long we keep it

  • Your company’s data, the work Veloccy wrote, transcripts and usage records are kept while your company uses Veloccy.
  • Backups are made every six hours and kept for 7 days, and daily ones for 30 days.
  • Server logs are kept for up to 30 days.
  • Your account is kept until you or your company ask us to delete it.
  • Early-access entries and website analytics are kept until you ask us to delete them.

When a company stops using Veloccy, or asks us to, we delete its data within 30 days, and the last backups that hold it expire 30 days after that. What the AI model and search providers keep is kept on their terms, and messages in your Slack stay in your workspace. How to ask for deletion.

Your rights

You can ask us for a summary of the personal data we hold about you, and ask us to correct it, complete it or delete it. Where we rely on your consent, you can withdraw it. Under India’s data protection law you can also nominate someone to act for you, and if you are in the European Union or the United Kingdom you can also object to how we use your data and ask for a copy you can take elsewhere.

Write to contact@veloccy.com. We reply within 30 days. If the data is your company’s, we will pass your request to your company and help it answer. If you are not happy with our answer, you can complain to the Data Protection Board of India, or to the data protection authority where you live.

Cookies

veloccy.com uses PostHog’s identifier, described above, and no advertising cookies. The app uses a cookie to keep you signed in, which it needs to work.

Veloccy is for businesses, and not for anyone under 18.

Changes and contact

When we change this policy we change the date at the top. If a change matters to how your company’s data is handled, we email your company’s owners before it takes effect.

Questions about this policy, or about your data: contact@veloccy.com.

Get early access

We take on a few teams at a time because we set each one up ourselves. Tell us about yours and one of the founders will reply personally, usually the same day.

Veloccy starts read-only, we do the setup, and if it isn’t worth it, you don’t pay.