What data goes where.
For reviewers, legal and anyone who has to sign off. What leaves your team, what Oraqul keeps, and who on your team can see it.
- Only public names, places and age bands go to Qloo.
- Uploaded results are kept as totals, never as people.
- Your plans are visible only to your team.
- Every number is computed by code you can check.
What travels, and what stays.
Your team
- Comparable titlesPublic
- Mexico City, LondonPublic
- Ages 25 to 34Public
- Your title and your planStays here
- Customer emailsStays here
Oraqul
Keeps the public names of comparable titles, places and age bands. Drops personal columns from uploads and deletes the raw file.
Qloo
Taste data comes back for public names only.
Salt RoadMexico City25 to 34
Where each thing goes.
WhatGoes toKept
- Comparable titles, place names and age bandsGoes to: Qloo, to look up audience tasteKept: With the claim it supports, as its receipt
- Your messages and plan textGoes to: The configured language model provider, to read the job and write the answer. Never to QlooKept: In your team’s project and its chats
- Results you supplyGoes to: Parsed into totals by place and age band, with the period and the source you wrote. Never to QlooKept: Totals only. The numbers kept are totals by place and age band; the text of the file stays on your project, so leave personal columns out
- Web searches for release timing and the marketGoes to: The language model provider’s own search. The title and story of your work are never sent, and a question you ask is sent with the title taken outKept: On the plan, as the page, the fact and the day it was read
- Campaign actions and the figures for a testGoes to: Nowhere. Code builds the actions from your plan, and your figures are compared in code, never sent to Qloo or a modelKept: In your team’s project, with the plan version they belong to
- Your name and emailGoes to: Our database, and our email service for sign in codes and invitesKept: With your account
- Anything about a personGoes to: NowhereKept: Not collected for planning
Who can see what.
Work belongs to a team. Each person on it has one role, checked on every request before anything is read or changed.
- Owner
- Manages members and invites. Can do everything an editor can.
- Editor
- Starts and continues plans, and edits projects.
- Viewer
- Reads projects and outputs. Cannot change anything.
| Action | Owner | Editor | Viewer |
|---|---|---|---|
| See the team and its members | Yes | Yes | Yes |
| Read projects, chats and outputs | Yes | Yes | Yes |
| Start and change projects, run the agent | Yes | Yes | No |
| See pending invites | Yes | No | No |
| Invite, change a role, remove a member | Yes | No | No |
Accounts and links.
Sign in
Email and password, Google, or a one time code by email. Codes expire after 10 minutes and work once.
Sessions
A sign in lasts up to 30 days on that browser. Signing out ends it.
Share links
Owners and editors can share one output as a read only link, and turn the link off at any time.