Frequently asked questions.

To request a report by email, send an email to report@sanctioniq.io.

Enter the name and country of the person or company you wish to search in the subject line. No text is required in the body of the email unless you want to pass your own additional parameters, which are then returned in the response.

Example email subjects:

• John Smith from Gibraltar
• John Smith from Spain, CEO of CompanyX
• John Smith from UK, DOB: 04/04/1979, CEO of CompanyX

For companies, simply replace the individual's name with the company name.

Example: John Smith from Gibraltar - LANGUAGE:SPANISH

To request a report from the portal, log in to your SanctionIQ dashboard and use the report request form.

Enter the subject details, choose the required report format and submit the request. Reports normally return to the portal within approximately 2 to 3 minutes.

Choosing a report format:

• HTML: This is usually the most common and easiest format for most users. It displays the report in a clean, readable layout inside the portal and can be exported neatly to PDF once the results arrive.
• JSON: This is a structured data format mainly used by technical teams, developers or systems that need to read the report automatically. It is useful for integrations, but it is not designed to be read like a normal document.
• Text: This provides the report as plain text only, without styling or layout. It can be useful when you need a simple copy-and-paste version of the findings.

For the smoothest experience, keep the browser window open while the report is being generated. If you close the browser or the report is not collected through the portal, SanctionIQ can send the completed report to you by email as a fallback.

API access is available to Enterprise accounts and to Professional accounts with the optional API add-on.

For API request formats, authentication, live endpoints and test endpoints, please read the API documentation: https://sanctioniq.io/documentation.html

The more detail you provide, the more accurately SanctionIQ can identify the correct person or company. Useful additional details include country, date of birth, current role, employer, company name, nationality or other identifiers.

However, very specific details can sometimes narrow the search too much. For example, adding a role or location may help distinguish between people with similar names, but it may also limit broader discovery if the public records use different wording.

Strict Search is an optional setting that tells SanctionIQ to treat supplied identifying details as stronger matching filters. These may include date of birth, country, nationality, company name, role, address, registration number or other identifiers.

When Strict Search is enabled, SanctionIQ is more cautious about linking results to the searched person or company. This can reduce false matches involving similarly named individuals or entities, but it may also return fewer report details.

When Strict Search is not enabled, SanctionIQ uses the broader default search mode. This may return more possible matches and wider OSINT context, but users should review similar-name results carefully.

Portal: Strict Search can be enabled by ticking the Strict search checkbox on the dashboard report form. If left unticked, the report runs in the broader default mode.

Email: add STRICT:TRUE to the email subject or body. If you do not include it, Strict Search defaults to off.

Example email subjects:

• John Smith from Gibraltar - DOB: 04/04/1979 - STRICT:TRUE
• John Smith from Gibraltar - LANGUAGE:SPANISH - STRICT:TRUE
• CompanyX from Spain - registration number 123456 - STRICT:TRUE

API: include the optional strict parameter in the request payload. If omitted, it defaults to false.

Only the main account owner can edit account-level details, including company details or the main individual account record.

Linked users can edit their own profile details, but they cannot edit the commercial account, company profile, billing settings or owner-level details.

Only the main account owner can manage billing. This includes upgrades, downgrades, billing cadence changes, token packs, recurring extra seats and API add-ons.

Linked users can use the platform according to the account permissions and available credits, but they cannot purchase or modify subscriptions.

Yes, active linked users can access the dashboard if they have been invited and activated. Disabled users cannot log in or request reports.

Reports can be requested through three channels:

• Dashboard: users submit a request from the portal and wait for the result.
• Email: authorised active users can send a report request from their registered email address.
• API: authorised accounts with API access can submit report requests programmatically.

The underlying report flow is designed to be consistent across all channels. The main difference is delivery format and how the request is submitted.

Dashboard requests return to the portal, email requests return by email, and API requests can return to a callback URL or use the configured response format.

Only active users linked to the account can request reports. This applies to dashboard, email and API requests.

If a linked user is disabled, their report requests are blocked and no report is generated.

A token is deducted only when a report request is accepted for processing. If the request is blocked due to access, billing status, unavailable credits or invalid permissions, no token should be deducted.

No. SanctionIQ is designed around a privacy-first model. Full report content is generated and delivered to the user, but it is not retained as a long-term archive by the platform.

The system may temporarily hold report content only as needed for delivery, fallback delivery or short-lived dashboard retrieval.

SanctionIQ records operational metadata needed to run the service, such as account details, authorised users, usage counts, billing status, API key metadata, report IDs, request status and delivery status.

The platform is designed to avoid storing the full report content as a permanent record.

Metadata is required for access control, usage tracking, billing, troubleshooting, delivery confirmation, auditability and support.

The current privacy-first approach does not retain full reports by default. A future version may allow paid users to choose per report whether a report should be stored, but that would be explicit and user-controlled.

If the account has no available report tokens, new report requests are blocked until more tokens become available.

Depending on the plan, this may happen when the next billing period begins or when the main account owner purchases a token pack or upgrades the plan.

Yes. Purchased token packs/top-ups roll over until consumed. Subscription plan tokens reset each billing period and do not roll over.

If a subscription payment fails, the account enters a grace period. During the grace period, users can continue generating reports as long as credits remain available.

If the payment is not resolved before the grace period ends, report generation is suspended until payment succeeds.

Only the main account owner can purchase token packs, upgrade, downgrade, change billing cadence, add extra seats or manage API add-ons.

If a dashboard report is generated successfully but is not collected through the portal, SanctionIQ can use fallback email delivery so the report is not lost.

If an API report is generated successfully but cannot be delivered to the callback URL, SanctionIQ can fall back to email delivery where possible.

Because the report was successfully generated, callback delivery failure does not automatically mean the token is refunded. The priority is to safely deliver the result by an alternative route.

If report generation fails before a usable report is produced, the system is designed to handle the failure, notify the user where appropriate and avoid charging unfairly.

A linked user is an additional user attached to the main account. Linked users can request reports if they are active and the account has available credits and access rights.

Disabled users do not consume an active seat. If a disabled user is re-enabled, they will consume a seat again.

Yes, provided the account has available seat capacity. If all available seats are already in use, the user cannot be re-enabled until a seat is freed, an extra seat is added or the plan is upgraded.

Yes. The main account owner can disable or remove linked users, but the primary account owner cannot disable themselves.

Any active user linked to the account can request a report by email from their registered email address, provided the account has available credits and report access is not suspended.

If a disabled or unauthorised user sends a request, the system can reply explaining that they are not authorised to request reports.

API access is account-based. If the account has API access, an API request can be attributed to any active linked user on that account, provided the submitted user email belongs to an active linked user.

No. Report generation requires the user to be active at the time of request. Disabled users are blocked across dashboard, email and API report flows.

Review the sources and the extended findings carefully. SanctionIQ reports are designed to assist compliance review, but the final assessment should always be reviewed by a qualified person.

If something appears wrong, contact support with the report ID and a clear explanation of the issue.

Include the report ID, account email, approximate request time, request channel used and a short description of the issue. Do not send unnecessary sensitive personal data unless requested.

No. SanctionIQ provides AI-assisted compliance report outputs to support human review. Reports should be assessed alongside your organisation's policies, regulatory obligations and professional judgement.

Yes. SanctionIQ provides a development/test API route that allows you to integrate and test your implementation without consuming live report tokens.

This route returns mock or controlled responses designed specifically for integration testing.

Once your integration is complete, you can switch to the live endpoint to begin generating real reports.

Full API details, including authentication, endpoints and usage examples, are available in the documentation: https://sanctioniq.io/documentation.html