Why We Log

mssg.it is built around a simple idea:

Good communication depends on restraint, not volume.

Because of that, we approach logging differently from most messaging tools.

This page explains what we log, where it lives, and when—if ever—it is shared.

Logging Is Local by Default

All logging in mssg.it happens locally, inside your own browser installation.

That means:

  • Logs live on your device
  • Logs are tied to your browser and extension install
  • Logs are not sent to our servers
  • Logs disappear if you uninstall or clear browser data

There is no background reporting and no central activity database.

What We Log

We log only what is necessary to keep the system safe and explainable.

1. System Errors and Health Signals

These help detect when something is broken or unsafe, such as:

  • WhatsApp being unavailable
  • Adapter incompatibilities
  • Message dispatch failures
  • Storage or lifecycle errors

This allows the system to fail safely instead of sending messages unexpectedly.

2. Safety and Guardrail Activity

We record when safety rules are activated, for example:

  • Messages blocked due to rate limits
  • Messages blocked due to "do not disturb" states
  • Broadcasts paused automatically by the system

These logs exist to ensure restraint is working as designed.

What We Do Not Log

Just as important as what we log is what we do not log.

We do not log:

  • Message content or previews
  • Contact names, numbers, or chat data
  • Message intent, sentiment, or keywords
  • User behavior analytics
  • Engagement or performance metrics

mssg.it is not a marketing or analytics platform.

You Control When Logs Are Shared

By default, logs never leave your device.

The only time logs are shared is when you explicitly choose to share them, for example:

  • When you export diagnostic logs for support
  • When you want help troubleshooting an issue

Exports are:

  • Generated locally
  • Clearly described before sharing
  • Free of message content and contacts
  • Shared only by your action

We cannot see your logs unless you decide to send them.

Why Logging Exists at All

Logging exists to:

  • Explain why something didn't send
  • Protect against accidental overuse
  • Detect unsafe or broken states
  • Make system behavior predictable and trustworthy

It does not exist to:

  • Monitor people
  • Optimize messaging
  • Track engagement
  • Increase message volume

In Short

  • Logs are local
  • Logs are minimal
  • Logs are never shared automatically
  • You share logs only when you want

This is how mssg.it protects trust while still being reliable and supportable.