Trust and governance

Who reads, who approves, and who sees what.

Ijaz is powered by AI, and works for a team with a manager, a legal reviewer and a procurement committee. Here is what buyers and information security ask, so they find it before they ask.

1 · AI

It reads and writes for you, and never speaks for you

The AI in Ijaz reads what is published about you, then writes the brief, the alert and the report. Publishing, replying and approving are your team’s decisions alone.

  • It publishes nothing in your name. What Ijaz writes reaches you, and nothing of it is posted on your accounts.
  • Who reviews the brief? Ijaz writes the brief with AI, then a second model reads it before it is sent: it matches every figure to its source, corrects or removes what doesn’t match, and puts the source link under every item. If that review cannot run, the brief is recorded as not reviewed and our team is told.
  • Approval before sending, if you like. The brief reaches your editors first, and the rest of the team only once one of them approves it.
  • It learns from your team. Readers’ ratings of items and their corrections are kept for your company only, and tomorrow’s brief builds on them.
2 · Changes

Every change, with who made it and when

Every edit to the monitoring plan, competitors, sections, readers and settings is logged with who made it and when, on the changes page of your dashboard, and can be undone from there.

From the change log

5 Nov 09:14 · Head of comms added a competitor: “Al Nakheel” · Undo

A change by email

4 Nov · An editor replied to the brief asking to add a reader, added after confirmation

In every brief

The brief ends with its keywords and monitoring window, so every reader knows what it was built on

Illustrative examples

3 · Sign-in and roles

Everyone sees what concerns them, and edits what they own

RoleWhat they can do
Account managerEverything, including inviting the team and setting their roles, approval chains, the subscription and data-connection keys.
EditorKeywords, competitors, sources and accounts, alert rules, the brief and approving it before it is sent, and the activity log.
AnalystCorrects the tone of posts, proposes rules, writes reply drafts, asks for reports and builds dashboards.
ApproverFor legal and investor relations: approves drafts at their step of an approval chain, and edits nothing else.
ReaderReads the dashboards, alerts, reports and brief, without changing anything.
Brief readerGets the brief only, in their language and edition; unlimited on every plan and not counted among dashboard users.
Sign-in with an emailed code

Every user signs in with a link or a 6-digit code sent to their email, valid for 30 minutes and once only; after 5 wrong tries the code stops working. Any user can add a password, or a code from an authenticator app with 10 recovery codes, to make sign-in two steps, and the account manager can require the app code of every member. On the Enterprise and Groups plans a company can sign in through its own identity provider (OpenID Connect) for its email domains.

Signed sessions

A session lasts one day, or 30 days if the user chooses “Keep me signed in”, in a signed cookie that page scripts cannot read. It ends on sign-out, and every user can end their sessions from the security page.

Signed links

Links to view the brief and to reader settings are signed per reader, and the owner can turn off opening the brief without signing in.

Approval chains

Each kind of draft has an approval chain the account manager sets, including a legal and investor-relations step for listed companies; a reply goes out only once it is complete.

Activity log

Every sign-in, edit, approval and export is logged with who did it and when. The account manager exports it as CSV or JSON, and each new line can go to the company’s signed webhook.

Data connections

Read-only keys limited to the data you choose, and signed webhooks, depending on the plan.

For groups

Each company in a group keeps its data and permissions separate, and the group's management has its own roles.

4 · Your data

We read what is published, and never ask for your keys

We never ask for your account passwords

We never ask for the password of any of your company’s accounts on the platforms. Their links are enough.

No selling or sharing

We don’t sell your data or share it for marketing, and we don’t send your reader list to the model provider.

No open tracking

On request, we stop counting email opens and link clicks for your whole account.

Retention and deletion

After a subscription is cancelled we keep the account’s data for 30 days after the paid period ends, then an automated job deletes it; we email the account manager 7 days before. Billing records are kept as the law requires.

Support access with your permission

Ijaz support opens your company’s account only with a permission the account manager grants from the security page, for a time they set, and can withdraw at any time. Every entry is in the activity log.

5 · Procurement

Ask for the vendor pack

The vendor pack: a summary of the master service agreement, the data processing agreement with its list of sub-processors, the service level agreement, and written answers to the usual vendor security questionnaire. Leave your work email; our team reviews the request and sends you the pack’s link. We also answer your own questionnaire if you send it.

We use this email only to answer your request.