Your work should feel like your own.

Information you choose to provide

Depending on the feature you use, information may include text, notes, checklists, drawings, prompts, board names, exported board content, account details, collaboration content, voice session participation information, and messages or document links you intentionally submit through Zekazi.

When you sign in, Zekazi processes the account information needed to authenticate you, secure access, maintain your session, and provide account protected features.

Whiteboard content and browser storage

Your board may contain personal, academic, business, or other information that you choose to place there. Regular board work can be stored in the current browser so the board can continue between visits.

Shared boards also maintain server-side collaboration data so authorized members can access the same board. Export important work when you want an additional portable copy.

Do not place passwords, payment card numbers, private authentication credentials, access tokens, or other highly sensitive secrets on a board unless Zekazi explicitly provides a feature designed for that type of information.

Accounts and authentication

Zekazi supports account access through Google sign-in or an email magic link. Authentication providers may process the information necessary to verify your identity and establish a secure session.

The sign-in connection is separate from the optional Google Docs integration described below. Signing in with Google does not by itself give Zekazi access to your Google Docs.

Shared whiteboards and live collaboration sessions

When you enable collaboration, shared whiteboard content and membership records are stored on our server so authorized members can access the same board. The owner and invited editors can see and change shared board content.

Collaboration codes are stored as cryptographic hashes rather than readable codes. Each code is intended for one signed-in editor, is invalid after successful redemption, and expires after 60 minutes if unused.

For the current free collaboration feature, a live collaboration session begins when the first invited editor successfully joins. A session lasts up to 20 minutes, supports up to 5 people total including the owner, and may be started up to 3 times in each seven-day period. Later editors join the same running session and do not restart its timer.

If collaboration stays inactive with nobody present for 60 minutes, Zekazi may expire editor memberships and unused collaboration codes while keeping the owner's shared board content available.

Zekazi may store limited session and allowance information needed to operate these limits, such as the related board, participants or membership, session start and end times, and allowance-window timing.

Voice collaboration

Voice is optional inside an active live collaboration session. It does not create a separate 20-minute session or a separate weekly allowance.

When you choose to use voice, your browser or device asks for microphone permission. Zekazi does not receive microphone audio unless you grant that permission and join the voice feature.

Live voice audio is carried through realtime communications infrastructure so authorized participants in the same collaboration session can hear one another.

Zekazi stores limited technical and session information needed to connect authorized participants, operate the feature, and enforce collaboration access or usage limits. This can include the related board, session identifier, participant identity used for the voice room, connection state, microphone permission state, and session timing.

Zekazi does not currently provide voice recording as part of the collaboration feature. Voice is intended for live communication. If recording is introduced later, this policy and relevant product notices should be updated before that feature is used.

Zekazi AI

When you intentionally use Zekazi AI, Zekazi may send your prompt, recent conversation context, and relevant whiteboard content to the configured AI service provider so the request can be processed.

AI features are optional. Zekazi validates supported board actions before applying them, but AI output can still be incomplete or wrong and should be reviewed before you rely on it.

Google Docs integration

Connecting Google Docs is optional and uses a separate Google authorization flow. Zekazi requests access that is limited to the Google Drive files you use with Zekazi, together with the account information needed to identify the connected account.

With your authorization, Zekazi can create Google Docs from board text, list Google Docs available to the Zekazi connection, read a Doc you select, and make a supported edit when you explicitly ask Zekazi AI to change that selected document.

Zekazi stores the authorization credentials needed to keep the connection working in encrypted form on the server. Zekazi does not receive your Google password. Google user data is used only to provide the user-facing Zekazi features described in this policy, not for advertising or unrelated purposes.

Notion integration

Connecting Notion is optional. Zekazi uses the permissions you grant through Notion to create a page from board text, show pages available to the connection, read a page you select, and make a supported edit when you explicitly ask Zekazi AI to change that selected page.

Notion authorization credentials are stored encrypted on the server. Zekazi does not receive your Notion password.

Selected external documents and AI

If you choose a Google Doc or Notion page as the active document source, Zekazi remembers that selection until you change or remove it. While a document source is selected, a Zekazi AI request that uses that source may include relevant content from the selected document so the AI can answer, summarize, or prepare a supported edit.

External document content is treated as untrusted data and cannot override Zekazi's system rules. Zekazi restricts destructive document actions and requires an explicit user request before performing supported external document edits.

Technical and security information

Like most web products, Zekazi may process limited technical information required to operate, secure, troubleshoot, and improve the service. This can include browser information, device information, timestamps, request metadata, error logs, and network information such as IP address.

For voice, technical information can also include microphone permission state, audio input device information exposed by the browser, connection state, participant identity used for the voice room, and session timing needed to connect and operate the feature.

How information may be used

• Provide and maintain the whiteboard and related features.
• Authenticate users and protect account access.
• Synchronize authorized shared boards and manage collaboration access.
• Operate live collaboration sessions, optional voice, and current session limits.
• Process actions you request, including AI actions, exports, and connected document workflows.
• Protect the service against abuse, fraud, attacks, and technical failures.
• Diagnose bugs and improve reliability and usability.
• Meet applicable legal obligations when required.

Service providers

Zekazi relies on service providers for functions such as hosting, database infrastructure, authentication, email delivery, AI processing, realtime voice communications, security, and optional integrations. We aim to provide each service only the information reasonably necessary for the feature being used.

External service providers and integrations may have their own terms and privacy practices. Content you create in an external service after an export is also subject to that provider's account controls and retention rules.

Storage and retention

Retention depends on the feature and storage involved. Information may be kept for as long as reasonably necessary to operate the product, maintain an active account or connection, protect the service, meet legal obligations, or complete the purpose for which the information was provided.

Collaboration session and allowance records may be retained as needed to operate the current session limits, investigate technical or security issues, and maintain service integrity. The current voice feature does not intentionally create stored audio recordings.

Authorization records for Google Docs or Notion may remain until the connection is replaced, revoked, deleted, or no longer needed. Revoking access through the external provider prevents future authorized requests, but it does not automatically delete documents or pages that were already created in that external account.

Your choices

You choose what information goes on a board, whether to use Zekazi AI, whether to collaborate, whether to join voice, whether to grant microphone access, whether to connect Google Docs or Notion, which external document is selected for AI, and when to export your work.

You can mute or leave voice, leave a shared board where the product allows it, remove the active document source in Zekazi, and revoke an external provider's authorization through that provider's account controls. For account, privacy, or deletion assistance, contact Zekazi support. Rights available to you may also depend on applicable law.

Children and inappropriate use

Zekazi is not intended to be used in a way that violates applicable law or exposes children or other people to unsafe, exploitative, or unlawful content. Users should follow applicable age, consent, education, recording, communications, and privacy requirements.

Changes to this policy

We may update this Privacy Policy as Zekazi develops. If the way Zekazi uses voice, connected account data, or other sensitive information changes materially, the policy and relevant product notices should be updated before the new use is introduced.

Questions

For privacy questions, account requests, or product support, email support@zekazi.com.