Privacy Policy
This policy explains how Aadhyant handles information when an institution connects advertising accounts, admissions CRM or optional AI services to Aadhyant Marketing Intelligence.
Last updated:
Who operates the service
Aadhyant operates this service at analytics.aadhyant.co.in for authorized institutional marketing and admissions teams. The customer controls its connected accounts and authorizes processing of its advertising and admissions data. This platform is intended for institutional staff, rather than student applications or children creating personal accounts.
Information we collect and access
- Workspace and user information: names, work email addresses, organization details, roles, account status and access settings supplied during registration or administration.
- Google Ads data: authorized account identifiers and names, currency and timezone, campaign and advertising metadata, and reporting metrics such as impressions, clicks, costs and conversions. An authorization refresh token lets the service retrieve reports without asking you to sign in for every synchronization.
- Meta Ads data: the connecting profile identifier and name, authorized advertising account and campaign information, performance metrics, authorization token and expiry information.
- Admissions CRM data: configured form and field metadata, lead and application identifiers, sources, campaigns, courses, counselor assignments, stages, outcome dates and available call activity or duration information needed for reports. Reporting views and AI evidence are designed to exclude student names, personal email addresses and phone numbers.
- Service records: synchronization status and errors, access and administration records, support correspondence, and questions, answers and supporting report evidence saved when AI Analyst is used. Do not include student contact details or credentials in questions or support messages.
Why we use the information
We use information to provide and secure your workspace, maintain authorized integrations, synchronize selected data, calculate advertising and admissions performance, reconcile coverage, answer permitted analysis questions and provide support. Google Ads data is used to display advertising performance and compare it with the customer's CRM outcomes. It is not used to serve or target advertisements.
Aadhyant's integrations retrieve information for reporting. They do not create, edit or delete campaigns, change advertising budgets or update CRM records. Google controls its authorization wording: the Google Ads scope can permit broader actions than the reporting functions implemented by Aadhyant. Use a Google Ads identity with Read-only account access when appropriate for your institution.
Storage and protection
Reporting data, workspace records and saved analysis are stored in the server-side database. Saved provider tokens and integration secrets are encrypted by the application before storage; they are not returned to university reporting screens or AI report evidence. Workspace and role checks restrict access. Hosting, database and backup services support operation of the platform. These controls reduce risk but do not guarantee immunity from security incidents.
Session cookies authenticate users and remember service state. They support platform operation rather than advertising tracking.
Your choices, disconnection and deletion
You choose which integrations to authorize and which eligible advertising accounts and CRM forms to select. An authorized administrator can disconnect an integration in Connections. You can also remove authorization through Google Account connections or the equivalent Meta account controls.
Disconnection removes saved credentials and selected-account links for that connection; it does not automatically erase historical reports, saved AI conversations or backups. Revocation at the provider prevents further use of that authorization, although saved status may not update until the next check. Reconnection requires authorization again.
Email info@aadhyant.co.in to request access, correction, export or deletion. We verify identity, workspace authority and scope before processing the request. Data is retained while needed for the agreed reporting history and service, security or legal obligations. See our Retention & deletion policy for the criteria and the distinction between disconnection, archive and deletion.
Policy changes
We update this page when our practices change and show the date above. Material changes to Google data use require an updated disclosure and necessary consent before that new use begins. Contact us about your institution's configuration or enabled providers.