Privacy notice

The iPhone/iPad version 1.0 is currently available on the App Store. Contact, call-sheet and email features described as the next update belong to the prepared version 1.0.1 and will become available after Apple approval. Mac is coming soon.

This notice explains what personal data is processed when you use this website, contact us or use the DREHSTAND app. The website presents the app and provides help and contact options. Production data is not uploaded or edited through the website.

Last updated: 13 October 2026.

1. Controller and contact

Julian Aschenbrenner
Waldfriedenstraße 15
86161 Augsburg
Germany
Email: aeschju@drehstand.com

This contact is responsible for the website and enquiries to the app provider. When DREHSTAND is used within a film production, that production determines the personal and production data it contributes, permitted recipients and retention. The production's own privacy information also governs that processing. Providing the app does not give the app provider general read access to your private or shared CloudKit content.

2. Website and external links

Website operation with Squarespace

This website is provided using the Squarespace website builder. Visits involve processing technical connection and usage data, including IP address, requested pages, times, browser and device information and, where applicable, referring page and technical errors. This enables delivery, secure operation and troubleshooting.

The Public Sans font and other website resources are delivered through Squarespace and its content delivery network.

Our legitimate interest is a reliably accessible, secure information and support website. Processing necessary for this is based on Article 6(1)(f) GDPR. Recipients are Squarespace and technical service providers used to operate the site.

Squarespace processes data partly on behalf of the website operator and partly for its own purposes, particularly platform security. Details of these roles are in the Squarespace privacy information and Data Processing Addendum.

Processing may also occur outside the European Economic Area, particularly in the United States. For transfers to Squarespace, Inc., Squarespace describes the EU–US Data Privacy Framework and supplementary Standard Contractual Clauses. Information about these grounds and requesting a copy is in the linked documents.

Squarespace determines retention according to the type of data and processing purpose, especially service provision, security, legal obligations and legal claims. No single fixed deletion period is promised here for all website access data.

Cookies and visit data

Non-essential Squarespace cookies are restricted for this website; the activity log is disabled. Google Analytics and Meta Pixel are not embedded. Restricting analytics cookies does not prevent every kind of technical data collection. Squarespace may still process technical access data and count page views in its platform statistics. Technically necessary storage serves operation and security; where strictly necessary to provide the requested website, section 25(2)(2) TDDDG applies.

Ordinary links, for example to the App Store or Apple and Google privacy information, lead to other providers' services. You access the external website only when opening its link. Its privacy information then applies.

3. Email, support and content reports

If you write to aeschju@drehstand.com, we process your sender address, name where provided, message content, attachments and technical email data. This is used to answer the enquiry, investigate errors or handle a report. Send only necessary information and redact uninvolved people and confidential production information in screenshots and attachments.

We use Google Workspace Business Standard to receive and send email. The contracting party for the email service is Google Cloud EMEA Limited, 70 Sir John Rogerson’s Quay, Dublin 2, Ireland. Recipients are Google and technical providers engaged for email operations, especially data centre and support providers. Google's Cloud Data Processing Addendum describes processing Workspace customer data on our behalf. Google's subprocessor list identifies companies, tasks and locations.

Email data may also be processed outside the European Economic Area, particularly in the United States. According to Google's current transfer information, transfers of EU/EEA data to Google LLC in the United States rely on the EU–US Data Privacy Framework and the associated adequacy decision. For other restricted transfers, Google's terms provide Standard Contractual Clauses where no other lawful transfer mechanism exists. Further information and relevant safeguards are available in the linked documents; you can also request a copy of safeguards relevant to your data through aeschju@drehstand.com. Storage exclusively in Germany or Europe is not promised.

For general enquiries and reports, the legal basis is Article 6(1)(f) GDPR. The legitimate interest is answering enquiries, resolving problems and handling abuse. Where an enquiry concerns agreed services or their preparation, Article 6(1)(b) GDPR applies; for legal obligations, Article 6(1)(c) GDPR applies.

Enquiries are stored for handling and necessary follow-up. Deletion criteria are closure of the matter, outstanding questions and any need to fulfil legal obligations or address legal claims. Without a continuing purpose, the enquiry and attachments are deleted. Longer retention where needed applies only to the necessary information.

A report may require review of the content concerned. Necessary disclosure limited to the matter may be made to the responsible production contact or, where legally required, competent authorities. Production and the app provider do not generally read private chats.

4. App: data and purposes

DREHSTAND supports call sheets, comparisons of planned and actual times, production collaboration, messages, personal timesheets, a calendar across productions and a private work overview. Depending on the features you use, the following data is processed:

Call sheets with dates, scenes, locations, planned times, recorded end times, changes, original PDFs and undo data; in the next update, archived daily versions and separate weekly PDFs with calendar-week assignment;
Production names, membership assignments, roles, shares and technical Apple account and record identifiers;
Profile name and role and, in version 1.0, an optional phone number; the next update adds an optional email address, separate visibility settings and private contact shares. Production admins may also maintain unit assignments and further member information;
Team messages, personal messages, sender assignments and timestamps;
Personal and department scene notes;
Timesheet days with work start, end, breaks, optional notes, manually entered locations and the name on the timesheet; weekly submission also includes submission time, version and sharing assignments;
Assignment data with member, production, date, role, call sheet/unit links, call time, location, assignment notes, timesheet requirements, reminder deadline, request/acceptance/decision states and submission/receipt status;
Offered weekly wages with offer, version and recipient assignment, plus personal digital/paper timesheet preferences, actual paper submission reports and receipt confirmations;
Optional private weekly wages in euros with production and calendar week, and the personal overviews and export files derived from them;
Local settings, block lists, unsaved changes, backups and exported files; in the next update, user-reviewed email drafts, selected recipients, cover messages, signatures and temporary EML files.

Data comes from your entries and imports, shared production content and Apple's technical account and sharing information. The app does not read your address book or record GPS location. Assignment and timesheet locations are entered as text, from manual entries and where applicable a linked call sheet, not GPS tracking.

Purposes are the app features you use and collaboration organised by the production. Where the provider processes personal data to provide an app service you requested, Article 6(1)(b) GDPR may apply. Processing by a production, such as employment data and working time records, requires that production's appropriate legal basis; using the app does not replace this assessment.

5. Processing on the device

PDFs are initially read on your device. The PDF reader is included in the app. Compatible devices may additionally use local analysis with Apple's Foundation Models and text recognition. The PDF content is not sent to an external AI API for this. The described app version also does not use Apple's Private Cloud Compute for this purpose.

When you apply an import, the original PDF is additionally stored in iCloud and may be accessible to authorised production members. Successful import removes the local import copy. Failed or unapplied imports may remain locally. Demo mode uses a separate local session without cloud shares. Device backups and exported files are additionally subject to your selected storage and backup arrangements.

6. iCloud, production sharing and recipients

Cloud features use Apple CloudKit private and shared databases, the iCloud account signed in on the device and private invitations. DREHSTAND creates no separate app sign-in account. There is no publicly readable call-sheet database or proprietary production-content server. The local demo requires no iCloud sign-in.

Recipients of shared content are the authorised people in the production. Production owners manage invitations and rights. In the new cloud structure, each member receives a separate author area in which only its assigned author writes; authorised other members read. The production owner manages these team zones and technically has access to their content. Older productions use the previous shared area until the owner migrates them.

Profile name and role are visible within authorised productions. In the currently available version 1.0, an optional phone number may also be visible in reachable productions.

Contacts in the next update: For phone and email separately, choose “Production admins only” or “All members of my productions”. New profiles default to “Production admins only”. Existing phone profiles without the new visibility settings may retain their earlier member visibility; check this choice in Profile settings.

Production admins receive contacts through separate private iCloud shares owned by the crew member, with read-only access for confirmed admins. The ordinary crew directory receives only contact fields intended for members under the saved visibility. Changes must be successfully saved and synced. If old copies cannot be confirmed as cleaned, a visibility restriction may be rejected or remain pending; the app does not confirm a new restricted visibility in that case.

Personal scene notes use an unshared private area. Members of the relevant department and production admins can read and edit department notes.

Personal chats are shared only between the two people involved. Each owns a sending area; the other receives read access. Production receives no share of these personal messages.

Personal timesheet drafts remain account-private. Only an explicitly submitted week is shared as a separate version with confirmed production admins. The current submission flow sends only days assigned to the selected production; other productions' entries and private weekly wages are excluded.

Crew assignments, individual call times, locations and assignment notes are in the production share and technically readable by its members. Only confirmed production admins edit them and confirm receipt of a timesheet actually submitted. Assignment notes are not confidential messages to one person. The personal calendar assembles your firm assignments and separately marked requests from these records. Planning is independent of an existing call sheet.

An offered weekly wage and the individual's acceptance or decline are in separate read-only shared areas: the offer area belongs to the publishing admin, the response area to the crew member. Recipients are only that person and confirmed production admins. Shared production planning contains technical references, not offered amounts or response texts. A firm confirmation remains valid only if the currently verified acceptance relates to the same offer. Older productions must be migrated by their owner to the secure author structure for this.

Your digital/paper submission preference remains unshared in your iCloud area. An actual paper submission report is passed to authorised production management only through your explicit action; management confirms receipt independently.

Optional weekly wages are stored in a separate unshared private CloudKit area of your account. Production receives no share. You decide separately for personal PDF exports: an Activities PDF may contain wages and totals; a timesheet PDF may contain a weekly amount for the selected production on a separate page. Without that selection, both PDF exports exclude wages; CloudKit weekly submissions always exclude private weekly wages. Recipients of an exported file depend on your chosen sharing and storage method.

Apple provides cloud storage, account functions and, where applicable, push notifications. For users in the European Economic Area, Apple names Apple Distribution International Limited in Ireland as the responsible legal entity in its privacy information. Apple also describes processing outside the EEA and the Standard Contractual Clauses used for it. More information and contact options are in Apple's privacy policy and the iCloud terms.

7. Revoking access and sharing limitations

Rights revocation must successfully sync with the affected cloud shares. Sync runs at launch, on returning to the foreground, periodically while visible and through manual rights checks. Revocation can remain pending offline, during cloud errors or while a required owner app is inactive. Production owners cannot centrally revoke personal chats or weekly shares owned by others. In the next update, this also applies to private contact shares owned by crew: the owning crew member’s app must be opened online and reconcile changed admin roles to adjust or revoke contact access.

Recipients may already have exported, photographed or otherwise stored content they read. Later revocation or deletion in DREHSTAND does not recall independent copies.

8. Chat protection and reporting

Blocking a production chat or person is stored on the device used. This includes hashed assignments of the iCloud account, production and person and the displayed person label. Blocking hides messages on this device and prevents further sending here. It deletes no cloud messages, revokes no share and does not sync between devices.

A local text filter checks certain explicit threats. It may hold back outgoing texts and replace recognised incoming content with a notice. It is not a complete content filter. It does not make decisions about you with legal or similarly significant effects.

“Report message” creates a local preview with message, sender assignment, timestamp, production/chat context, report reason and optional reporter details. It is not automatically sent. In version 1.0, you select an application and recipient yourself; provider reports can be sent to aeschju@drehstand.com.

In the next update, after your review, the app prepares a complete report draft addressed to that support email. A supported configured mail composer or compatible mail client sends it only when you choose. Without a composer, a complete EML is exported; export is not delivery. Local chat-demo reports are labelled fictitious and can only be exported.

9. Storage, deletion and export

The app has no general automatic deletion period. Production and personal content remains in its cloud area until the responsible person carries out the appropriate deletion action. Personal production data must also be handled according to the responsible production's retention and deletion rules.

Your profile: profile deletion removes name, role and phone and, in the next update, email and associated contact visibility from your own profile and reachable securely assigned profile/contact copies. The action is “Delete my profile” or “Delete profile”. The name for new timesheets is also reset. Unreachable or older copies can leave cleanup pending and require the responsible owner app. The app shows pending cleanup; in the next update, a new profile cannot be saved until cleanup is confirmed.
Your Apple/iCloud sign-in and production memberships remain. Admin-maintained member details, personal notes, chats, timesheet days, submitted weeks and private weekly wages are separate records with their own management or deletion actions. Remove personal scene notes at the relevant scene. Profile deletion does not recall exported copies.
Your messages: after confirmation, delete your own message texts within a selected chat. Other people's texts are not removed. Older archives may require a confirmed deletion request; the app shows deletion as pending until implemented.
Timesheets: delete a personal day individually. This does not change a submitted week; withdraw it separately. Withdrawal clears its submitted contents and removes other participants from the weekly share.
Private weekly wages: delete a personal weekly amount in Activities after confirmation. Working hours and submitted weeks are not removed. Technical version/deletion markers remain for conflict protection; previously exported PDFs are not recalled.
Assignment planning: production admins edit crew and deselect members for a day. After confirmed sync, the updated personal calendar no longer displays that assignment. Earlier timesheets and exports are separate records. Assignment data is deleted with the production areas managed by the owner.
Call sheets and productions: owners can delete their own call sheets or entire productions they own. Production deletion removes production areas managed by that owner. Private chats, personal profiles, own timesheets and separate weekly submissions belonging to other accounts are not all removed by this action.
Local and exported files: removing the app may delete local app files. Delete exported files and backups separately at their storage locations. Uninstalling does not automatically delete cloud content.

Individual deletion actions leave technical identifiers and version/deletion markers. They prevent older changes from restoring removed content and help assign pending cleanup actions. These markers are not automatically removed after a fixed period in the current version. Stored locations, personal notes and unapplied import copies also currently have no general automatic cleanup period.

If you lose access to an area or deletion remains pending, contact the responsible production owner or the support address above. The provider can delete only data it actually has access to and has no general access to private iCloud content. Statutory rights to deletion and restriction apply independently of the technical menus.

10. Optional notifications and technical storage

With notifications enabled, the app uses Apple's push service and private iCloud change subscriptions. Local settings and comparison states control display on your device. Notifications may show unit and scene numbers on the lock screen. Restrict or disable notifications and previews in System Settings. New requests and explicit production decisions may trigger a local notification after successful sync. Offered amounts, names and assignment notes are not shown on the lock screen for these notifications. Immediate delivery is not guaranteed.

Optional timesheet reminders are scheduled locally from your confirmed assignments and deadlines. Technical reminder identifiers and a limited history of already displayed reminders are stored per account on the device; refresh limits that history to the most recent 90 days. Reminders contain no wages or assignment notes. Cloud sync updates or removes scheduled reminders; changing accounts removes pending and displayed app notifications. Changes or submissions on other devices take effect only after the next successful sync. There is no guaranteed remote push delivery or central server-side deadline monitoring.

The app locally stores technically required settings and states, such as language, view options, blocking and unsaved changes. Required storage serves the functions you request (section 25(2)(2) TDDDG).

The described app version contains no advertising, tracking SDKs or usage analytics of its own. These functions require no location or address-book permissions.

11. Your privacy rights

Where statutory requirements are met, you may request access, rectification, erasure, restriction and data portability. For processing based on legitimate interests, you may object on grounds relating to your particular situation. You can withdraw consent for the future. Use the contact above or the contact for the production responsible for your production data.

You may complain to a data protection supervisory authority. For private entities in Bavaria, the relevant authority is in particular the Bavarian State Office for Data Protection Supervision (BayLDA), Postfach 1349, 91504 Ansbach, Germany. You can also submit a complaint through its online complaint channel. Contact the authority.

12. Optional information and changes

Phone and, in the next update, email in the crew profile are optional, as are support enquiries and optional production contacts. Without contact details, a specific enquiry may not be answerable. Cloud features require a suitable iCloud account and necessary shares; the local demo is an alternative. The provider does not perform automated decision-making with legal or similarly significant effects.

This notice will be updated when the app or the services and data flows actually used change.

13. Next update: call-sheet documents and email drafts

Prepared version 1.0.1 processes additional version information and archived original daily call-sheet PDFs, plus separate weekly PDFs with calendar-week assignment. Current and previous daily PDFs and weekly PDFs are production documents for authorised production members. A weekly call sheet is a guideline and does not become individual daily planning.

Authorised admins can maintain the production name and optional website, phone, contact person, contact email, emergency number, additional contacts and information. These production details are visible within the authorised production and with its assignments/requests. They are separate from crew-profile contact visibility; crew cannot edit the production profile.

A call-sheet email draft processes confirmed contacts of selected crew and the current daily PDFs of all units for one production and chosen date. Recipients are prepared as Bcc. A cover message, sign-off and verified production contacts, including an optional emergency number, form the draft. Old daily versions and weekly PDFs are not automatically attached.

The app has no email server and does not automatically send. You review recipients, content and attachments and trigger sending in a supported configured mail composer or compatible mail client. Without a supported composer, especially on Mac, the app exports a complete EML with recipients, text, signature and embedded PDFs. Exporting or opening a draft is not delivery confirmation. The local call-sheet demo only exports drafts with fictitious call-sheet recipients.

Your chosen recipients and mail service have their own processing and retention. The provider's support mail service is described in section 3; it is not a central production-email service. Emails and attachments already sent cannot be recalled by deleting a profile or app data. Drafts/exports may also need deletion at their storage locations. New cloud features depend on successful sync of the relevant iCloud shares.