Privacy notice

Important pre-launch notice

This page documents the intended product behaviour and is not a complete production privacy policy. Forjdeck's operating legal entity, privacy contact, lawful bases, jurisdiction-specific rights, provider agreements, and final retention schedule must be confirmed before launch.

Information the product is designed to handle

• Account details such as name, email address, profile image, and team role.
• Production records, assignments, comments, mentions, and activity history.
• Review videos, version metadata, timestamps, annotations, and decisions.
• Client deliverables and raw-footage request, availability, and deletion records.
• Basic staff operations data for birthdays, leave, overtime, and subscriptions.
• Security and diagnostic data needed to protect and operate the service.

How information is intended to be used

Information is intended to provide private account access, coordinate production work, deliver and review media, manage client archives and temporary raw-footage access, notify authorised users, maintain an audit history, and protect the service. Forjdeck should not use customer production content for advertising.

Access and visibility

Access is designed to be private and role-scoped. Clients should see only their own projects and deliverables. Staff-only information—including birthdays, leave, overtime, subscriptions, internal notes, and other clients—must not be exposed to client accounts. Hiding interface controls is not a substitute for server-side authorisation.

Service providers

When configured for production, Forjdeck is designed to use Turso for application data, Resend for transactional email, Cloudflare Stream for review video, Backblaze B2 for temporary raw-footage packages, and the selected hosting provider for the application. The final policy must identify the actual contracted providers, locations, safeguards, and links to their applicable notices.

Retention and deletion

Client deliverables may be retained for long-term archive access according to the client agreement. Raw-footage packages are intended to be available for 60 days after upload, after which access should close and deletion should be verified. Review history and audit records may need a separate documented retention period. Exact schedules and legal exceptions must be confirmed before production use.

Your choices and rights

Account holders should be able to request access, correction, export, restriction, or deletion where applicable. Some records may need to be retained for security, contractual, or legal reasons. A verified privacy contact and request process are launch requirements and are not configured in this prototype.

Security and changes

Forjdeck is designed around least-privilege access, private storage, short-lived media access, secure invitation and password-reset links, and server-side permission checks. No online service can promise absolute security. Material changes to the final notice should be dated and communicated through an appropriate channel.