Brand Context Protocol Registryclaimed
Public brand record

Omniva

This record is managed by an account, but domain control has not been proven.

boundaries.md

---
bcp_version: "0.8"
file_type: boundaries
parent: https://registry.brandcontextprotocol.dev/omniva-691-staging/.well-known/brand.md
last_updated: 2026-10-06
---

# Boundaries

This public-source demonstration does not authorize an agent to speak for Omniva, alter a shipment, promise a remedy, handle personal information, or approve claims on Omniva's behalf.

## Hard no

```yaml
hard_no:
  - item: "Do not present this BCP as official, approved, domain-verified, or authored by Omniva."
    tier: core
  - item: "Do not invent or change a tracking status, delivery estimate, price, route, parcel-machine location, opening time, compensation, or service availability."
    tier: core
  - item: "Do not ask for, expose, or repeat unnecessary personal data, access codes, credentials, payment details, addresses, or shipment identifiers. Use the current official secure workflow."
    tier: core
  - item: "Do not guarantee delivery time, condition, availability, successful customs clearance, customer happiness, or resolution."
    tier: core
  - item: "Do not describe a service or delivery as sustainable, green, carbon-neutral, emission-free, or zero-impact without current scoped evidence."
    tier: core
  - item: "Do not claim a customer, merchant, carrier, government, or partner endorses Omniva or this package unless a current official source states the relationship and scope."
    tier: core
  - item: "Do not turn Omniva's vision, Caregiver archetype, areas of excellence, or 'delivering happiness' idea into proof of an operational result."
    tier: core
  - item: "Do not draw, trace, typeset, approximate, or generate an Omniva symbol, wordmark, slogan lockup, or graphic element. Use a current official asset and confirm usage rights."
    tier: core
  - item: "Do not use Omniva's name or visual identity to imply approval of this demonstration."
    tier: core
```

## Review required

```yaml
soft_no:
  - topic: "Service availability and delivery estimates"
    rule: "Confirm origin, destination, service, item type, cut-off, local terms, and current operational information. Label estimates as estimates."
    tier: core
  - topic: "Tracking and support"
    rule: "Use the official tracking or support channel. Verify identity and authorization through that channel before discussing protected shipment details."
    tier: core
  - topic: "Loss, damage, delay, returns, and compensation"
    rule: "Use current local terms and the accountable claims process. Do not improvise liability, eligibility, deadlines, or remedies."
    tier: core
  - topic: "Restricted goods, customs, taxes, and cross-border transit"
    rule: "Use current official rules and qualified advice for the exact route and item. Do not infer legality or clearance from general brand material."
    tier: core
  - topic: "Environmental claims"
    rule: "State the initiative, emissions or impact boundary, geography, reporting period, method, result, and limitations from a current Omniva source."
    tier: core
  - topic: "Comparative or leadership claims"
    rule: "Define the category, geography, period, method, and source; obtain review before naming a competitor."
    tier: default
  - topic: "Partnerships and customer stories"
    rule: "Confirm the current parties, scope, permission, results, and attribution."
    tier: default
  - topic: "Promotions and offers"
    rule: "Confirm market, eligibility, dates, price, inventory or capacity constraints, and applicable terms."
    tier: default
  - topic: "Humor and gift or Christmas imagery"
    rule: "Keep branding subtle and context-aware. Remove humor when addressing service failure, safety, privacy, or distress."
    tier: default
```

## Entity and context distinctions

- Omniva Group corporate language is not a substitute for current Estonia, Latvia, or Lithuania service terms.
- “Across the Baltics and beyond” does not mean every service is available for every origin, destination, or item.
- A public brandbook asset is not automatically licensed for every use. Confirm rights, current version, format, and language.
- “Delivering happiness” is brand language, not a warranty or service-level commitment.
- “Seamless and sustainable” appears in vision language. Treat it as direction, not verified outcome.
- The brandbook traces the postal-service story to 1638; do not say the current legal entity has operated unchanged since that date.

## Incident response

When the source does not resolve a live delivery, privacy, payment, customs, safety, or account issue, say what is unknown and route the person to Omniva's current official local channel. Do not fabricate a reassuring status. Care is shown through an accurate handoff.

## Sources

- https://www.omnivagroup.com/
- https://www.omnivagroup.com/brandbook/tone_of_voice/
- https://www.omnivagroup.com/brandbook/logo/
- https://www.omnivagroup.com/brandbook/colors/
Domainomnivagroup.com
Registry handleomniva-691-staging
Published2026-10-06 · 8 files
Read the source

Brand context for people and agents.

The signed BCP is the machine-readable record. Agents can fetch the root file directly or connect to the same record over MCP.

Ownership status

Prove domain control.

This record is claimed but not yet domain-verified. Open the owning Encoded Brands workspace to finish DNS verification.

Verify in Encoder →

Contact support if the record belongs to a different account.