Before rolling out TicNote or any meeting recorder in a Gulf enterprise, freeze invite disclosure, a start-of-meeting consent script, stop-on-objection rules, an access and retention list, and written vendor answers on where audio goes — then run a short privacy test on real meetings with guests. This is an operating protocol, not a PDPL opinion.
This page deepens Week 0 of the live Gulf pilot. It does not rewrite the two-week scorecard. It is not legal counsel. It does not rank hardware and does not run checkout.
Why hardware needs the same bar as meeting bots
A calendar bot that joins a call is easy to notice. A table recorder or an open-ear device is not the same signal. Visible capture helps only when the room can see or hear that capture is on. Software note-takers often announce themselves in the participant list. Hardware does not. Treat a physical recorder with the same disclosure, stop, access and retention rules you would demand of a meeting bot. A device on the table is not consent.
Guests cannot assume your internal tool list. If you would not let a silent bot sit in the call without a join notice, do not let a silent recorder sit on the table or in an ear without the same invite language and spoken start. Covert recording is out of scope, as are HR, legal, privileged and confidential-beyond-minutes sessions. Those labels are scope boundaries, not legal advice. If a session might be excluded, do not record it.
Test pack to freeze before first recording
Write the pack in an approved system before any file exists. The pilot owner accepts it. Do not start a quiet trial on a personal account.
- Meeting types in scope, and exclusions (covert recording; HR, legal and privileged sessions).
- Invite disclosure: purpose, expected languages, who will see audio, transcript and summary, and how to object.
- Start-of-meeting script, including a pause after the question.
- Stop-on-objection rule: stop, do not negotiate in the room, do not keep a partial file.
- Late-join rule: repeat the script for anyone who arrives after the start.
- Access list by artifact — audio, transcript, summary — with named people, not departments.
- Retention default, storage location, and who can delete each artifact.
- Written vendor answers on residency, subprocessors, training use, export and deletion.
- Account owner and approved system (not a personal inbox).
- Guest rule: external guests appear on the invite and hear the verbal script.
If any line is blank, the privacy test has not started. Keep confidential minutes out of a first vendor inquiry. See privacy.
Invite language and start-of-meeting script
Use one invite block and one spoken start. State that the session may be recorded to produce internal notes; name the languages you expect (Gulf Arabic and English, including switching); say who will see audio, transcript and summary; and tell people how to object — reply to the invite, or say so at the start. Then pause. The English and Arabic lines below are examples, not official translations. If your company already has approved notice text, use that instead.
Invite example (English). This session may be recorded to produce internal meeting notes in Gulf Arabic and English. Audio, transcript and summary will be available to the host, the designated reviewer and the pilot owner only. To object, reply to this invite or say so at the start. If anyone objects, we will stop recording.
Invite example (Arabic) — example only, not an official translation. قد يُسجَّل هذا الاجتماع لإعداد ملاحظات داخلية بالعربية الخليجية والإنجليزية. الاطلاع على الصوت والنص والملخص مقتصر على المضيف والمراجع وصاحب التجربة. للاعتراض، ردّوا على الدعوة أو قولوا ذلك في البداية. عند أي اعتراض سنتوقف عن التسجيل.
Start-of-meeting script example (English). We are about to record this meeting to produce internal notes. The recording, transcript and summary will be seen by [names or roles]. Anyone may object. I will pause now. If anyone objects, we stop.
Start-of-meeting script example (Arabic) — example only, not an official translation. سنبدأ التسجيل لإعداد ملاحظات داخلية. من يمكنه الاطلاع: [الأسماء أو الأدوار]. من يعترض؟ سأتوقف الآن. عند الاعتراض نتوقف عن التسجيل.
After the pause, if no one has objected, start capture that is visible to the room.
Objection and late-join handling
An objection ends capture for that session. Stop the recorder. Do not continue without using someone’s name. Do not keep a partial file. Offer unrecorded minutes, or reschedule with a different list. Do not negotiate a “just this once” exception in the room.
If someone joins after the start, repeat the script and pause again before their voice is on the file. If they object, stop. External guests must see the disclosure before they join. Do not record guests on a personal account. Remote participants need the same notice as people at the table. Log the outcome — recorded with notice, stopped on objection, or not recorded — in the approved system.
Access, retention, and deletion proof
List who may open audio, transcript and summary. Default to the host, the designated reviewer and the pilot owner. A share link is access; record who holds it. Do not widen the audience because a summary looks useful.
Before the first file exists, set how long each artifact is kept, where it lives, and who can delete it. Use a short default that still covers the test window. Write the deletion path. “We will delete it later” is not a retention default.
Prove deletion on one sample before you call the pack complete. If the vendor cannot show that audio, transcript and summary can be removed, do not roll out devices on that stack. Personal drives and unnamed shared folders fail the test even when the invite language was correct.
Vendor questions before you capture
Ask these as procurement questions, not as a PDPL interpretation. Require written answers. If an answer is vague, do not start the privacy test on that vendor.
- Residency. Where are audio and text processed and stored? Is a residency option available for the destination you named? Name the region, not a marketing phrase.
- Subprocessors. Who else can see content? List subprocessors that handle audio or text, and whether they are optional.
- Training use. Is customer audio, transcript or summary used to train models? Can you opt out in the contract or admin setting?
- Export. Who can export files, and in what format? Can an account be reassigned when someone leaves?
- Deletion. How is deletion requested and proven for audio, transcript and summary? What remains in backups, and for how long?
Escalate the answers to counsel and the security owner.
Open-ear devices are a special case
Open-ear capture is easier to miss than a recorder on the table. The privacy bar does not drop. If the room cannot see the device, the invite and the spoken start have to do more work. Repeat the script when someone joins. If your policy wants disclosed, visible capture for client guests, do not treat an in-ear form as equivalent to a table device.
This page does not rank SKUs and does not open checkout. Choose form factor only after the privacy pack is frozen. For UAE meetings and lectures, the shop chooser explains table versus open-ear form — not a purchase recommendation from www.cnps.ai: TicNote Lite vs Pods WiFi for UAE meetings and lectures. Confirm destination and listing on shop.cnps.ai before any order. After this test and the two-week pilot pass, compare form factors on AI meeting devices and Equip my team. Purchases complete on shop.cnps.ai.
Pass or fail: ready to roll out devices
Run the pack on real meetings that include at least one session with external guests, if guests are normal work. A tabletop walkthrough is not a pass.
Pass. Every line in the test pack is written and accepted. Invites used the frozen disclosure. Hosts used the script and the pause. An objection ended capture with no partial file kept. Late joiners heard the script again. Access and retention match the list. Deletion was proven on one sample. Vendor answers on residency, subprocessors, training use, export and deletion are in writing. No excluded session was recorded. Open-ear use, if any, had extra spoken disclosure.
Fail. Invite omitted disclosure. Capture started without the pause. Recording continued after an objection. A partial file was kept. A guest was recorded on a personal account. Access widened past the list. Retention or deletion was unwritten. Vendor answers were verbal only. An open-ear device ran without a spoken start.
Ready to roll out devices means this privacy test passed. Hardware waits until the pack holds.
After the privacy test
When the pack passes, run the full bilingual method: Gulf Arabic–English meeting-notes pilot. That page owns the two-week scorecard and owned action items. This page stays the consent and privacy gate.
If you want help freezing the pack — destination, languages, guest mix, or a device shortlist after the workflow passes — contact CNPS or request a quotation. Share country, team size and languages. For hardware after both protocols hold, use Equip my team. This site does not take payment.