Legal
Privacy Policy
How GrowTricity handles your information, in plain language. Last updated 19 October 2026. Read the GrowTricity Connect Google-data section.
Who we are
GrowTricity provides practical AI training and personal business-assistant services, including GrowTricity Connect. These services are run by Grupo Pounj Software Exports, a GST- and Udyam-registered firm at SCO 34, Sector 33D, Chandigarh 160020, India. If you have any question about your data, email ashish@gpounj.com or message us on WhatsApp at +91 89689 91639.
What we collect, and why
We try to collect as little as possible. In practice:
- What you tell us. When you book a free class, message us on WhatsApp, email us or visit, you may share your name, age, learner type, class choice, phone number, an optional email and whatever you write. We use it to confirm your class, contact you about it and run the course.
- Call-back requests. New demo and enquiry forms also ask whether you currently own or run your own business, its name and type, and one practical business problem. These are your self-reported answers, used to check current intake eligibility and respond to your request. Please do not include customer details. If you leave your name and number for a call back, we keep them with the page you were on and your device's IP address for up to about 13 months, only to call you back and to stop abuse of the form. The franchise enquiry form also asks for your PIN code, your city and a short note about your plan, kept for the same purpose and for the same time.
- Optional WhatsApp lessons and videos. If you separately tick the optional WhatsApp marketing box on the booking form, we record the time, source, copy version and exact wording you accepted. We may then send occasional GrowTricity AI lessons and videos using an approved WhatsApp marketing template. The box starts unchecked, is not required to book, and you can withdraw permission at any time by replying STOP.
- Booking and follow-up. A pending booking carries a one-time code to WhatsApp. When you send it, we record the WhatsApp number that sent it, the chosen class, the confirmation time, the booking status, the reminder-delivery status, and whether you attended, did not attend, or later enrolled. Pending attempts expire after ten minutes and do not reserve a seat.
- The website AI assistant ("Pi"). If you chat with our assistant, your messages are sent to an AI service to write a reply. We keep chat logs for up to about 30 days, with obvious personal details removed, only to improve the assistant. You do not have to give your name to use it.
- Site and campaign analytics. We use Google Analytics to understand visits and booking steps. We keep the landing page, the referring website and campaign labels such as UTM source, medium and campaign with a booking, so we can measure which promotion led to a confirmed, attended or paid student. If you arrive from a Google ad, Google adds a click id (gclid, gbraid or wbraid) to the link; we keep it with your booking for the same reason, so that Google can be told which ad led to a booking. If Meta advertising is active, the Meta Pixel and Conversions API may measure the same steps with deduplicated event IDs. This uses cookies or similar identifiers; it does not change whether you can book.
- Technical logs. Our host keeps standard server logs, such as your IP address and browser, to keep the site secure and reliable.
- Device details on a booking. When you submit a booking we record the IP address and browser of the device you used. This is used only to confirm the booking came from a real device and, when Meta advertising is active, to measure whether an ad led to a real student. We clear both from the booking record after seven days.
GrowTricity Connect and Google user data
GrowTricity Connect is the Google-account connection service for customers of our personal business-assistant service. The Google permission screen may identify the app as Growtricity. This section covers Google information accessed through those connections, including information derived from it. It is separate from course bookings, advertising and the website assistant Pi.
Our use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We use Google data to provide the assistant features you request. We do not sell it or use it for advertising, data brokerage, creditworthiness decisions or training general-purpose AI models.
What we access and why
You choose whether to connect a Google account. Google shows the permissions for your connection before consent. We check the account identity using the permissions provided by that connection. Identity-enabled connections request openid and email; earlier onboarding can read the account email through Drive. The assistant's available actions are limited by both your granted permissions and the tools supported by your setup.
The full-access Google connection requests the following services. It supports individual operations; it does not provide unrestricted account administration or bulk sharing.
- Gmail (
mail.google.com). Read and search messages and relevant message metadata/content, create and update drafts, send a reviewed email, and change or delete supported individual messages. This broad permission also permits immediate permanent deletion of messages you explicitly approve for deletion. Received email bodies cannot be edited by these tools. - Contacts (
contacts). Find contact names, email addresses, phone numbers and related supported fields, and create, update or delete an individual contact you ask the assistant to manage. - Drive (
drive). Search and read files and metadata, and create or change supported files and folders. Moving files to trash, restoring them and approved permanent deletion are supported. This connection can access existing files, rather than only files created or selected for the app. - Sheets (
spreadsheets). Read spreadsheet metadata and cell values; create spreadsheets and update cells or supported tabs for records, trackers and reports you request. - Forms (
forms.bodyandforms.responses.readonly). Read and edit form structure and questions, create a form, and read submitted responses where permitted. These methods do not edit or delete a respondent's submitted answers. - Calendar (
calendar.events). Read event details and create, update or delete supported events, including titles, times, locations, guest addresses and alerts. Event creation and changes are reviewed before approval; guest notifications need separate send approval.
Other existing connections have different permissions. The Calendar-only connection requests verified identity plus calendar.events.readonly and can only read events. Earlier business onboarding requests drive.file, spreadsheets, forms.body, calendar.events, gmail.send and business.manage. Its Drive permission covers app-created or chosen files; Gmail send does not read the inbox; Forms access does not read responses. Business Profile access is for supported profile information and updates when separately available and authorised. An earlier personal assistant connection may use read-only Gmail, Contacts and Drive access. Those connections do not gain full-access permissions just because this policy describes them.
Your requests and approvals
Connecting an account does not instruct the assistant to send a message or make every possible change. For the full-access Google connection, the assistant shows the proposed record and action for your review. Changes need your approval after that preview. Email sends, guest notifications and deletions require the separate typed approval shown in your chat. Requests to draft are not requests to send. Other assistants follow the working scope and approval rules agreed during their setup.
Where data and authorisation are stored
A separate VM is assigned to each customer's assistant during setup. The private connection link identifies the intended Google account and assistant; the web handoff is encrypted for that assistant's registered key. Other customers are not authorised to claim that handoff. Separate VMs do not mean every processing step stays on that VM: the onboarding service, configured AI provider, WhatsApp and private memory can process data as described below. We explain who operates your VM and any authorised support access during setup.
- Google source records. Your original emails, contacts, files, forms, spreadsheets and events remain in Google. Approved changes are made in that account. Disconnecting the assistant does not erase those records.
- Direct VM setup. Google authorisation is held in protected storage on the assistant's VM. The assistant retrieves relevant content from Google to carry out your request. The model does not receive the OAuth secret or refresh token.
- Web connection handoff. When the web connection flow is used, GrowTricity processes sign-in and renewal and temporarily stores an encrypted authorisation handoff for the intended assistant. Once the assistant acknowledges receipt, that handoff is cleared; connection status, identifiers and token hashes remain. The assistant holds its usable authorisation in protected VM storage.
- Earlier onboarding and private setup intake. These flows hold the Google refresh token encrypted in GrowTricity's onboarding Cloudflare database until handover or a deletion request. The private intake also encrypts your setup answers, optional uploaded recording, Cloudflare token and generated setup exports. Handover to your own account is a separate setup step, not an automatic transfer when you submit the form. Do not assume the onboarding copy has been deleted until we confirm it.
- Assistant memory and operation records. Requests, voice transcripts, replies, previews, results and selected Google content may be retained in the assistant's private memory. The current business-assistant pilot uses a private database in the client's Cloudflare account. Its local operation journal holds hashes, provider IDs and state rather than message or document bodies. Temporary working files may be processed on the VM. The current pilot's conversation memory stores voice transcripts, not the original voice recordings; the separately uploaded private onboarding recording described above is a different storage path.
AI processing, service providers and human access
Relevant requests, conversation context and Google content may be sent to the AI service configured for your assistant, such as OpenAI's ChatGPT/Codex service, to interpret the task and prepare a reply. This is processing by that provider; it is not a promise that data stays only in Google, the VM or Cloudflare. Provider retention and account data controls depend on the service and account used. We explain the configured service and account controls during setup. GrowTricity does not use Google data to train or improve general-purpose AI models.
Google provides the connected APIs. Cloudflare provides web hosting, encrypted onboarding storage and, for the current pilot, private assistant memory. The VM operator processes the data needed to run the assistant. WhatsApp, Meta and the configured WhatsApp gateway carry requests and replies, which can contain the Google information you asked to receive. These providers process the information needed for those features under their own applicable terms. Google-derived content from this connection is not used in our website advertising or booking-conversion measurement.
We do not permit routine staff browsing of your Google content. Human access is limited to your affirmative permission for specific support work, security or abuse investigation, legal obligations, or other uses allowed by Google's Limited Use requirements. Other transfers are limited to providing the user-facing features you consent to, security needs, legal obligations, or a business transfer with the required prior consent. We do not sell Google data or transfer it to advertising platforms or data brokers.
Retention
Business-assistant memory is not the website Pi log. Saved business-assistant conversations, facts, tasks and operation history remain until you request deletion or the service ends and cleanup is completed. There is no automatic 30-day deletion promise for that business memory. Provider records in your Google account remain under your control. AI-provider and WhatsApp copies follow the applicable provider's retention rules.
Usable authorisation remains in the configured credential store while the connection is active, unless revoked or removed. Web handoff content is cleared on successful acknowledgement; status and integrity metadata remain for connection operation and recovery. Earlier onboarding and intake copies remain until the separate handover or deletion is completed. Security/audit records and protected recovery copies may remain for their operational or legal retention period; if an exception prevents full erasure, we explain it when handling your request.
Disconnect, revoke or request deletion
You can remove the app's Google access from Google's third-party connections settings. Removing the whole Growtricity app can revoke several connections together. If you want to stop just one additional connection while keeping the others, contact us first so we can identify it correctly.
Revoking Google access does not delete information already copied into assistant memory or onboarding storage. To request disconnection, deletion of stored Google-derived content, or removal of our stored authorisation copy, email ashish@gpounj.com or WhatsApp +91 89689 91639. We identify the account and requested connection, confirm the scope and report completion. We delete our active stored onboarding authorisation copy within seven days of a verified request. Deleting assistant memory and any retained recovery copies is handled separately, with any legally necessary exception explained. We do not delete your Google files, contacts or events merely because you end the assistant service.
Security and questions
We use encrypted onboarding storage, protected VM credential stores and authenticated connection routes. Access controls and the separation between model requests and credential handling reduce unnecessary exposure; no system is a guarantee against every breach. Never put passwords, one-time codes or API tokens into a chat. Ask ashish@gpounj.com for the access and data-handling details for your specific setup before connecting.
Who we share it with
We do not sell your data. We use a few services to run the site:
- Google. Analytics, Fonts and the embedded map. For business clients who connect a Google account, Google's own APIs carry the work your assistant does in your Drive, Sheets, Forms, Calendar, Gmail and Business Profile, as described above. If you choose “Find address with Google” on the enrolment form, the area or street you search is sent to Google Maps to suggest addresses. You can enter your address manually instead. Your name, phone number and payment reference are not sent with an address search.
- Cloudflare. Hosting, security, website-assistant inference through Workers AI and booking storage for the website, plus the Google connection/onboarding and private assistant storage described above.
- Configured AI providers. Services such as OpenAI may process business-assistant requests and selected Google content as described above. The website assistant and the business assistant have different data paths.
- WhatsApp and Meta, and our WhatsApp gateway. When you choose to message us on WhatsApp, WhatsApp carries the conversation, and our gateway checks the booking code, sends the confirmation and class reminders, and may measure an advertising conversion when Meta advertising is active. Where a conversion is measured, we send Meta a protected (hashed) form of your name, email and phone number, together with the IP address and browser recorded with your booking.
- Resend. Sends the instructor a confirmed-booking email and, if you give an email address, your optional email confirmation.
Each has its own privacy terms. We share only what these services need to work, or what the law requires.
Cookies
The site uses cookies for analytics and, if ads are running, to measure them. You can block or delete cookies in your browser settings. The booking still works, although campaign attribution may be incomplete.
How long we keep it
Pending booking attempts expire after ten minutes and are removed from time to time. We keep confirmed booking, attendance, enrolment and delivery records only as long as reasonably needed for class administration, safety, accounting, legal obligations, campaign measurement and handling a request or dispute. The IP address and browser recorded with a booking are cleared after seven days. Website assistant Pi chat logs are kept for up to about 30 days. Google connection credentials, onboarding material and business-assistant memory follow the separate Google-data retention and deletion details above; they do not inherit the Pi log period. Analytics data follows each analytics provider's configured retention.
Your choices
You can ask what personal information we hold about you, ask for a correction, ask for erasure where we are not legally required to keep it, or raise a grievance by emailing ashish@gpounj.com. If you opted into WhatsApp lessons and videos, reply STOP to any promotional message to withdraw that permission. We handle these requests under India's applicable data-protection law.
Children
This course is for adults aged 24 to 48. We do not knowingly collect information from children.
Changes to this policy
If we change how we handle data, we update this page and the date at the top. This version is dated 19 October 2026.
Questions about your data
Email ashish@gpounj.com or WhatsApp +91 89689 91639. Grupo Pounj Software Exports, SCO 34, Sector 33D, Chandigarh 160020. The course terms are on the terms page.