How information moves through Striq.
A plain-language view of what enters the service, why it is used, and what remains under your control.
You add the record.
Your team provides account details, creator assets, agreements, licence terms, advertisements, notes, and decisions needed to operate its rights workflow.
Files stay private.
Private source files are stored behind limited access. The browser receives only the access needed for the signed-in person and requested action.
Terms become structured fields.
When extraction is enabled, the service proposes contract fields for a person to check. The source remains available beside the proposal.
Rules compare use with permission.
Striq compares confirmed terms with asset, advertisement, channel, territory, dates, and spend to surface conflicts and expirations.
People make the decision.
An authorized team member renews, approves, removes, or escalates the use. The service records the decision and supporting note.
Retention closes the loop.
Source-file retention follows organization settings. Account, security, and decision records may be kept longer where needed to provide and protect the service.