Security and control
Controlled autonomy. Traceable down to the detail.
Upper OS may only do what you allow. Every action passes fixed checks before it is carried out, and every result is checked before it counts. Here we show how this works – and the evidence behind it.
- Permissions Has access been granted? Passed
- Approval May this happen without asking? Passed
- Budget Does it stay within the cap? Passed
- Brand rules Do tone and statements fit? Passed
- Audit trail Is everything recorded? Passed
Result: Carried out and logged.
- Permissions Has access been granted? Passed
- Approval May this happen without asking? Stopped
- Budget Does it stay within the cap? Not reached
- Brand rules Do tone and statements fit? Not reached
- Audit trail Is everything recorded? Not reached
Result: Waits for your approval, with its reasoning.
- Permissions Has access been granted? Passed
- Approval May this happen without asking? Passed
- Budget Does it stay within the cap? Stopped
- Brand rules Do tone and statements fit? Not reached
- Audit trail Is everything recorded? Not reached
Result: Blocked. Upper OS approves no spending beyond the budget cap.
- Permissions Has access been granted? Passed
- Approval May this happen without asking? Passed
- Budget Does it stay within the cap? Passed
- Brand rules Do tone and statements fit? Stopped
- Audit trail Is everything recorded? Not reached
Result: Sent back for revision before anything is published.
01 Approval limits
Clear limits for every type of action.
You define what Upper OS may do on its own and when it has to ask. Outside the limit, an action becomes a proposal.
Autonomy & Approvals · Approval rules
Example scenario- Adjust bids On its own, as long as the change is at most 15% per day Otherwise: Proposal for approval
- Shift budget between campaigns On its own, as long as the monthly budget is kept Otherwise: Proposal for approval
- Update opening hours On its own, as long as the details come from your system Otherwise: Ask first
- Start a new campaign On its own, as long as never Otherwise: Always with approval
- Publish content On its own, as long as never Otherwise: Always with approval
Example scenario: Fictional company and illustrative figures – no real customer or product data.
02 Budget control
Caps on every level.
Budgets are nested: the monthly budget caps the channels, the channels cap the campaigns. On no level does Upper OS release spending beyond the limit above it.
Autonomy & Approvals · Budget structure
Example scenarioMonthly budget
CHF 2,000 Hard cap
Channels · Search
CHF 1,700Campaigns
“Heat pump advice”
CHF 1,500
Campaigns
Brand terms
CHF 200
Reserve
CHF 300
Not yet allocated – free for new opportunities, only within the monthly cap.
Example scenario: Fictional company and illustrative figures – no real customer or product data.
How a cap behaves day to day is shown by the simulator on the autonomous marketing page. Go to the budget simulator
03 Permissions and roles
Everyone sees and decides what fits their role.
You define who sets goals, who approves and who only sees results. Upper OS itself only works with the rights you grant in the connected systems.
Autonomy & Approvals · Permissions and roles
Example scenario- Set goals and budgets Allowed
- Change approval rules Allowed
- Approve actions Allowed
- Connect systems Allowed
- View results and audit trail Allowed
- Manage access Allowed
- Set goals and budgets Not allowed
- Change approval rules Not allowed
- Approve actions Allowed
- Connect systems Allowed
- View results and audit trail Allowed
- Manage access Not allowed
- Set goals and budgets Not allowed
- Change approval rules Not allowed
- Approve actions Not allowed
- Connect systems Not allowed
- View results and audit trail Allowed
- Manage access Not allowed
- Set goals and budgets Not allowed
- Change approval rules Not allowed
- Approve actions Allowed
- Connect systems Allowed
- View results and audit trail Allowed
- Manage access Not allowed
Example distribution of roles. You define roles and rights yourself.
04 Traceability
Every action with reason, rule and effect.
The audit trail records who did what and when – and why. Every entry can be opened.
Marketing Command Center · Audit trail
Example scenario-
09:12 Raised bids for three search terms by 8% Executed
- Triggered by
- Upper OS
- Rule
- Bids: on its own up to 15% per day
- Reasoning
- More relevant searches in the morning, cost per verified enquiry below target.
- Change
- Average bid CHF 2.40 → CHF 2.60
-
08:40 Verified an enquiry from the contact form Verified
- Triggered by
- Upper OS
- Rule
- Results only count after matching
- Reasoning
- Recorded in the customer database as a new quote request, origin: search campaign.
- Change
- Verified enquiries 8 → 9
-
Mon 11:20 Stopped a social media post Stopped
- Triggered by
- Upper OS
- Rule
- Brand rules: no unsupported comparisons
- Reasoning
- The wording “cheapest provider in the region” is not supported.
- Change
- Back to draft
-
5 Oct Approved the campaign “Heat pump advice” Approved
- Triggered by
- Management
- Rule
- New campaigns: always with approval
- Reasoning
- Reviewed the proposal with expected effect and budget cap.
- Change
- Proposed → Approved
Example scenario: Fictional company and illustrative figures – no real customer or product data.
05 Verification
Two checkpoints: before and after.
Before execution, guardrails check whether an action is allowed. After execution, the result is checked: is it genuine and does it belong to the action?
Autonomy & Approvals
Before execution
- Permissions
- Approval
- Budget
- Brand rules
Autonomous Execution
Action
Adjust bids of the search campaign “Heat pump advice”
Measurement of the effect started
Performance & Verification
After execution
- Measurement works
- Result is genuine
- Origin assigned
- Matched with customer database
9 / 12
Counted as a result
9 of 12 reported enquiries verified · 2 Spam, 1 Duplicate enquiry excluded
Example scenario: Fictional company and illustrative figures – no real customer or product data.
06 Data isolation
Every company in its own space.
Upper OS is designed so that each company’s data, rules, knowledge and audit trail sit in its own, separate workspace. This also applies to agencies with many clients: every client gets its own, separate workspace.
-
Workspace
Company A
- Marketing Brain
- Data from your systems
- Approval rules and budgets
- Audit trail
-
Workspace
Company B
- Marketing Brain
- Data from your systems
- Approval rules and budgets
- Audit trail
-
Workspace
Company C
- Marketing Brain
- Data from your systems
- Approval rules and budgets
- Audit trail
07 Evidence
Proof, not badges.
Trust comes from documents you can check. We publish evidence when it exists – and name nothing that is not supported.
-
Documents to read
Data processing, sub-processors and privacy will be documented publicly before the conclusion of a contract.
-
Certifications only once issued
We only name a certification or external audit once it has been issued.
-
Functions only once tested
A function counts as available once it has been technically tested – not before.
Explore further
Let’s talk about your goals.
Tell us briefly what you want to achieve with your marketing.