In plain language
Ages Capture is a film and television production capture tool for authorized production crew members. The app records media when a user starts recording, saves files locally on the device, creates project metadata and logs, and uploads approved project media to the project's Box folder.
1. Overview
Ages Capture is a private capture app for authorized film and television production use. In this policy, "production" means a film, television, streaming, commercial, or similar video production project, and "the production" means the company or client running that project. The app is designed to help production teams record project video and audio, save files locally on the assigned device, create project metadata and logs, and upload approved project media to the production's approved Box folder.
Ages Capture is not a public social media app, advertising app, or consumer sharing service. It is not available to the general public. It is intended for authorized production crew, producers, production staff, cast-facing teams, or other users approved by the production/client.
The app should only be used for production work where the production/client has decided that the user, device, and project are authorized.
2. Who controls the data
For each film or television production, the production company, client, employer, or project owner generally controls the production media and project records created for that project.
Ages Productions Inc. provides the app, setup support, workflow support, and technical upload tools for the production workflow. Depending on the project agreement, Ages Productions Inc. may act as a service provider, processor, contractor, technical workflow provider, or production-support vendor for the production/client.
Box may be used as the production/client-approved storage platform for project files. The production/client's Box administrator may control Box access, folder permissions, retention rules, sharing, legal holds, and deletion policies.
3. Information the app may collect, create, store, or upload
Ages Capture may collect, create, store, display, or upload the following categories of information as part of normal app functionality.
3.1 Production media
- Video recordings created in the app
- Audio captured with video recordings
- Optional thumbnails or preview images used for upload status or review
- Optional Photos library copies, if that setting is enabled
3.2 Project and production metadata
- Project/File Naming ID
- Assigned ID, camera ID, phone ID, or similar production identifier
- Display Name entered in Setup / Project Info
- File name generated by the app
- JSON sidecar filename
- Capture date and time, including local and UTC timestamps
- Duration, file size, media type, frame rate, resolution, requested capture quality, and related file details
- Local file path references used by the app to manage app-private storage
- Cloud provider name, cloud folder path, cloud file path, or cloud file ID when uploads are completed
- Upload status, upload attempts, upload timestamp, upload method, and error summaries
- App version, iOS version, device model, and device name or device identifier used for diagnostics and project setup
3.3 Location information
If enabled for the project and allowed by the device/user, Ages Capture may collect and store capture-location metadata. This may include GPS latitude and longitude and the device's location permission status.
Location metadata may appear in JSON sidecars, daily logs, master logs, or other project records. If location permission is denied, unavailable, or disabled, location metadata may be missing or marked unavailable.
3.4 Upload and workflow logs
The app may create local logs, daily logs, master logs, test reports, and upload queue records. These records may include:
- File name and sidecar file name
- Project ID / Project File Naming ID
- Assigned ID
- Display Name
- Local and UTC capture timestamps
- Upload timestamp
- File size and duration
- Media type
- GPS latitude/longitude and location permission status, when available
- Device name, device model, iOS version, and app version
- Upload provider or upload mode
- Cloud folder path, cloud file path, or cloud file ID
- Upload status, retry status, upload attempt count, and failure/error summaries
- Local save status
- JSON sidecar status
- Upload method, such as direct or chunked upload
- App settings relevant to capture, storage, upload, cleanup, or project readiness
These logs are intended to help production and post teams verify what was recorded, what uploaded, what failed, what needs attention, and what was handed off.
3.5 Device credentials and runtime tokens
The app may store an Ages-issued device credential in the iOS Keychain so the app can request project-limited upload access from the backend broker.
The app should not store or display Box client secrets, Box enterprise credentials, Box developer tokens, Box refresh tokens, Cloudflare Worker secrets, Authorization headers, or long-lived Box credentials.
The app may receive a short-lived, downscoped Box upload token at runtime so the device can upload directly to the approved Box project folder. Runtime tokens should not be written to logs, CSV exports, JSON sidecars, Test Reports, screenshots, or public documents.
4. How information is used
Ages Capture uses information for the following purposes:
- Recording production video and audio when the user starts a recording
- Saving production media locally on the assigned device
- Creating filenames, JSON sidecars, daily logs, master logs, and upload records
- Uploading approved project media, sidecars, and logs to the project's approved Box folder
- Showing upload progress, completed uploads, failed uploads, retry status, and missing-file status
- Supporting production-to-post handoff reporting
- Troubleshooting capture, storage, metadata, network, upload, Box, broker, and setup issues
- Confirming whether project setup, permissions, broker access, credentials, and upload readiness are configured correctly
- Supporting project wrap, device disablement, and cleanup workflows
Ages Capture does not use production media or app data for advertising. Ages Capture does not sell personal information. Ages Capture does not track users across other companies' apps or websites for targeted advertising or advertising measurement.
5. Where information is stored or processed
5.1 On the device
Ages Capture stores captured media, metadata, JSON sidecars, upload queue records, logs, setup values, and project records locally on the assigned device as needed for app functionality.
Local device storage may be used as a production backup, especially when network access is unavailable or uploads are still pending.
Device credentials are intended to be stored in the iOS Keychain. Runtime upload tokens should be kept out of logs and exported files.
5.2 Box
For current project workflows, Ages Capture uploads approved project media, JSON sidecars, and logs to the project's approved Box folder.
Box storage, access, sharing, retention, deletion, and audit settings may be controlled by the production/client's Box account, Box administrator, project policy, or applicable production agreement.
5.3 Cloudflare Worker broker / Ages Capture API
Ages Capture may use a Cloudflare Worker broker or an Ages Capture API domain, such as https://api.agescapture.app, to request short-lived Box upload access.
The broker is intended to:
- validate the app/device/project request
- hold Box app credentials server-side
- request Box access server-side
- return only a short-lived, project-limited upload token and approved Box base folder ID to the app
Video files are intended to upload directly from the iPhone to Box. They are not intended to pass through Cloudflare as normal video proxy traffic.
Cloudflare or other infrastructure providers may process request metadata such as IP address, request time, route, status code, user agent, and error information as part of standard hosting, security, abuse prevention, routing, and logging operations.
6. Data retention
6.1 During an active project
During an active project, Ages Capture may retain local app data on the device to support capture, upload retry, verification, troubleshooting, and production handoff.
This may include:
- captured media
- JSON sidecars
- thumbnails
- upload queue records
- daily logs
- master logs
- test/readiness reports
- setup values
- app settings
- local references to files and folders
By default, local media may remain on the device as a backup unless an authorized cleanup workflow removes it.
6.2 Local cleanup after verified upload
If a verified local cleanup feature is enabled by an authorized admin, the app may remove app-private local video copies after upload has been verified.
The app should not automatically delete media that is pending, uploading, waiting for Wi-Fi, waiting for connection, failed, retrying, missing required verification, or otherwise not confirmed as safely uploaded.
JSON sidecars, logs, upload queue records, and project records may remain locally for reporting, troubleshooting, verification, and production handoff unless removed through an approved cleanup workflow.
6.3 Project closure / project wrap
When a project is closed or wraps, Ages Productions Inc. or the production/client may disable new app access, deactivate the project, rotate credentials, disable device credentials, or stop additional uploads.
After project closure, data inside the Ages Capture app may be deleted through an authorized cleanup workflow, device management process, app reset, app removal, or future project-close cleanup tools. This is intended to help remove local project data from the device when it is no longer needed for production backup, troubleshooting, or handoff.
This local deletion process does not automatically delete copies that already exist outside the app, including files or records in Box, client storage systems, backups, exports, emails, screenshots, downloaded files, or other third-party systems.
6.4 Box and third-party retention
Files uploaded to Box are controlled by the production/client's Box environment and retention policies unless a separate agreement or authorized workflow gives Ages Productions Inc. the ability to manage deletion.
Ages Productions Inc. cannot guarantee deletion from systems outside its control, including client Box folders, client backups, client downloads, post-production systems, third-party storage, audit logs, legal holds, or other copies made by authorized production/client personnel.
6.5 Logs and reports
Daily logs, master logs, test reports, and upload records may be kept for the duration of the project and for a reasonable period afterward to support production/post handoff, troubleshooting, verification, dispute resolution, and project wrap.
The exact retention period may vary by production, client policy, Box configuration, legal/business requirements, and project agreement.
8. iOS permissions requested by the app
Ages Capture may request the following iOS permissions depending on enabled features:
- Camera: to record production video clips
- Microphone: to record audio with production video clips
- Location: to add capture-location metadata when enabled for the project
- Photos Add: to save an optional copy of captured media to Photos when this setting is enabled
- Photos Read: only if a current or future feature reads from Photos
The app should only request permissions needed for active app features. The user/device may deny certain permissions. If a permission is denied, related features may not work or related metadata may be unavailable.
9. Security practices
Ages Capture is designed to reduce the amount of sensitive cloud access stored on the device.
Current security practices include or are intended to include:
- Ages-issued device credentials stored in iOS Keychain
- Box client secrets kept off-device
- Box enterprise credentials kept off-device
- no Box developer token stored in the app
- short-lived Box upload tokens
- Box downscoped upload access where supported
- broker host validation
- project/device validation through the broker
- project active/inactive controls
- local-first recording so media is not lost if network access is unavailable
- no credential values in logs, CSV exports, JSON sidecars, Test Reports, or UI
- no committed secrets in the app repository
- app bundle audits before TestFlight where practical
No system can be guaranteed perfectly secure. Users should only use Ages Capture on authorized devices and should report lost devices, suspected credential exposure, unexpected upload behavior, or unauthorized access promptly.
10. User choices and project controls
Depending on project setup and device configuration, authorized users or admins may be able to:
- enable or disable location permission at the iOS level
- enable or disable optional Photos copy features, if present
- configure project/file naming values
- configure Assigned ID and Display Name
- configure upload settings such as Wi-Fi-only behavior
- review upload status and failure details
- retry failed uploads
- finalize or export logs
- perform or request authorized cleanup
- deactivate a project or device credential through the broker/backend workflow
Some controls may be limited to authorized admin users, project owners, Ages Productions Inc., or the production/client.
11. Data subject and privacy requests
Because Ages Capture is used in a production/client workflow, privacy, access, correction, deletion, or retention requests may need to be handled by the production/client or employer that controls the project.
Users may contact Ages Productions Inc. using the contact method listed below. Ages Productions Inc. may need to coordinate with the production/client, Box administrator, project owner, or employer to respond to requests related to project media, uploaded files, logs, or retention.
Ages Productions Inc. may not be able to delete or modify data controlled by a production/client, stored in the client's Box account, retained in client backups, subject to legal hold, or otherwise outside Ages Productions Inc.'s control.
12. Children and minors
Ages Capture is not a consumer app directed to children. It is intended for authorized production use.
If a production uses Ages Capture in a workflow involving minors, the production/client is responsible for ensuring that any required parent/guardian permissions, production releases, labor requirements, privacy notices, and legal requirements are handled according to the production's policies and applicable law.
13. Changes to this policy
Ages Productions Inc. may update this policy as the app, project workflow, client requirements, storage providers, or legal requirements change.
When material changes are made, the updated policy should be posted at https://agescapture.app/privacy. The effective date or last-updated date should be updated when the policy changes.
14. Contact
For privacy questions about Ages Capture, contact:
For requests about a specific production's media, retention, deletion, access, or Box storage, the production/client or project owner may also need to be contacted.
This policy is written for the current Ages Capture TestFlight and pilot workflow and for future client projects using the same app model. It should be reviewed by counsel and, where applicable, by the production or client's legal or privacy contact before public App Store release, broad client rollout, or use on productions with special confidentiality, union, child/minor, health, biometric, or regulated-data requirements.