Privacy Policy
Effective: 2025
This Privacy Policy explains what information Zact collects, how we use it, and what choices you have when using Zact and connecting third‑party services (like Google Calendar, Google Drive/Docs, Notion, Asana, Jira, and Slack).
1. Overview
Zact is an AI meeting assistant that can join meetings with context, participate in real time, and help carry outcomes into your workspace. To do that, Zact may process meeting context (title/agenda/attendees), content you provide, and data from integrations you choose to connect.
This policy applies to information processed through the Service, including when you connect integrations and when Zact participates in meetings.
2. Who we are
Zact is the data controller for information collected directly through our website and application. When you connect integrations and sync outcomes to your workspace, we process information to provide the Service under these terms and our agreements with you.
3. Information we collect
Information you provide such as name, email, and basic account settings.
Meeting metadata such as meeting title, description/agenda, participants, time, and related links (e.g., conferencing link), as available via your calendar or meeting provider.
Content shared during meetings and/or content you provide to Zact for the purpose of generating actions (e.g., decisions, owners, tasks, updates). This may include text and other media depending on product configuration.
If you connect integrations (e.g., Google Workspace, Notion, Asana, Jira, Slack), Zact may access data necessary to perform the actions you request or enable, such as reading relevant documents or creating tasks/notes where you already work.
Basic usage and diagnostic data (e.g., logs, performance, and error reports) to keep the service reliable and secure.
We may use cookies or similar technologies for essential functionality (e.g., remembering preferences) and, if enabled, analytics to understand usage and improve the Service. See “Cookies & analytics” below.
4. Integrations & permissions
Zact only connects to third‑party services when you authorize it. The exact scopes and permissions shown in the OAuth consent screen (or integration setup) control what Zact can access. Below are common categories of permissions Zact may request depending on the features you enable:
- Access meeting metadata (title, time, attendees, agenda/description)
- Join meetings you opt in to (using the conferencing link)
- Create or update events you request (e.g., follow‑up meetings)
- Create or update notes/documents (e.g., meeting outcomes)
- Read documents you explicitly reference or grant access to
- Create pages/databases for meeting outcomes
- Read/update content you’ve authorized for syncing context and outcomes
- Create tasks/issues with owners and deadlines from meeting decisions
- Update status or add comments you request
- Post meeting outcomes to channels you specify
- Send reminders or notifications configured by you
Google API data usage: if you connect Google services, we use the data strictly to provide the features you request (e.g., reading meeting metadata, creating follow‑ups, writing notes). You can revoke access at any time in your Google account security settings or within Zact settings.
5. How we use information
- Provide and operate Zact (joining meetings, participating, and executing follow‑through)
- Personalize behavior to your preferences (when to speak up, where to sync outcomes)
- Maintain reliability, prevent abuse, and improve security
- Communicate with you about product updates and support requests
6. AI processing
Zact may use machine learning models to understand meeting context, generate suggested decisions, create tasks, and draft updates. Depending on configuration, processing may involve trusted service providers that help run model inference.
You control which meetings Zact joins and which integrations are connected. Where possible, we minimize the data used for processing to what’s necessary to provide the feature.
8. Data retention
We retain data only as long as needed to provide the service, comply with legal obligations, and resolve disputes. Retention periods may vary by feature and plan.
You can typically limit retention by disconnecting integrations and limiting which meetings Zact joins. If you request deletion, we will take steps to delete or de‑identify data as required by applicable law and our contracts.
9. Security
We take security seriously and use safeguards designed to protect your data. For more, see Security.
11. International transfers
Your information may be processed in countries other than where you live, including where our service providers operate. Where required, we use appropriate safeguards for cross‑border transfers.
12. Your choices
- Disconnect integrations at any time through the third‑party provider or Zact settings
- Limit which meetings Zact joins
- Control where outcomes are synced (docs/tasks/channels)
13. Children
The Service is not directed to children. If you believe a child has provided personal information, contact us and we will take appropriate steps to delete it.
14. Changes to this policy
We may update this Privacy Policy from time to time. We will post the updated version and change the effective date above.
15. Contact
Privacy questions? Email hello@usezact.com.