Last updated: November 12, 2026
This policy explains how Chiefscope collects, uses, shares and protects your personal and company data. Chiefscope is accessible via the mobile app and web panel; this policy covers all of them. Data controller: Londist Ltd, 276 Chase Road, Suite 7-0384 Lonsto House, London, England, N14 6HA — support@chiefscope.com
Account information (name, email). If you sign in with Google or Apple, those providers share your name and email with us to verify your identity; we never see your password. Messages you write to your assistant and the content you create (tasks, meetings, notes, reminders, documents you add to the knowledge base). Audio, if you use meeting recording or the live voice assistant (Scope); invoice/document photos you upload for analysis. Operational data from the business systems you connect (ERP, bank accounts, e-invoicing/ETA, accounting and inventory systems, e-commerce and CRM platforms, Google Calendar, etc.) needed to give you summaries and reports, and the access keys for those systems (stored encrypted). Your device push token, to send notifications in the mobile app. Subscription payments are handled by Stripe on the web, or by the Apple App Store / Google Play from within the mobile app; we never see or store your card details. For in-app purchases, your account ID is shared with our purchase infrastructure (RevenueCat) to verify your subscription status.
To understand your requests and generate content (summaries, reports, newsletters), Chiefscope sends part of your data to a single third-party AI provider — OpenAI: the messages you write, task/work details, company data from the systems you've connected, meeting audio recordings, your live voice assistant conversation, and images you upload. Your passwords, payment card details and integration access keys are never sent to the AI. Under OpenAI's commitment, data sent via the API is not used to train their models; OpenAI retains this data for at most 30 days before deleting it, and processes it mainly on infrastructure in the United States. You're informed and asked to consent within the app before using AI features.
Pseudonym option. When enabled for your company, the names of your recorded customers and suppliers, your team members' names, your company name, email addresses, phone numbers, IBANs and Turkish tax/ID numbers in written content sent to OpenAI are replaced with pseudonyms (for example “Müşteri-3”, Turkish for “Customer-3”) before sending, and the real names are put back before the answer reaches you. This option is off by default. Even when it is on, amounts (unless separately selected), names not recorded in your systems, images and documents, meeting audio recordings and your live voice assistant conversation are not covered.
So you don't have to explain yourself from scratch every time, your assistant extracts and stores a few durable work-related facts from your conversations: your role, what you're responsible for, which tools you use, how you prefer reports to be formatted. This is done only from the messages you write yourself, once a day.
What is never inferred: health, religion or belief, political opinion, union or association membership, ethnic origin, sex life, biometric data and criminal convictions. These are special categories of personal data under Turkish data protection law (KVKK) and EU law; they are blocked by a technical filter on the write path, not by an instruction given to the AI — so even if such a statement were produced, it would not be stored. One-off events (today's meeting) and details about your private life are not stored either.
You can see it and delete it. Ask your assistant "what do you know about me" and it lists every stored item verbatim. Say "forget that" to remove a single item, or ask it to delete everything it knows about you. A deleted item is not learned again — it will not reappear the next day.
This information is personal to you. In a company account, your colleagues and your manager cannot see your profile; access is restricted to you at the database level.
You can add your assistant to an online meeting (Google Meet, Zoom, Microsoft Teams) so it joins and records. This is a per-meeting decision: the assistant never joins anything on its own — only the meetings you explicitly add. You can remove a meeting from that list at any time.
When it joins, it appears in the participant list as "Scope" and, as soon as it joins, posts in the meeting chat that it is an AI assistant and is recording, so everyone in the meeting can see that a recording assistant is present. Making sure the other participants are aware of the recording is the responsibility of the user who added it.
The joining and recording itself is carried out by Recall.ai; the audio is processed on that provider's European Union (Frankfurt) infrastructure and deleted after 24 hours. We only need the recording long enough to transcribe it; transcription happens through our own path (OpenAI) described above. The resulting meeting notes, summary and decisions are stored in your account and can be deleted like any other data.
You can also add the AI experts you created to an online meeting; this too is a per-meeting decision. Each selected expert joins under its own name as a separate participant and, as soon as it joins, posts in the meeting chat that it is AI, on whose behalf it is listening live, and that anyone can ask for it to be removed.
An expert does not record the meeting or take notes. What is said is transcribed live (Recall.ai, European Union infrastructure; the provider's copy is deleted after 1 hour) and messages in the meeting chat are read. When a sentence or chat message starts with the expert's name, the question, the last few minutes of the meeting and the expert's dossier are sent to OpenAI to write the answer; in longer meetings a short running summary is also kept with OpenAI. The answer is posted only in that meeting's chat; the expert sends nothing outside the meeting. The transcript it heard and the answers it gave are stored in the account of the person who added it, so it stays consistent in later meetings, and can be deleted like any other data.
Meeting recording: audio is first sent to Chiefscope's servers to be transcribed, then forwarded to OpenAI; the audio file itself is not stored permanently. Live voice assistant (Scope): your voice streams directly between your phone and OpenAI over a secure connection (WebRTC) — Chiefscope's servers never see this audio, though it still reaches OpenAI. Microphone access is only requested when you use these features; you can revoke the permission at any time from your device settings.
You choose what to connect, and each connection asks for your consent on Google's own screen. Google Calendar: we read your events and create the events you ask for, to show your schedule and prepare your meetings. Gmail: we read your messages to show your inbox and detect replies to follow-ups you started, and we send a message only after you approve it. Google Drive: we read the files you connect so the assistant can answer from them. You can disconnect at any time in Settings, and access ends then.
Chiefscope's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We use this data only to provide features you can see in the product. We do not sell it, do not use it for advertising, and do not use it to train generalized AI models. Text may be processed by the AI providers listed below only to produce the feature you asked for.
If you connect your Google Calendar, only event read/create permission is used; it is never shared with third parties or used for advertising. From other business systems you connect (ERP, bank accounts, e-invoicing/ETA, accounting and inventory systems, e-commerce and CRM platforms, etc.) we only read the data needed to give you summaries, reports and reminders; more systems may be added in the future under the same principles. Your access keys and credentials are stored encrypted. You can remove any connection from the panel at any time.
Every account's data is isolated at the database level (via row-level security); one account can never access another account's data. This isolation is verified with regular automated tests. Data is encrypted in transit with TLS. Integration access keys and credentials are additionally stored encrypted at the application level in the database. Your data is hosted with our cloud infrastructure providers; some hosting and AI processing steps may take place outside your country. The provider list below covers all such transfers.
We rely on the following providers to run the service. Each one only processes the data its function requires:
This list is kept current. New providers are published here when added.
When you tap "Delete Account" in the app, all your data — tasks, messages, meeting notes, memory, uploaded files and login credentials — is permanently and irreversibly deleted. If you're part of a company account with other active team members, this only deletes your own membership; shared company data is preserved. To delete an entire company's data, email support@chiefscope.com. You always have the right to access, correct, or request deletion of your data.
Chiefscope is a business/productivity service and is not directed at users under 18. We do not knowingly collect data from anyone under 18.
For questions and requests: support@chiefscope.com