Privacy Policy
Jameela takes notes of meetings. This page explains what data we collect, why, and how you control it.
Who we are
The provider and data controller of Jameela is Jameela.id (https://jameela.id). For any question, use the support form.
What Jameela does
Jameela is an AI meeting recorder. The bot "Jameela (Pencatat Rapat)" joins Google Meet, records audio and the video of the bot's view, and creates an Indonesian transcript, a summary, and action items. The bot sends one chat message in the meeting to say that the meeting is recorded.
Today Jameela is for invited teams (access by invitation) and a public demo account.
Data we collect
- Google account profile: name, email, photo, and account ID, when you sign in.
- Calendar data, only if you connect your calendar (read-only scope): event title, time, attendees (name and email), meeting link, RSVP status, and the list of calendars.
- Meeting recordings: audio and video.
- Meeting results: transcript, speaker names, meeting events (join, leave, speak, screen share), summary, and action items.
- AI app connections: app name and the time you gave permission. Tokens are stored as hashes.
- Personal access tokens: only the hash is stored.
- Technical logs: without meeting content.
- Access request and support forms: the email and message you send.
How we use data
We use data to run the service: the bot joining meetings, transcripts, summaries, search, and sending to the AI apps you connect.
- We do not sell your data.
- We do not use your data to train AI models.
Third-party processors
| Party | Purpose |
|---|---|
| Cloudflare | Hosting, database, file storage, and queues. |
| Groq | Audio transcription and summary generation. Data is sent to Groq for processing. |
| Sign-in, Google Calendar API, and Google Meet. | |
| Contabo | Bot server in Singapore. |
If you connect Jameela to an AI client (Claude, ChatGPT, Cursor, and others) through MCP, the data that client requests is sent to that client and is subject to that client's policy. See the MCP documentation.
Google user data
Jameela.id's use and transfer of information received from Google APIs adheres to theGoogle API Services User Data Policy, including the Limited Use requirements.
How long we keep data
| Data | Retention |
|---|---|
| Audio and video | 30 days, then deleted automatically. |
| Transcripts, summaries, and action items | Until you delete the meeting or your account is closed. |
| Calendar cache | 7 days after the event ends. Deleted right away when you disconnect the calendar. |
| Demo account and all its data | 7 days. |
| OAuth access tokens | 1 hour. Refresh tokens: 30 days. |
| Technical logs | At most 7 days. |
Your rights
- Delete a meeting from the app, or with the
delete_meetingtool in an AI client. - Disconnect your calendar at any time.
- Revoke an AI app's access in Settings.
- Ask for a copy or deletion of your data through the support form.
Security
- All traffic uses HTTPS.
- Recordings are kept in private storage.
- Tokens are stored as hashes.
- Google refresh tokens are encrypted with AES-GCM.
Age limit
Jameela is not for children under 18.
Changes to this policy
This policy is effective from November 4, 2026. If we change it, the new version and its effective date appear on this page.
Contact
Send questions through the support form.