Privacy, in plain words.

Last updated 23 October 2026. This is short and specific to what the product actually does.

Who we are

Oraqul is built and run by Wahab and Adedunmola. It is an AI agent for launch planning in media and entertainment. This page says what we collect, why, and who else handles it. If anything here is unclear, ask the Oraqul team.

What we collect

  • Your account. Your name and email. If you set a password, we store only a salted hash of it, never the password. If you sign in with Google, we receive your name, email and whether Google has verified it.
  • What you give the agent. Your messages, the files you attach, and the projects, chats and outputs Oraqul makes from them.
  • Results you upload. We parse them into totals by place and age band, drop any personal columns, and delete the raw file. We also keep the period and the source you wrote beside them.
  • Your campaign. The actions made from a plan’s calendar, your edits and notes, and the figures you add for a test. None of it is sent to Qloo or a model.
  • Your team. Which teams you belong to, your role in each, and invites you send or receive.

How we use it

Only to run Oraqul: to sign you in, to read what you ask and answer it, to send sign in codes and invites, and to show your work to your team. We do not sell your data, show ads, or use your projects to train models.

Who else handles it

  • Qloo receives only public entity names (titles, artists, brands), place names and age bands, to look up audience taste. Never your plan text, results or anything about a person.
  • Google (Gemini), the language model we use today, receives your messages and the text of small files you attach, so it can read the title, category and job and write the answer.
  • The web search built into that same provider looks up release timing and market facts. It never receives the title or story of your work, and a question you ask it is sent with the title taken out. Pages and facts are kept on the plan with the day they were read.
  • Brevo sends our emails, so it receives your email address and the message: a sign in code or an invite.
  • Google, only if you choose to sign in with Google.
  • Our hosts run the website (Vercel) and the server and database (a private virtual server).

Cookies and browser storage

  • oraqul_session keeps you signed in, for up to 30 days or until you sign out.
  • oraqul_team remembers which of your teams is open.
  • oraqul_oauth exists only while you sign in with Google, to protect that step.
  • Your browser also stores your light or dark choice and whether the sidebar is collapsed. No advertising or tracking cookies.

How long we keep it

Your account and your team’s work stay until you ask us to delete them. Sign in codes expire after 10 minutes, invites after 7 days, and sessions after 30 days.

Your choices

You can ask to see, correct or delete your data at any time by contacting the Oraqul team. A team owner can remove members and delete projects in the app.

Changes

If this changes, we update this page and the date at the top. For how data moves through the product, see Trust.