Frequently Asked Questions

No. Roya is a pre-submission verification layer only. We do not touch money, do not replace societies, and do not change your workflow. We simply catch errors before they reach STIM's queue.

STIM's validation remains the final authority for all registrations. If Roya misses something, STIM's process catches it as normal.

No integration required. Roya operates as a standalone pre-submission layer for publishers. There are no changes to STIM's existing IT systems, no CUBE code modifications, and no timeline dependencies.

Publishers upload their STIM registration CSVs to Roya, we validate them, and they receive verified files ready for submission to STIM — using exactly the same workflow they use today.

STIM's validation is still the final authority. Roya is an additional check, not a replacement. If we miss something, STIM's process catches it as normal — exactly as it does today.

The pilot will measure both false positives and false negatives to ensure accuracy.

Roya stores only the data needed for verification: contributor names, roles, percentages, and IPI/ISWC identifiers from split sheets. All personal data is stored in secure, encrypted infrastructure compliant with GDPR and applicable Swedish data protection regulations.

We do not store payment data, bank details, or sensitive personal information beyond what's already in STIM submissions.

Blockchain provides an independent, tamper-proof timestamp. In disputes, neither party can claim the verification was altered after the fact. It serves as a neutral third-party record.

The blockchain stores only a cryptographic fingerprint (hash) of the document — no personal data, no contractual terms, no financial information. It's simply a timestamped proof that the file existed at a specific point in time.

Yes. During the pilot, we'll establish data-sharing protocols so STIM can verify the audit trail for any disputed registrations. Publishers can also share their verification reports directly with STIM when questions arise.

Zero cost to STIM. The pilot is fully funded by Roya. Participating publishers use the service at no cost during the evaluation period. There are no integration costs, no licensing fees, and no financial commitment from STIM.

We'll track four key metrics:

• Rejection rate reduction: Target 20-30% decrease in split-related corrections for pilot publishers
• Processing speed: Time from submission to completion (target: days instead of weeks)
• Admin time saved: STIM staff hours spent on manual corrections (target: 3,000+ hours/year at scale)
• Workflow impact: Zero disruption to existing processes

After the 5-month pilot, we'll present a comprehensive report to STIM leadership with findings, metrics, and recommendations. Based on results, we can discuss:

• Extending the pilot to additional publishers
• Long-term operational integration models
• Potential for STIM-endorsed verification standard

There is no obligation to continue beyond the pilot period.

Almost nothing changes. Publishers who already export STIM CSV files can upload them to Roya, receive a verification report, and fix any issues before submitting to STIM. The workflow is:

1. Export CSV from their existing system (same as today)
2. Upload to Roya (new 2-minute step)
3. Review issues and auto-fix if desired
4. Download verified file and submit to STIM (same as today)

No system integration required, no software to install, no training needed.

They receive a verification record confirming the data is clean and can submit directly to STIM with confidence. The verification record provides an audit trail that can be referenced if questions arise later.