Apex Video
Privacy notice
Effective August 5, 2026. This notice explains how GFSR LLC (GFSR), owned and operated by Jonathan Blanco, handles information for the Apex Video website and private creation console.
Information used for sign-in
The email address entered on the sign-in page is used to deliver a single-use sign-in code. It is kept only until that message is accepted for delivery, then discarded; the service retains a protected one-way representation of the address, a request reference, and limited authentication records. Those records do not contain the address exactly as submitted or the readable sign-in code. An account is identified by that one-way representation, and each account's work is isolated from every other's.
Sessions and security evidence
Successful sign-in creates an essential, security-protected browser session. Sign-in codes and sessions expire automatically. Limited records needed to prevent abuse, investigate security events, and demonstrate account access may be retained for security and accountability.
Video requests
Video instructions are processed to create a structured production plan. The service retains job records and output details needed to fulfill, secure, audit, and troubleshoot requests. The original instruction text is not included in the production plan sent for video creation.
Voice input
If you choose Dictate, your browser or device speech service may process microphone audio to produce text. Apex does not receive or store the microphone recording. Apex receives the resulting text only when you choose Create video, and then handles it as a video request described above.
Service providers and tracking
Specialized service providers process website delivery, security checks, data storage, background processing, and transactional email on behalf of the operator. The application contains no advertising and does not use advertising or behavioral-analytics trackers.
Contact
For a security or privacy concern, use the role address published in our security.txt.