Privacy Policy

#1. Who we are

Quantalog is operated by DA Orbit (“we”, “us”, “our”). This policy explains what we collect, why, and the choices you have. It applies to:

• Visitors to websites that have installed the Quantalog tracker;
• Customers who create a Quantalog account;
• Respondents who submit a form built with Quantalog; and
• Anyone using quantalog.daorbit.in, including the Orbit assistant on it.

#2. Our role

For analytics collected on a customer's website and for responses to a customer's forms, the customer decides what is collected and why. They are the data controller, and we process that data on their behalf and on their instructions. For account, billing and support information, and for this website, we are the controller.

If you visited a website that uses Quantalog and have a question about it, the owner of that website is the right first contact.

#3. What the tracker collects

When a page running the tracker loads, we receive:

• the page address, the referring address, any UTM campaign parameters and any ad click id in the page address (such as gclid or fbclid);
• the screen size;
• custom events and properties that the website owner has chosen to send; and
• the HTTP request itself, from which we derive the device type, operating system, browser and country.

Customers who measure a mobile or web app through our tracking API send their own identifier for each signed-in user with every event, and we store it with those events. The customer chooses that identifier and is responsible for it.

#4. What the tracker does not collect

• No cookies or localStorage. A random session id, the session's page count, entry page and campaign source are kept in the tab's sessionStorage, which the browser clears when the tab is closed.
• No identifier is created that follows a web visitor across websites or across weeks.
• No keystrokes, form input, mouse movement or session recordings.
• No names, email addresses or other directly identifying information.

Our terms forbid customers from sending personal data through custom event properties.

#5. How visitors are counted

A web visitor is a SHA-256 hash of the IP address, the user agent, the website's site key and the current calendar week. Because the week is part of the hash, the same person appears as a new visitor the following week, and the same person on two different websites produces two unrelated hashes. We store only the hash, never the IP address, and we never use the hash to identify anyone.

#6. Information about customers

When you create and use an account, we hold:

• Account details — your name, email address and a one-way (bcrypt) hash of your password. If you sign in with Google, we also keep your Google account id and profile picture address (see section 8).
• Workspace configuration — the workspaces, sites, goals, reports and settings you create.
• Mobile number — only if you add one to receive reports on WhatsApp.
• Billing records — the plan or pack bought, the amount, currency, any coupon, the receipt number and the Razorpay payment reference. Card and bank details are entered in Razorpay's own window; we never see or store them.
• Support correspondence — the messages you send us and our replies.
• Technical logs — standard server logs used to keep the service secure and working.

#7. Connected accounts

Some features ask you to connect an account you hold with another service. You choose whether to connect each one, and you can disconnect it at any time.

Google accounts, including Google Calendar, Search Console and Business Profile, are covered in section 8.

#LinkedIn and Instagram

To schedule posts on LinkedIn (and on Instagram, where available to your account), we store the access token the network grants, the account name and picture, and a record of what was published. The token is used only to publish posts you compose and schedule yourself. We never publish anything you did not create or approve.

Access tokens are encrypted at rest. Disconnecting an account deletes its stored token immediately.

#8. Google API Services and Google Calendar data

Some features let you connect a Google account. Each connection is optional, is started by you, and is used only for the feature you connected it for. This section explains what we access from Google, why, how long we keep it and how to remove it.

#Google Calendar for booking forms

A Quantalog form can include a booking field that lets the people filling it in pick a time with you. A member of your workspace can connect a Google Calendar under Lead capture → Apps → Google Calendar. The connection belongs to that workspace, and every booking field in it can use it. Booking forms work without it; connecting is optional.

#What we access and why

When you connect, Google asks you to allow the following. Each permission maps to one feature:

• Your email address (openid, email) — to show which Google account is connected to the workspace.
• The list of your calendars (calendar.calendarlist.readonly) — calendar names, ids, which one is primary and whether you can add events to it, so you can choose where bookings go and which calendars to check for conflicts.
• Availability on your calendars (calendar.events.freebusy) — only the start and end of busy periods on the calendars you choose. We never receive event titles, descriptions, guests or locations through this permission.
• Events on your calendars (calendar.events) — to create an event for each confirmed booking in the calendar you pick, with a Google Meet link if you turn that on, and to delete that event when you delete the entry. We do not read, change or delete any event that Quantalog did not create.

Workspaces that connected before October 2026 granted the broader calendar.readonly permission instead of the calendar list and availability permissions. We use it only for the same two purposes. Disconnecting and connecting again replaces it with the narrower permissions above.

#How the Calendar features work

• Availability. When someone opens a booking form, our server asks Google for busy periods on the calendars you chose, for the dates being shown, and hides any time that overlaps. Respondents see only the open times, never your events or why a time is taken. Busy periods are held in server memory for at most 30 seconds so the same request is not repeated, are checked again just before a booking is confirmed, and are never written to our database.
• Event creation. When a booking is confirmed, we create an event in the calendar you picked. Its title and description come from your booking settings and include the respondent's answers. If the form has an email field, the respondent is added as a guest and Google sends them the invitation.
• Google Meet links. If Add a Google Meet link is on, Google creates a Meet conference for the event. We show the Meet link on the thank-you screen, in notification emails and in the entry.
• Synchronisation. Sync is one-way. We add and remove only the events we create. We do not import your events or watch your calendars for changes. Deleting an entry in Quantalog deletes its event, and Google notifies the guests.

#What we store, where and for how long

Google Calendar data is stored in our database, hosted on MongoDB Atlas. We keep only the following:

• The connection — the Google account's email address, the access and refresh tokens (encrypted), when the access token expires, the permissions granted, which member connected it and whether it is active. It is kept until you disconnect, the workspace is deleted or your account is closed. If Google tells us access was revoked, we delete both tokens straight away and keep only the email address and an “expired” status, so the dashboard can ask you to reconnect. That remaining record is deleted when you remove the connection or delete the workspace.
• Booking settings — the ids of the calendars you chose, saved in the form.
• Each booking we add to Google Calendar — the calendar id and event id, so we can remove the event later, and the Meet link and event link, saved with the entry. These are kept as long as the entry is, which is until you delete it, the form or the workspace.

We do not store the contents of your calendar events, your busy periods or your list of calendars. The list is fetched from Google each time you open the settings that show it.

#Who can see it and whether it is shared

• The connected email address and your calendar names are visible to members of the workspace in Apps and in the booking field settings.
• The respondent sees the booked time and, if enabled, the Meet link. Notification emails containing the booking and Meet link are sent through our email delivery providers.
• Our hosting providers (MongoDB Atlas and Vercel) store and process the data on our behalf. We may also disclose it where the law requires.

We do not sell Google user data, use it for advertising or to build profiles, or transfer it to data brokers. We do not use it to develop, improve or train generalised AI or machine learning models, and it is not sent to Orbit or any other AI feature. Our staff do not read it, except with your explicit permission for a support request, where it is necessary for security purposes such as investigating abuse, or to comply with the law.

#How Google data is protected

• Access and refresh tokens are encrypted at rest with AES-256-GCM. The key is kept in our server environment, separate from the database.
• Tokens stay on our servers. They are never sent to your browser, placed in a URL or written to our logs, and they are left out of database reads unless a request to Google needs them.
• Requests to Google go directly from our servers over TLS. Each connection attempt carries a signed state value that expires after 10 minutes and ties the result to your workspace.
• Access to production systems is limited to the people who need it.

#Disconnecting and revoking access

• In Quantalog: open Lead capture → Apps → Google Calendar and choose Disconnect. We ask Google to revoke the token, then delete the stored tokens and the connection record immediately.
• In your Google Account: remove Quantalog under Third-party apps & services. The next time we try to use the connection, Google refuses it, we delete the tokens and the dashboard shows the connection as expired.

After you disconnect, we no longer access your Google Calendar. Busy-time checks and new events stop, and booking forms keep working using only the weekly hours you set. Events we already created stay in your Google Calendar, where you control them. The event ids, Meet links and event links saved with existing entries stay until you delete those entries. Deleting an entry after disconnecting no longer removes its Google event, so delete it in Google Calendar yourself.

#Deleting Google data and contacting us

Deleting an entry deletes its saved Meet and event links. Deleting a workspace, or your account under Settings → Security, deletes the Google connection, revokes its tokens with Google and deletes every booking record. You can also email daorbit2k25@gmail.com to ask us to delete the Google data associated with your account or workspace, or with any other question about it. We will confirm when it is done.

#Other Google services

The same Limited Use commitment applies to these optional features:

• Sign in with Google (openid, email, profile) — we receive your name, email address, Google account id and profile picture address, and use them only to create your account and sign you in.
• Google Search Console (webmasters) — we show clicks, impressions, rankings, index status and sitemaps for the properties you link. The only change we make to your Search Console account is submitting or removing a sitemap, and only when you ask us to. We store the connected email address, encrypted tokens, the properties you link and cached reports, which expire automatically.
• Google Business Profile (business.manage) — we read your locations and reviews to show them in the dashboard. We store the connected email address, encrypted tokens, each location's name, address and rating summary, and its reviews as Google returns them, including the reviewer's public name and photo, the rating, the text and any reply. We do not post replies or change your profile.

Disconnecting Search Console or Business Profile in Quantalog revokes the token with Google and deletes the tokens and all the data listed for that service.

#9. Forms and respondents

When someone submits a form built with Quantalog, the answers are stored for the customer who owns that form, alongside the analytics that led to the submission. If the form takes a payment, it is processed through the form owner's own payment account, and we store the payment reference, status, method and the contact details the payment provider returns. A form owner can also choose to record each respondent's IP address.

If a form has a booking field, we store the time booked. When the form owner has connected Google Calendar, the respondent's answers are added to an event in the owner's calendar and, if they gave an email address, Google sends them an invitation, as described in section 8.

Form owners may configure notification emails and webhooks. A webhook sends each submission to an address the form owner chooses, and what happens there is governed by the form owner.

#10. Orbit, our AI assistant

Questions you ask Orbit are sent to a third-party AI model to generate an answer. Orbit currently uses Meta's Llama models hosted on Cloudflare Workers AI; when more than one model is available, the one that answers is chosen automatically.

• On this website, each question is sent together with the text of the page you are viewing so Orbit can answer in context. These conversations are not saved to an account and are gone when you close the tab.
• In the dashboard, conversations are saved to your workspace so you can return to them. They are visible to members of that workspace and you can delete any of them.

We do not use your questions or answers to train AI models. Please don't share sensitive personal information with Orbit.

#11. This website

This website measures its own traffic with Quantalog, so it sets no cookies either. If you use our contact form, we use what you send only to reply to you and keep it with our support correspondence.

#12. How we use information

• to provide, maintain and improve the service;
• to process payments and issue receipts;
• to send service messages — receipts, scheduled reports and notice of material changes;
• to respond to support requests;
• to detect and prevent abuse, fraud and security incidents; and
• to meet our legal obligations.

We do not use your information for advertising, and we do not sell or rent it to anyone.

#13. Legal bases

Where laws such as the EU and UK GDPR or India's Digital Personal Data Protection Act, 2023 apply, we rely on: performing our contract with you; our legitimate interests in running a secure, reliable service; your consent, where you connect a third-party account or choose to receive something optional; and compliance with legal obligations such as tax and accounting rules.

#14. Service providers

We use a small number of trusted providers to run Quantalog:

• MongoDB Atlas — database hosting.
• Vercel and Cloudflare — hosting, content delivery and network security; Cloudflare Workers AI also runs Orbit.
• Cloudinary — storage for images you upload.
• Razorpay — payment processing.
• Email and WhatsApp delivery providers — to send receipts, reports and notifications.
• Google, LinkedIn and Meta — only when you connect an account with them. Google data is handled as described in section 8.

Each provider receives only what it needs to perform its service. We may also disclose information where the law requires it, and only to the extent required.

#15. International transfers

Our providers may process data in countries other than your own, including India and the United States. Where data leaves the EU, UK or another region with transfer rules, we rely on appropriate safeguards such as standard contractual clauses offered by our providers.

#16. Retention and deletion

• Analytics events are kept for 25 months on every plan, then deleted automatically. Your plan sets how far back the dashboard can show within that window.
• Form data is kept until the customer deletes it, deletes the workspace or closes their account.
• Account data is kept while your account is open. You can delete your account yourself under Settings, then Security. That deletes it together with every workspace you own, their sites, analytics, forms and submissions, media files, and any connected account tokens, which are also revoked with the provider.
• Google connections are kept until you disconnect them. What is kept, and what is deleted when you disconnect, is set out in section 8.
• Billing records are kept for as long as tax and accounting law requires, even after an account is closed.

You can export or permanently delete a site's data at any time from the dashboard.

#17. Security

Data is encrypted in transit with TLS. Passwords are stored only as one-way hashes, access tokens for Google accounts are encrypted at rest with AES-256-GCM, access tokens for other connected accounts are encrypted at rest, and access to production systems is limited to the people who need it. No system is perfectly secure; if we become aware of a breach affecting your data, we will notify you and the relevant authorities as the law requires.

#18. Your rights

Depending on where you live, you may have the right to access, correct, export or delete your personal data, to object to or restrict certain processing, to withdraw consent, and to complain to a data protection authority.

Customers can exercise most of these directly in the dashboard, or by emailing daorbit2k25@gmail.com. Because the tracker does not store identifying data, we are generally unable to find records relating to a specific visitor; the website owner is the right contact for questions about their site.

#19. Children

Quantalog is a business service and is not intended for anyone under 18. We do not knowingly collect personal data from children.

#20. Changes to this policy

We may update this policy as the product or the law changes. The date at the top shows the latest version. If a change materially affects how we handle your data, we will email account holders before it takes effect.

#21. Contact

For any privacy question or request, including a request to delete data received from Google, email daorbit2k25@gmail.com. See also our Terms of Service.