Security and trust

Keep customer-facing changes under your control

BlipLogger is designed so AI can help with drafts and setup while important actions still require review.

You decide what gets published or sent.

Trust boundaries

BlipLogger keeps important actions behind clear review and access controls.

  • You control what gets published or sent to customers.
  • AI can help with drafts and setup, but it cannot take over billing, security, or account administration.
  • Access stays tied to the project and permissions you choose.
  • If a protected action is not allowed, it does not quietly continue.

What drafting help can do

AI can help prepare and explain work without taking customer-facing action on its own.

  • Prepare release drafts and summaries.
  • Explain setup and installation steps.
  • Help organize project information for review.
  • Suggest wording without publishing or sending anything.

What requires approval

Important customer-facing and account changes stay under human control.

  • Publishing or sending customer-facing changes.
  • Billing, security, access, and other sensitive account changes.
  • Destructive actions that could remove or replace important data.
  • Any action that BlipLogger marks as requiring review.

Available today

BlipLogger provides hosted changelogs and in-product update tools with clear review controls.

  • Hosted changelog pages for published updates.
  • An embeddable What's New widget.
  • Release pages with supported images, GIFs, and video embeds.
  • Themes, layouts, and branding controls for supported public surfaces.
Advanced details

Deeper security, access, and implementation notes for teams that need them.

Approval and access boundaries

BlipLogger's MCP server is live at /api/mcp. Authenticated tools require scoped access. Publishing, billing, security, RBAC, and admin operations stay under owner-approved product controls.

  • Release communication: approval-aware workflow support exists, but customer-facing execution still requires human review.
  • Product updates: approval-aware workflow support exists, but customer-facing execution still requires human review.
  • Customer transparency: approval-aware workflow support exists, but customer-facing execution still requires human review.
  • Public changelogs: approval-aware workflow support exists, but customer-facing execution still requires human review.
  • Approval-aware drafting: approval-aware workflow support exists, but customer-facing execution still requires human review.
  • AI-assisted communication operations: approval-aware workflow support exists, but customer-facing execution still requires human review.

How BlipLogger handles customer-facing changes

Customer-facing changes remain tied to controlled pathways, explicit review, and fail-closed capability disclosure.

  • Communication activity is designed to stay attributable and audit-friendly where live.
  • Drafting, setup, and trust guidance remain explicit rather than hidden execution behavior.
  • When a capability is not explicitly live, it is treated as unavailable, advisory only, or planned rather than callable.
  • Integration guidance helps teams evaluate setup paths without granting connector execution authority.

For teams that need review and accountability

Project-scoped access, human review, and clear responsibility stay visible across drafting, setup, ecosystem guidance, and delivery readiness.

  • Project-scoped access and tenant isolation remain core product truths.
  • Authenticated and server-authoritative checks remain the trust boundary for protected actions.
  • This trust layer is meant to help technical buyers evaluate approval boundaries, audit-friendly behavior, and authority limits without overclaiming compliance.
  • Project-scoped access, explicit review steps, and fail-closed capability disclosure are product truths today.

Authentication and session handling

Authentication decisions and protected actions are handled on the server. Account access is tied to configured sign-in methods, and session-related controls remain server-authoritative rather than delegated to client-side UI state.

Validation and tenant boundaries

BlipLogger validates requests on the server and limits access to project data based on authenticated account context. Setup guidance does not mean autonomous install. Ecosystem positioning does not mean live integration or execution authority.

Hosting and service providers

BlipLogger is hosted on Vercel, uses Neon for database infrastructure, relies on Stripe for payment processing, and uses NextAuth as part of the authentication layer.

Vulnerability reporting

If you believe you have found a security issue, email support@bliplogger.com. Please include reproduction details, affected routes or features, and any relevant account or project context. Business address available upon request.

What is not being claimed

This page explains product trust boundaries. It does not claim compliance certification, legal certification, or enterprise audit certification that is not already implemented and verified.

  • No SOC 2, HIPAA, ISO, GDPR certification, or enterprise compliance certification claims are being made here.
  • Trust signaling explains product boundaries without implying legal or certification status.