Your team’s context. Handled with care.

Membership determines access to a workspace and its channels. Private conversations are restricted to their members. AI requests must be authorized against the conversation being used; an administrator role is not a blanket promise of access to every private message.

• Keep company workspaces separate.
• Invite people only to the conversations they need.
• Review membership when someone changes roles or leaves.

Pulse’s current assistant works with authorized recent channel context. Answers can include source-message links so you can inspect the evidence. It can miss something, misunderstand a conversation, or produce an incorrect answer. A source link is an aid to review, not a guarantee of accuracy.

• Workspace administrators control AI availability.
• AI runs when requested or through an approved scheduled summary.
• Do not treat an AI answer as an automated personnel, legal, or financial decision.

Pulse uses Supabase for authentication, relational data, and permissions; Cloudflare for website and delivery infrastructure; Stripe for payments; Resend for transactional emails; Google for optional basic sign-in; and OpenAI or Cloudflare for configured AI processing. Google sign-in does not grant access to Gmail, Drive, or Calendar. Authorized conversation context is sent for AI processing. This is not an on-device-only or end-to-end encrypted AI service.

• The active AI configuration determines which provider receives the authorized context.
• Do not assume that third-party services share one retention policy.
• See the privacy notice for the current data-handling terms.

Files belong to their conversation. Downloads and previews require authorized access, with supported image and PDF previews in the app. Downloads use short-lived links; a link already issued can remain valid until it expires. A preview does not make an uploaded file trustworthy: use your organisation’s own review process before opening unfamiliar files.

A drafted automation is not an active automation. Review its channel, action, time, and time zone before activation. Workspace permissions and AI limits continue to apply to scheduled execution. Pause routines that no longer serve the team.

Response requests capture explicit commitments and acknowledgements. Timing information needs context: the current elapsed-time metrics use calendar time, not a person’s working hours, holidays, or leave. Pulse does not calculate a universal employee score or make automated disciplinary decisions.

Drafts and unsent attachments can persist on the device across app restarts and workspace changes. They are scoped to their account and conversation. Protect the computer and its user account, especially on a shared device. Persistent local data is not the same thing as a cloud backup.

We do not claim a Pulse-specific SOC 2 or ISO certification, an independent security audit, a guaranteed data-residency region, or an enterprise uptime SLA here. A supplier’s certification does not certify Pulse. Tell us what your organisation requires before adopting the pilot.

For privacy questions, access or deletion requests, and security concerns, contact charles@predictive.company. Include enough context to identify the workspace, but never send passwords, API keys, or private message content in an initial report. We may need to verify your authority before acting.