Private software is faster to build than ever. Authentication services, modern frameworks and managed infrastructure make it possible to launch a customer portal or internal tool in days.
That speed solves access. It does not automatically solve what happens when an authorised viewer captures the screen.
Start with the identity you already have
ExactMark does not need to replace your login. After authentication, the application passes the stable user ID it already knows to the SDK, with optional context such as a display name, email address and page.
That identity is associated with the protected session. Every authenticated viewer receives a session-specific rendered signal while the application continues to behave normally.
Protect the right surfaces
Begin with the pages where a screenshot would create the greatest uncertainty or damage. Typical priorities include:
- Financial and investor information
- Customer records and account details
- Proprietary research
- Client deliverables
- Internal operational data
- Administrative and reporting interfaces
The allowed-origins policy ensures the property is issued only where expected. Protection settings can then be adjusted for the needs of the application.
Keep privacy in the design
Traceability should not require collecting the contents of every protected page. The ExactMark SDK records the session identity and relevant context needed for attribution; it does not capture page contents.
Viewer IDs can also be pseudonymised, allowing the protected application to retain the mapping in its own system.
Test the real integration
An installation is not complete merely because a script tag exists. Use the connection test to open the protected application through an isolated test flow, sign in and confirm that ExactMark receives the expected session.
Review the first detected and last detected timestamps, the identified viewer and the recorded page. This confirms that the SDK loads after authentication and receives the intended user identity.
Traceability is an operational control
Once installed, ExactMark creates the session history needed if evidence surfaces later. That history is most valuable when teams know how to preserve an original screenshot, run an analysis and interpret a confidence-scored result responsibly.
One script establishes the technical layer. A small response process turns that layer into a useful operational control.