Privacy Policy
Self-hosted software does not mean that Sanrish receives no personal information. This policy separates our website and business communications from the data processed inside your TollGate installation.
Effective date: 9 October 2026
1. Who we are and what this covers
TollGate is provided by Sanrish Technologies Private Limited (“Sanrish”, “we”, “us”). Our address is Suite-05A, A-186/187, BSI Business Park, Sector 63, Noida, Uttar Pradesh, India.
This policy covers trytollgate.com, inquiries, demo bookings, sales discussions and support information received by Sanrish. It also explains the boundaries of the current self-hosted Developer edition. A customer’s own notice governs its employees’, users’ and customers’ information inside its installation. A separately agreed managed service or support engagement may involve additional access and processing, which must be described in that agreement.
2. What Sanrish receives
| Interaction | Information and purpose | Providers involved |
|---|---|---|
| Website visits | Your IP address, requested URL and query string, request time, browser/device headers and security-rule results can be processed to deliver the page and detect abuse. Sanrish can view sampled security requests and aggregate traffic/security metrics. If you accept optional analytics, we also receive reports about page views, sessions, approximate location, browser/device type, referring source, campaign parameters and selected website interactions. Do not put secrets or customer information in URLs. | Amazon Web Services: S3 hosts website files, CloudFront delivers them, and AWS WAF inspects requests. CloudWatch provides aggregate metrics. Google Analytics is loaded only after you accept optional analytics. |
| Email inquiries | Your name, email address, company, optional contact details, message, attachments and email routing metadata. We use these to respond, assess requirements, arrange a pilot and keep relevant business correspondence. The email composer on our website prepares a message in your mail application; Sanrish receives it when you send it. | GoDaddy business email powered by Titan, together with the email providers used by senders and recipients. |
| Demo bookings | Your name, email address, chosen appointment, time zone, answers to booking questions and rescheduling/cancellation details. We receive these to arrange and follow up on the meeting. Calendly separately processes visitor/device information on its pages. | Calendly for scheduling and Zoom for meetings. If you add a booking to your own calendar, your calendar provider also processes that event. The booking link opens Calendly; it is not an embedded tracker on our homepage. |
| Zoom meetings | Sanrish participants receive your display name and the audio, video, chat or screen content you choose to share. Zoom processes meeting identifiers, device and connection information and meeting content to provide the call. | Zoom. Recording, transcription or AI Companion features are enabled in our meeting setup. When used, these features may create recordings, transcripts or AI-generated summaries from meeting content. Participants should check the meeting’s recording and AI notices. You may ask the host to disable these features or arrange an email discussion instead. Saved outputs are used for meeting follow-up and support, with access limited to those who need them for that purpose; any sharing with participants is explained for the meeting. |
| Support | Contact details, issue descriptions, product/version information and any logs, screenshots or diagnostic files you choose to share. Such files may contain personal information or customer content. We use them to investigate and resolve the issue and maintain relevant support records. | Our business email service for private support; GitHub for public issues. Remote access or additional file-sharing tools require an agreed support arrangement. |
| GitHub downloads and issues | GitHub handles visits and downloads. Sanrish can see public usernames, profiles, issues, comments and attachments you publish, and repository traffic/download statistics made available by GitHub. A download alone does not send us your installation’s prompts, response history or database. | GitHub. Public issues and attachments are visible to others and may be indexed or copied. |
Only share information needed for your inquiry or issue. Do not email passwords, provider API keys, payment-card details or unredacted production data. Send security reports privately to info@trytollgate.com, not to a public GitHub issue. If sensitive information is necessary for support, agree a suitable restricted transfer method first.
3. Website cookies, analytics and security sampling
Google Analytics is optional. The marketing page does not load Google Analytics or send data to Google until you select “Accept analytics” in the consent banner. If you accept, Google Analytics uses first-party identifiers such as the _ga cookie to distinguish users and sessions and measures page views, campaign attribution and selected actions such as demo-link clicks. We have disabled Google Signals and advertising-personalization signals in the website configuration. Google uses IP addresses during collection to derive approximate location and states that GA4 discards them before the data is logged. You can decline without losing access to the website and can reopen “Analytics choices” from the footer.
Your analytics choice is stored in your browser’s local storage under tollgate.analytics-consent.v1. Choosing “Decline” prevents the Google tag from loading on a new visit; changing an accepted choice to “Decline” sends a denied consent update and removes TollGate’s accessible _ga cookies. Clearing browser storage will cause the banner to appear again. We do not use advertising pixels or session-replay tools, and the Calendly booking page is linked rather than embedded.
Our AWS configuration currently has CloudFront standard access logging, real-time request logging and S3 access logging disabled. WAF sampled-request visibility is enabled, while full WAF request logging is disabled. A sample can include an IP address, URL, headers, timestamp and rule outcome. AWS makes sampled requests available for up to three hours. This is a sampling window, not a promise that all AWS operational records or independently preserved incident evidence are erased after three hours. See AWS WAF documentation.
If you follow a Calendly, GitHub or other external link, that service may use cookies and collect technical information under its own policy. Your browser may send a referrer when following links.
4. What stays in the customer’s installation
In the standard self-hosted Developer deployment, customer-controlled infrastructure holds configuration, provider credentials, local account records, organization/project/member information, access-key records, budgets, usage and cost records, audit events, unresolved reservations and backups. Conversation features may store prompt and response history in the local database. The customer controls access to that infrastructure and is responsible for its notices, permissions, backups and retention settings.
The self-hosted request path does not pass through a Sanrish-hosted model relay. The bundled signed entitlement is checked locally, without an online licence-check call to Sanrish. Installing this edition does not give Sanrish automatic administrator access to the customer’s server or database.
Information leaves the installation when it is sent to the selected model provider, when the customer configures another external service, or when someone shares it with us for support. Software downloads and dependency registries also process ordinary download metadata. If Sanrish is given support access or a diagnostic export, that information becomes part of the separately agreed support processing; self-hosting is not a claim that we never receive customer information.
5. What goes to OpenAI or Anthropic
For an allowed model request, the installation sends the selected provider the content needed to generate a response: prompts, instructions, relevant conversation history, supported attachments or tool-related content included in the request, model settings and technical request metadata. The provider receives the credential for its own account and sees the installation’s outbound IP address. Responses and usage information return to the installation. This is not a transfer of your entire TollGate database, and an OpenAI request does not automatically go to Anthropic or vice versa.
The released direct OpenAI integration sends store: false. That setting is not a zero-retention guarantee: provider abuse monitoring, caching, safety exceptions and legal requirements can still apply. OpenAI documents default abuse-monitoring retention of up to 30 days with exceptions and additional endpoint/model-specific handling. See its API data controls.
Anthropic describes standard API input/output deletion within 30 days, with exceptions for contractual arrangements, certain services or models, safety enforcement and legal requirements. See its commercial data-retention policy. These descriptions are not a Sanrish retention promise.
Your provider contract, account settings, selected model and applicable provider policy determine provider-side retention, training use and location. A TollGate plan does not automatically provide a zero-data-retention agreement. For a separately scoped Amazon Bedrock deployment, AWS processes the model request under the customer’s AWS configuration and contract; the direct OpenAI/Anthropic description is not a statement that every deployment uses those providers.
6. Why we use and share information
We use the information described above to deliver and secure the website, answer requests, schedule meetings, evaluate and deliver services, troubleshoot issues, maintain relevant business records and meet legal obligations. We do not need production prompts or provider secrets for ordinary sales inquiries.
Information may be available to authorized Sanrish personnel and the relevant service providers named above for those purposes. Disclosure may also be required by law, a valid legal process or the protection of legal rights. Where applicable law requires consent or other conditions for a disclosure or transfer, those requirements apply. This policy is not blanket consent to unrelated processing or to sharing sensitive information.
We do not use an additional CRM, support platform or separate AI assistant for customer correspondence. This does not exclude the Zoom meeting features described above.
7. Retention and deletion
The periods below are our retention schedule, administered through review and deletion procedures; they are not a claim that automatic deletion is enabled in every service. Different records have different lifecycles. The customer’s local database, Sanrish’s business records and provider-held API data are separate. Deleting information from one does not automatically delete the others.
| Record | Retention position |
|---|---|
| Website request samples | AWS WAF makes samples available for up to three hours. Current full website request logging is disabled. Incident evidence deliberately preserved by Sanrish requires separate, limited retention. |
| Optional website analytics | Google Analytics event and user-level data follows the retention setting configured for the TollGate GA4 property. Aggregated reports may remain after that period. You can withdraw future analytics consent through the website footer; this does not automatically erase reports already created. Contact us to make an applicable deletion request. |
| Inquiry and booking records | Our retention schedule is to delete or anonymize inactive records 12 months after the last substantive contact, unless part of an active customer relationship or a documented legal need. |
| Closed support correspondence | Our retention schedule is to retain for 24 months after case closure for service continuity and dispute handling, then delete or anonymize unless a documented obligation requires longer. |
| Support diagnostic attachments | Our retention schedule is to delete working copies within 30 days after resolution, unless the customer agrees a longer investigation period or legal preservation is required. Apply this to mailbox and file copies, not only the support view. |
| Zoom meeting records | Zoom retains service records under its own applicable lifecycle. Our schedule is to delete Sanrish-controlled recordings, transcripts and AI summaries within 30 days after the meeting, unless an ongoing support case, agreed engagement or legal preservation requires longer. Necessary follow-up correspondence follows the inquiry or support schedule above. A meeting ending does not erase saved records, and copies held by participants are outside our control. |
| Contracts, invoices, disputes and security investigations | Retain the necessary records for the relevant contractual, accounting or legal purpose. We limit retention to the period required for that purpose or by applicable law, and review continuing need when the matter closes. |
| Public GitHub issues | Remain visible until removed or edited through GitHub. We can assist with reports on our repositories, but cannot guarantee deletion of copies, forks, search caches or another person’s records. |
| Customer installation and backups | Controlled by the customer. The seven-day searchable window does not purge stored records or backups. |
| Provider operational records and backups | Subject to the relevant service contract and provider lifecycle. Removal from an active account may not immediately remove provider backups, security records or copies held by other participants. Their lifecycle is governed by the applicable provider terms and legal obligations. |
Deletion requests are reviewed against the purpose of the record, applicable duties and others’ rights. Where limited records must be retained, we will explain the reason where permitted. A backup may retain information until its scheduled expiry; we will not describe removal from an active inbox as immediate erasure of all copies.
8. Location and safeguards
The website’s origin is hosted in AWS’s Mumbai region; CloudFront and other providers operate internationally. That origin location does not mean all processing remains in India. Email, booking, Zoom, GitHub and model-provider processing can occur outside India according to the applicable service arrangements. The customer selects and controls its own deployment and model-provider settings.
The website uses HTTPS and AWS web-application protection. Business email has two-factor authentication enabled. We limit access to shared support information to people who need it to handle the request. Customer administrators remain responsible for security and backups within their installations. No website or self-hosted deployment can guarantee absolute security.
9. Your choices and privacy complaints
You may choose not to provide optional information. If information is necessary to arrange a meeting or investigate an issue, withholding it may limit what we can do. Contact us to request review or correction of information you supplied, request deletion where applicable, withdraw consent for processing based on consent, or raise a privacy concern. We may request proportionate verification without asking for passwords or API keys. For data held only in a customer’s installation, contact that customer’s administrator first.
Grievance contact: Rishit
Sanrish Technologies Private Limited
Suite-05A, A-186/187, BSI Business Park, Sector 63, Noida, Uttar Pradesh, India
info@trytollgate.com
Suggested subject: Privacy / Grievance — TollGate
We will address applicable grievances expeditiously and within one month of receipt under the 2011 SPDI Rules. Any additional rights, remedies and deadlines apply as required by the law in force. The Digital Personal Data Protection framework has phased commencement; this policy does not treat all future provisions as already effective or displace existing applicable Indian privacy obligations.
10. Changes to this policy
We will publish an updated date when this policy changes. Material new processing, providers or purposes will be described before they are introduced, with additional notice or consent where required.
Provider notices and legal references
AWS privacy notice · AWS customer-data FAQ · Google privacy policy · Google Analytics data collection · GoDaddy privacy notice · Calendly privacy notice · Zoom privacy statement · Zoom retention standard · GitHub privacy statement
2011 SPDI Rules — India Code · DPDP commencement notification — MeitY