Controller and roles
The controller for account management, security and service delivery is Sabatino Astolfi, trading as SABBA Productions. Contact: info@sabbaproductions.com. No Data Protection Officer (DPO) has been appointed. For personal data about cast, crew or other people included in a project, the roles of the production and SABBA depend on the circumstances of processing and any agreements that apply.
Access and account data
Access uses invitation codes and requires a username and password, not a first name, surname or email address. The system processes a username, internal identifier, creation date, status, password hash and sessions. Passwords are salted and hashed with scrypt; the token is stored on the device in IndexedDB and its hash on the server.
Account and project invitations record a label, code/hash or identifier, role, permissions, project and creation, expiry, use or revocation dates. The server records access type, device label, creation and last access. Failed sign-ins use temporary in-memory IP counters with configurable retention (900 seconds by default); the reviewed code does not store them in a persistent table.
Version 3.4.0 source provides a ZIP download under Settings → Privacy and personal data of data they can access, including account information and attachments from their projects subject to permissions; passwords/hashes, invitation codes, tokens and 2FA secrets are excluded. The source provides a deletion request after data download. For an account, the request is verified with a password, immediately blocks access and signs out devices. The controller sees a counts-only preview, not private content, and completes deletion. Projects transferred before the request remain with the recipient who accepts; projects not transferred are deleted. An administrator account cannot request its own deletion through this flow and must transfer management.
Project content and data
The app stores information created or uploaded for a production: scripts and notes, scenes, characters and crew, departments, any contact details entered, props, costumes, vehicles and effects, locations, shooting schedules, call sheets, shot lists, slates and takes, continuity, lighting setups, reports, chat, invitations and permissions, exports, files and images. Records may include an author display name, project identifiers and creation or change dates. Users may enter third-party personal data into content and attachments; the system does not automatically filter it.
Data are stored locally for offline use in IndexedDB (sabaslate), including records, the synchronization queue, files not yet uploaded, metadata and session. Some preferences use localStorage; writing drafts use sessionStorage. The service worker caches the app shell and selected documents, not API responses or project data. When connectivity returns, the client synchronizes changes with the server. Clearing browser data may remove local copies and changes that have not yet synced.
Version 3.4.0 source includes a tool for selective removal of access, contacts, photos and files after explicitly identifying them and reviewing a preview; the system does not match data to a person by name alone. Selected personal data are removed from history and earlier versions, while unselected creative content and operational data remain. Deleting a file removes it from all references in the project. Affected devices must sign in again when reconnecting and discard older offline changes; devices that remain offline and exports already downloaded cannot be erased remotely. Selected text may also appear in a screenplay or chat: review the preview because removal can affect creative text. The app does not delete a screenplay solely because its author leaves the crew.
Purposes and legal bases
Creating and managing accounts, authentication, projects, collaboration, synchronization, recovery and export; proposed bases: providing the requested service (GDPR Article 6(1)(b)) and, for security and abuse prevention, legitimate interests (Article 6(1)(f)). For free accounts, SABBA records activity time and last access to assess use of the service during testing and guide improvements. The legal basis is the legitimate interest in improving the service (GDPR Article 6(1)(f)). These data are not used for marketing or individual profiling. For personal data about people entered into projects, the project controller is responsible for the legal basis and notice to those people, according to the roles set out in any agreements between the parties, where applicable.
Server, recipients and external services
The SABBA server is managed on a NAS in Italy, as stated by the controller. Cloudflare Tunnel is used to reach the server; Cloudflare processes network requests and may set the __cf_bm cookie for bot protection.
The weather feature sends the location name from the server to Open-Meteo geocoding, then uses the resulting latitude, longitude and requested date to retrieve a forecast. The code caches geocoding responses for 30 days and weather responses for one hour. Open-Meteo states that individual API logs are kept for 90 days.
No calls to external AI or advertising services were found in the application code reviewed.
Retention and deletion
Version 3.4.0 source defaults, configurable by the server, are: change history 365 days; screenplay history 365 days; resolved conflicts 90 days; completed deletion-request records 30 days; revoked/expired session cleanup every 15 minutes. Failed-login counters remain in memory for 900 seconds by default. If enabled, the code provides daily access-log files deleted after 7 days without IP, query, body or token.
Encrypted full archives are retained for no more than 30 days; a new backup is planned before expiry. Copies may contain data during the stated retention period.
A technical journal outside the database retains identifiers, operation and transfer timestamps, not removed content or credentials; it is used to reapply deletions after restore and is included in encrypted full backups.
Rights and requests without a registered email
Version 3.4.0 source provides a data download and deletion request under Settings; for access, rectification, restriction or objection, users may contact info@sabbaproductions.com. Because accounts do not require an email, the controller must define a proportionate identity check without asking for passwords or invitation codes. An in-app request immediately blocks access; the controller completes permanent deletion after reviewing the preview. For third-party data in projects, the production that determines purposes must provide the notice and handle requests, according to the roles set out in any agreements between the parties, where applicable. Users may lodge a complaint with the Italian Data Protection Authority (Garante).
Security and automated decisions
Version 3.4.0 source includes scrypt password hashes, permissions by role and section, session tokens, temporary in-memory limits on sign-in attempts and security headers. Deletion requests use a separate journal that reapplies removals after a restore; if an error occurs, the server may block access until processing is complete. The code provides daily access-log files deleted after 7 days without IP, query, body or token when logging is enabled. Cloudflare may automatically classify requests for bot protection. No SABBA automated decisions with legal or similarly significant effects on users were found.
Updated 1 November 2026. For privacy requests: info@sabbaproductions.com.
Official sources reviewed
For requests: info@sabbaproductions.com