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 an opaque viewer reference
ExactMark does not replace your login. After authentication, your backend reads a stable, randomly generated viewer reference that only your application can map to the account. It then signs a short-lived token binding that reference to the correct Web App.
The browser passes only the opaque reference and matching token to ExactMark. Every verified Web Session receives its own 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 a protected page or the viewer's profile. The ExactMark SDK does not accept names, email addresses, usernames, raw account IDs or page paths, and it does not capture page contents.
The customer retains the only mapping between each opaque reference and its real account. ExactMark stores the reference as pseudonymous session data, not as a personal profile.
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 and last activity timestamps, Web App and opaque viewer reference. This confirms that the SDK loads after authentication and receives the intended signed reference without receiving personal viewer details or a page path.
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.