This page explains what personal data we collect on ai.glints.com and in Glimmer, why we collect it, who handles it, and how long we keep it. It also explains how to see, correct or delete your data.
Last updated: 13 November 2026
Who we are
ai.glints.com and Glimmer are run by Glints Singapore Pte Ltd (UEN 201607739W), part of the Glints group. In this page, "we" and "Glints" mean that company.
This page covers ai.glints.com, the Glimmer AI agents we build and run for companies, and the Glimmer apps we offer through app stores. For everything else Glints does, such as the Glints job platform, the main Glints Privacy Policy applies. Where this page says nothing on a topic, the main policy applies.
What we collect on this website
When you visit any page
Our website is hosted by Cloudflare. As on every website, our server receives your IP address and basic details about your browser when you open a page.
Why: to show you the page and keep the site safe.
Who handles it: Cloudflare.
How long we keep it: we do not keep a log of your visit. Cloudflare does not store these details for us.
Most pages also use Google Analytics. The next section, "Cookies and Google Analytics", explains it.
Our event slide pages load fonts from Google and icons from unpkg.com. When you open one of those pages, Google and unpkg.com receive your IP address.
When you ask for a file or a reply by email
Five pages ask for your work email and company name before they give you something:
the staff AI policy builder, which gives you a Word file;
the safe AI check, which gives you the AI plan comparison PDF;
the grant check, which gives you a grant application pack;
the security page, which gives you the security overview PDF;
the Microsoft Copilot course page, where you ask about the course.
We save your email, your company name, the page you were on, and one result from the tool. The result depends on the page: the grant named, the AI plan shown, or the AI plans you ticked. For the course, it is what you need and your team size. Your other answers stay in your browser. We do not see them.
Why: to reply about what you asked for. We may email you about what you asked for, and about our services that relate to it. We will not add you to a newsletter unless you say yes. For the course, we also email you a confirmation and tell our team about your request.
Who handles it: Cloudflare passes the form to our records in Lark, the work app Glints uses. Lark also sends the course confirmation email.
How long we keep it: 24 months after we last contact you.
If our records system is down when you send the form, your email and company name appear in Cloudflare's live error log. Cloudflare does not store that log.
When you book a call
The "Book a call" button opens a Lark booking page inside our site. Lark runs that page. You pick a time and enter your name, your email and any notes you want to add. Lark emails you to confirm. The booking creates a calendar invite in our Lark calendar, and the Glints staff on the call can see it. The booking page shows Lark's own cookie notice and sets Lark's own cookies.
Why: to set up the call you booked.
Who handles it: Lark.
How long we keep it: 24 months after we last contact you.
When you apply for the leadership workshop
The application form is a Lark form. It asks for your full name, work email, company, job title, the workshop dates you want, and your mobile or WhatsApp number if you choose to give it. You tick a box to agree before you send it.
If we offer you a seat, we send you a short questionnaire. It asks about your laptop, whether you can install software, the AI tools you use, and the work task you want to bring to the workshop. We use your answers to plan the exercise you will build at the workshop.
Why: to decide whether the workshop fits you, to contact you about it, and to prepare your session. We may contact you on WhatsApp if you gave us your number.
Who handles it: Lark stores your form and questionnaire. WhatsApp carries our messages if you gave us your number.
How long we keep it: 12 months after your workshop date. If we chat on WhatsApp, we keep those chats for 24 months after we last contact you.
When you pay for a workshop seat
We send you a Stripe payment link by email. You pay by card or PayNow on Stripe's page.
Why: to take payment for your seat.
Who handles it: Stripe.
How long we keep it: 5 years, because the law requires us to keep tax and accounting records for that long.
When you contact us through Microsoft Marketplace
If you click "Contact me" on our Microsoft Marketplace listing, Microsoft sends us the contact details you agreed to share with us there.
Why: to reply to your request about Glimmer.
What we receive: your first and last name, email, phone number, country, company and job title, the offer you asked about, and any note you write.
Who handles it: Microsoft. Your details stay in Microsoft Partner Center, Microsoft's site for its partners. We do not copy them into any other system.
How long we keep it: as long as Microsoft keeps them in Partner Center. We keep no copy.
When we use AI tools on your details
Our team uses Claude, an AI tool from Anthropic, to help with our work. Claude may read the details you sent us through our forms, the booking page, and the workshop application and questionnaire. We use it to prepare replies, calls and your workshop exercise.
Who handles it: Anthropic, under its data protection terms.
How long we keep it: the same period as the details it reads.
What we do not do
We do not sell your data. We do not use advertising trackers on this website.
Cookies and Google Analytics
Google Analytics counts visits to our pages. It records which links you click, the words on the link, and where the link is on the page. When you click a link to another site, it also records the address of that site. It records when someone sends one of our forms, and from which page. Google receives your IP address. Google Analytics does not receive your email, your answers in our tools, or the text of a policy you build. It places cookies in your browser to tell one visit from the next. These cookies are set for the whole glints.com domain.
Why: to see which pages help people, and fix the ones that do not.
Our legal basis: we rely on our legitimate interests to understand how people use the site. The impact on you is low. We do not use this data for advertising, and our reports show totals across all visitors, not single people.
How long we keep it: Google Analytics keeps the detailed record of each visit for 2 months. It keeps the data linked to your browser's cookie for 14 months after your last visit. Totals in our reports stay after that.
Our website's own code does not set other cookies. If you have visited glints.com, your browser may also send cookies that glints.com set. Our website does not read or use them, and the main Glints Privacy Policy covers them. The Lark booking page sets its own cookies when you open it.
Google Analytics is on in this browser.
How to turn it off. Use the "Turn off analytics" switch on this page. It saves your choice in your browser and stops Google Analytics on ai.glints.com. You can also:
install Google's opt-out add-on, which stops Google Analytics on every site;
block or delete cookies in your browser settings.
Our pages and forms still work if you turn off Google Analytics.
Glimmer: data your company puts into it
Glimmer is the set of AI agents we build and run for a company. Each company gets its own copy of Glimmer. It runs in the company's own cloud account, on a server in its office, or on a machine Glints hosts for that company alone. Your documents, chat history, activity log and search index are stored in your company's copy. No other company shares that copy.
Your company decides what goes into Glimmer and what each agent can reach. For the data we handle while we run Glimmer for you, Glints acts as your company's data intermediary under your contract. Your company stays responsible for the personal data in Glimmer, so your company's own privacy policy applies to the people in that data.
What Glimmer records about the people who use it. Glimmer records each person's name and ID in your chat app, and their work email. It records the messages they send to agents, the answers, the actions they approve, the cost of their requests, and when they sign in to the Glimmer console. It also keeps:
recordings of the agent's browser, with the name of the person who asked, and the team and channel;
meeting recordings and voice notes that staff send to an agent, with their transcripts;
what an agent saves to its memory, with every earlier version;
the agent's saved browser sessions, so it stays signed in to the websites it uses.
Your company's agent owners and admins can see this record. Glimmer keeps the activity log and memory history for the period your company's contract with us sets. It keeps browser recordings, meeting recordings, voice notes, transcripts and the agent's saved browser sessions for 90 days, unless your company's contract sets another period.
What Glints does for your company.
Glints sets up Glimmer, runs it and keeps it updated. Named Glints staff reach your copy over a private network (Tailscale) to do this work. When Glimmer runs in your cloud account or your office, your company can switch this access off at any time. On a machine we host, we switch it off when you ask.
Our staff open your data only to set up, fix or update Glimmer.
We protect your company's copy with the controls listed below.
If we find a data breach in your Glimmer, we tell your company without undue delay.
When your contract ends, we delete your company's copy and any backups we hold within 30 days, or hand it over to you.
What leaves your company's Glimmer. Some data has to pass through outside services for Glimmer to work. We name each one in writing before it is switched on.
The AI model. To answer a request, Glimmer sends the question and the parts of your files, records and chat history that the AI needs to answer. This includes screenshots of the pages the agent's browser opens. Glimmer sends these to the AI company your company picked, using your company's own account and key. That AI company works for your company, under your company's own contract with it. Glints does not hold that contract. Your passwords never go to the AI. Whole files stay in your copy unless the AI needs them. Your company chooses the AI company's terms, including how long it keeps your requests.
Speech to text. If your company turns on transcription, meeting recordings and voice notes go to the speech service your company picks. One choice is OpenAI, using your company's own account and key, which handles them in the United States or Europe. Another is your company's own server.
Your chat app. Your chat app (Teams, Slack or Lark) carries the messages between your staff and the agents, under your company's contract with that app.
Systems your company allows. An agent sends data to the outside systems your company allows it to use, such as your email or accounting software.
Websites. When your company turns on web access for an agent, the agent's browser visits websites, and those websites receive the browser's requests. Glimmer logs every site the browser opens.
Using the Glimmer console or watching an agent's browser. We set up a Glints-run Cloudflare service for every Glimmer, unless your company asks for a private connection inside its own network instead. We tell you in writing which one your Glimmer uses. When your staff use the Glimmer console, the Glints-run Cloudflare service carries the traffic between them and your Glimmer. This traffic includes console pages, sign-in links, and passwords your staff type into Connected systems. When someone watches or controls an agent's browser, the same service carries the screen images, typing and sign-ins. It checks who the person is before it passes on any console page or browser view. Cloudflare records each sign-in to this service, with the person's email, IP address and time, and keeps that record for 24 hours. Cloudflare and Glints do not store the pages, screens or typing that pass through the service.
Microsoft Teams messages and change alerts. When Glimmer runs in your company's cloud, Teams messages for your agents go through a message relay in that same cloud, not at Glints. The relay also receives change alerts from Microsoft 365 or Google Drive. It deletes each message and alert once your Glimmer has received it. When Glimmer runs on an office server or on a machine Glints hosts, the relay runs on that same machine, and the Glints-run Cloudflare service carries these messages and alerts to it.
Read more about how Glimmer keeps data safe on our security page.
Data sent outside Singapore
Lark stores our records in Singapore. These services store or handle personal data outside Singapore: Google, Cloudflare, Stripe, Microsoft, WhatsApp (Meta), Tailscale and Anthropic. When we send personal data overseas, we make sure the receiver protects it to a standard comparable to Singapore law.
Our event slide pages also make your browser ask Google Fonts and unpkg.com for files. Those two services receive your IP address. We do not have data protection terms with them.
For Glimmer, the place depends on how your company runs it. If Glimmer runs in your cloud account, you pick the region, and it can be Singapore. If Glints hosts it, it runs in Singapore. The Glints-run Cloudflare service may carry console and browser traffic through servers outside Singapore. Your company also picks the AI company and the speech service, and each may handle data outside Singapore.
How we protect your data
Encrypted connections. Every page and form on ai.glints.com uses HTTPS.
Website forms. The service that saves form entries can only add new entries.
Limited access. Only the AI Transformation team at Glints can open our records in Lark.
Glimmer controls. Glimmer keeps each company's data in its own copy. A separate program stores each system's password and never sends it to the AI. A password that your staff type into the console passes through the Glints-run Cloudflare service on its way to your Glimmer, as described above. Every request, action and approval is logged. Our security controls follow the ISO 27001 framework. Glints is working toward ISO 27001 certification, expected January 2027. The full list of controls is on our security page.
Your choices
You can ask us to:
show you the personal data we hold about you, and how we used it;
correct data that is wrong;
delete your data;
stop using your data, by withdrawing your consent.
To do any of these, email our data protection officer at [email protected]. Tell us which page or service you used, so we can find your data.
We answer a request to see your data within 30 days. If we cannot answer within 30 days, we tell you in writing within those 30 days when we will. Seeing your data and correcting it are free.
We delete your data unless the law requires us to keep it, for example payment records for tax.
If you withdraw your consent, we stop using your data for that purpose within 10 working days. We tell you first if this means we can no longer do something for you, such as keep your workshop seat for you.
Tell us if your details change, so that we keep them up to date.
If your data is inside a company's Glimmer, contact that company first. We help that company find and correct your data. Glimmer cannot yet delete single entries from its activity log and memory history. If your request covers one of those entries, we tell the company, and Glimmer keeps the entry for the period the company's contract sets.
