Know what
you are sharing.
FramePulse shares a view of render progress, not your footage. A monitor link is readable by anyone who possesses it.
This website
The Dream Road Labs website contains no third-party tracking cookies, behavioral analytics scripts, or advertising beacons. Browsing our pages is accountless. Network requests necessary to serve pages and static assets are handled by hosting providers for routing, DDoS protection, and operational integrity.
Software registration & download
When you request FramePulse from our download page, we collect your name and email address to process your registration and deliver the setup link via transactional email. Transactional email delivery and contact management are handled securely through Resend.
Optional marketing consent: You may optionally choose to receive product updates and news from Dream Road Labs. This consent is separate, default-unchecked, and never required to download the software. If you do not opt in, your registration is retained solely for software delivery and records, without creating a marketing subscription.
Retention and data removal: Registration records are retained privately for product delivery and operational verification. To request removal of your registration details or update your preferences, reply to your download email. Marketing unsubscribe preferences in Resend are preserved.
Aggregate service counts
The FramePulse infrastructure records high-level aggregate counters: active writer connections, rendering monitor sessions, connected viewer WebSockets, and HTTP setup download requests. These represent raw network request counts and connections—not unique individuals, persistent user profiles, or completed installations. Daily download metrics and active session states contain no project names, timeline names, disk paths, shared URLs, writer credentials, or IP addresses.
What a FramePulse link exposes
Creating a monitor link publishes normalized project and timeline names, approved render settings, and live status metrics. Depending on information exposed by DaVinci Resolve, these include:
- Normalized project name and timeline name (capped at 100 characters)
- Video format, codec, resolution, and output frame rate
- Render state (waiting, rendering, paused, completed, cancelled, or failed)
- Elapsed rendering time, estimated time remaining (ETA), and progress percentage
What is never exposed: FramePulse never uploads video files, source media, render output files, local workstation disk paths, internal Resolve identifiers, or private writer keys.
Who can read a monitor link
Viewer links are accountless: viewers do not sign in or authenticate. Anyone possessing the URL can view the render status, including anyone to whom a recipient forwards the link. Do not include confidential client or project codenames in project titles if they should not be visible to link possessors.
Chat and messaging link previews
Sharing a FramePulse link inside messaging platforms (such as Slack, Messages, or WhatsApp) may prompt the messaging provider to fetch open-graph preview metadata, displaying the project and timeline name. Those platforms determine their own preview caching lifetimes.
Session and snapshot lifetime
Each monitor session has a strict, fixed lifetime of seven days from creation. Viewers can view the last reported status snapshot until the seven days expire.
On your workstation, monitor sessions and writer keys exist only in the current FramePulse process memory. Closing FramePulse clears desktop links and disconnects live updates; reopening starts empty. Stopping tracking or removing a link disconnects live updates without immediately revoking the viewer link.
Third-party infrastructure
FramePulse queries render status using the locally installed DaVinci Resolve Studio Workflow Integration SDK provided by Blackmagic Design. Cloud telemetry and read-only viewers are served using Cloudflare edge infrastructure, and transactional registration delivery is provided via Resend. Dream Road Labs does not claim endorsement by or partnership with these independent providers.
Practical choices
Share links only with trusted team members or clients. Keep FramePulse open only while active updates are needed. For detailed lifecycle and configuration guidance, refer to the support guide.
This launch privacy information requires owner approval before public deployment.