Privacy Policy for Atraxis

Last updated: November 2026

1. Controller

The controller responsible for data processing within the meaning of the General Data Protection Regulation (GDPR) is:

Handcrafted Halloween Haunts e.K.
Am Schifferwall 2
21335 Lüneburg
Germany

Phone: +49 176 30348899
Email: info@handcrafted-halloween-haunts.com


2. General Information

The protection of your personal data is important to us. We process personal data exclusively in accordance with applicable data protection laws, in particular the General Data Protection Regulation (GDPR).

This Privacy Policy explains the nature, scope, and purpose of the processing of personal data in connection with the use of the Atraxis platform.


3. Purposes of Data Processing

Atraxis is a software platform for managing cast members, applications, costumes, availability, and staff scheduling.

Personal data is processed in particular for the following purposes:

  • Providing the platform
  • Managing user accounts
  • Authentication and login processes
  • Managing applications
  • Managing cast members
  • Planning and documenting assignments
  • Managing costumes
  • Storing, versioning and sharing documents (Atraxis Cloud)
  • Communicating with users
  • Handling support requests (Atraxis Support)
  • Activating and licensing devices for Atraxis Stage
  • Ensuring security and traceability within the platform
  • Statistical analysis of page views (audience measurement) to improve the website and platform
  • Fulfilling legal obligations

4. User Accounts

When using Atraxis, personal data required for the creation and management of user accounts is processed.

This may include:

  • Name
  • Email address
  • User role
  • Authentication data
  • Login and activity timestamps

Processing is based on Article 6(1)(b) GDPR for the performance of a contract or pre-contractual measures.


5. Application Management

If the application management functionality is used, the following data may be processed:

  • Name
  • Contact details (email address, phone number, and where provided postal address and social media profile)
  • Date of birth
  • Message or application text
  • Photos
  • Size information and other free-text details about the application
  • Notes and evaluations by the organization
  • Application status information

Photos are uploaded to a temporary area as soon as they are selected in the application form so that a preview can be shown. If the form is not submitted, these photos are deleted automatically after 24 hours.

Processing is carried out for the purpose of conducting the application process in accordance with Article 6(1)(b) GDPR.

Six months after an application is closed (acceptance, rejection, withdrawal, or no-show), it is anonymized automatically: name, contact details, date of birth, address, photos, free-text fields, and notes are deleted. Only statistical information (organization, event, season, status, and timestamps) is kept.


6. Contact Form and Support Requests

Contact form

On our website you can send us an enquiry about Atraxis via a contact form. The following data is processed:

  • Name
  • Email address
  • Event, attraction or company (optional)
  • Your message
  • Time of the enquiry

Your enquiry is stored in our database (Supabase) and additionally forwarded to our mailbox by email via Resend. To prevent abuse, your IP address is briefly used to limit the number of enquiries and is deleted after two days at the latest.

We use your details exclusively to process and answer your enquiry. The processing is carried out to take steps prior to entering into a contract pursuant to Article 6(1)(b) GDPR or on the basis of our legitimate interest in answering enquiries pursuant to Article 6(1)(f) GDPR.

Contact form enquiries are automatically deleted 12 months after receipt.

Support requests (Atraxis Support)

With an Atraxis user account you can send requests to our support team from the Planner and from Atraxis Account and follow how they are handled under “My support requests” in Atraxis Account. The requests are handled in Atraxis Support (support.atraxis.app). The following data is processed:

  • the internal ID of your user account and the name and email address from your account
  • the organization the request relates to (optional)
  • kind of request (bug, feature request, question), subject, description and – for bugs – your answers on whether the error happens once or keeps happening and how you noticed it
  • images you choose to attach (e.g. screenshots); metadata such as the location is removed in your browser before uploading
  • technical details sent automatically: the application and its version you send the request from, and your browser and operating system as a short label (e.g. “Chrome 131”, “macOS”), derived from the browser identifier (user agent); the full user agent is not stored
  • history of the request, including our support team's replies
  • internal handling details of our support team (priority, assignee, affected product areas, internal notes and change history), which are not visible to you
  • processing status and timestamps

The technical details are used to find errors; they are shown to you before sending and can be seen in your request.

So that support remains available even if the rest of the platform is disrupted, this data is stored separately from all other Atraxis data in a dedicated database at Neon, attached images in Neon's object storage (see section 13). Name and email address are taken from your user account for this purpose and updated when you use Atraxis Support. Only you and the Atraxis support team can see your requests.

Support requests are automatically deleted 24 months after they were closed, together with their attached images and technical details. The details taken from your user account are deleted once none of your requests are stored any more and you have not used Atraxis Support for 24 months.

The processing is carried out to perform the contract of use pursuant to Article 6(1)(b) GDPR or on the basis of our legitimate interest in handling requests pursuant to Article 6(1)(f) GDPR.


7. Cast Members and Staff Scheduling

As part of cast member management, the following data may be processed:

  • Name
  • Contact details
  • Address
  • Availability information
  • Team and position assignments
  • Assignment history
  • Communication data

Processing is carried out for the organization and execution of events as well as the administration of employment or contractual relationships.

The legal basis is Article 6(1)(b) GDPR and Article 6(1)(f) GDPR.

Documents and forms: Organizations can assign forms and contracts to people with access to the self-service portal for them to fill in (for example personnel questionnaires, consents or instructions). Which information a form asks for is determined by the respective organization, which is responsible for it (see section 23). We store the filled-in fields, a signature drawn in the browser, and who assigned, submitted, returned for correction or completed the document and when. Individual fields can be prefilled with your master data (for example name, address, date of birth) when you open the document; your profile is not changed by this. The drawn signature is a simple electronic signature; it does not replace any written form required by law. You and the organization's personnel management (by default owners, administration and HR) have access. You are notified by email about a new assignment or a return for correction; the email contains no form content. The organization's history only records the events, never form content. Filled-in documents are deleted 5 years after completion or submission, assignments that were never submitted 5 years after assignment or withdrawal.


8. Costume and Makeup Planning, Health-Related Information

To match suitable costume pieces, we collect clothing and size information (e.g., clothing, trouser and shoe size, height). This information on its own does not allow any inference about health status.

In addition, health-related information may be recorded. This is special category personal data within the meaning of Article 9 GDPR:

  • Allergies (voluntary; does not trigger an automatic warning)
  • Latex and silicone allergy and other notes for makeup
  • Restrictions such as claustrophobia, asthma, sensitivity to cold or intolerance of strobe light, and other notes
  • In the application process: information about a latex allergy

This information is used solely to protect your health in costume, makeup, and scheduling, for example to avoid materials you cannot tolerate or to not assign you to confined or cold areas.

Access to this information is limited to you and to the roles the respective organization has granted access to these fields (e.g., costume and makeup leads). Latex and silicone allergies are checked against the material information of masks and makeup: before you are assigned to a role whose mask or makeup contains a substance you cannot tolerate, a clear warning is shown. Planners without access to the allergy fields receive a derived safety notice based on your health information: they only see "Assignment needs clarification" - neither the allergy, the material, nor the mask or makeup concerned. This notice is health-related information too; only roles with the separate permission "See makeup intolerance safety notice" can see it (by default administration, planning, and makeup leads; the organization can adjust this). If such an assignment is nevertheless made knowingly, this is logged with a fixed reason, the confirming person, and the time, and deleted after 12 months. The confirmation is only stored together with the assignment itself. We also store when you last saved the latex, silicone, restriction, and glasses information yourself in self-service. Until you have done so, this information is shown as "not answered" rather than "no", and we ask you for it.

For the makeup team, latex and silicone allergies appear in makeup planning, in the makeup report, and in the makeup artists' makeup plan as a work instruction ("Do not use: latex" or "silicone"), not as a diagnosis. Health-related information is not included in exports of the member list.

For mask issuance we store who received which mask on which event day and in which role, that the issuance form has been signed, who handed the mask out and took it back (each with the time), which defects were found on return and how they were handled. The purpose is to document where the masks are and what condition they are in. The organization's makeup managers have access; makeup artists see the masks to be handed out on the respective day together with the names of the people assigned. This information is deleted 5 years after the mask was returned or the defect was handled.

If you work as a makeup artist, your organization's makeup managers record your working times (artist times): on which event day you checked in and out and when, who recorded or changed the times, and whether they have already been billed. The purpose is billing your work. Only the organization's makeup managers have access; changes are logged in the history. Billed times can no longer be changed. The times are deleted at the end of the year following the respective season (season 2026: on January 1, 2028).

Health-related information is never sent to AI services and is removed before any transmission to our error monitoring.

We are currently determining, together with our data protection advisers, the legal basis under Article 9(2) GDPR and which of these details are mandatory or voluntary. This Privacy Policy will be updated accordingly. You can have health-related information corrected or deleted at any time (see Section 20).


9. Audit Logs and Activity Records

To ensure the security, traceability, and integrity of the platform, changes to relevant records are logged.

This may include:

  • Time of change
  • Type of change
  • Affected record
  • User performing the action

Processing is based on our legitimate interest pursuant to Article 6(1)(f) GDPR.


10. Document Storage (Atraxis Cloud)

Organizations can store files in the Atraxis Cloud, manage them in folders and link them to events, attractions or event dates. Files are either uploaded by users or generated and filed automatically by Atraxis, for example an attraction's duty roster as a PDF after it has been published. Such documents contain the names of the scheduled people and their roles.

For every file we store, besides its content, the file name, type and size, all earlier versions, the time of each version, the person who uploaded it or triggered the automatic filing, and its links. Which other personal data a file contains is determined by the respective organization (see Section 23).

Only signed-in members of the organization whose role has access to the cloud can access it. Folders can additionally be protected so that they, with all subfolders and files, are only visible to certain roles, for example only to staff administration. On upload we automatically check file type and size; the content of files is not analyzed and not sent to AI services. Automatically generated documents are created within our application with the access rights of the person triggering them; no further service provider is involved.

The files are stored with Supabase in Frankfurt am Main (see Section 13) and are only delivered through short-lived, signed links.

Share links: Authorized members of an organization can pass individual files or folders on to third parties via a link. Every link expires after 90 days at most, can be revoked at any time and can optionally be protected with a password; content released only to staff administration cannot be shared by link. For a link we store only a non-reversible check value of the link and, if applicable, of the password, the expiry date, the person who created it and the number and time of the last views, but no IP addresses or device data of the viewers. To protect against password guessing, the IP address is stored with every password attempt and deleted after two days at the latest. After a correct password a cookie is set (see Section 15). Share pages are not indexed by search engines.

Processing is carried out to perform the user relationship based on Article 6(1)(b) GDPR and, where files contain personal data of third parties, on behalf of the respective organization. Storing the IP address on password attempts is based on our legitimate interest in securing share links pursuant to Article 6(1)(f) GDPR.

Files, including all earlier versions, are kept until the organization deletes them. Deleted folders and files remain in the cloud's trash for 30 days and are then permanently deleted with all versions.


11. Licensing of Atraxis Stage

Atraxis Stage is activated per device; each organization has a booked number of device slots. For activation, Stage shows a code that an owner or administrator of the organization confirms in Atraxis Account.

For this we store the device's public key, the device name (usually the computer name, which may contain a person's name), the times of activation, last connection and release, who confirmed or released a device, and the issued licences with their term. Owners and administrators of the organization can see this information in Atraxis Account. For activation requests and code entries, the IP address is stored briefly to limit abuse.

The licences are digitally signed (see section 18) and stored on the device so that Stage can also be used without an internet connection. A licence only contains internal identifiers of the organization, the activation and the device, and its term.

Processing is carried out to perform the user relationship on the basis of Article 6(1)(b) GDPR; the IP address is stored on the basis of our legitimate interest in secure activation pursuant to Article 6(1)(f) GDPR.


12. Hosting by Vercel

The platform is hosted using Vercel. Server-side processing of the application takes place in a data center in Frankfurt am Main, Germany.

Technical access data may be processed during use of the platform, including:

  • IP address
  • Browser information
  • Device information
  • Server log data

Errors are recorded in the server log data with technical details only (affected function, error type, internal identifiers of the organization and record, and code location). Error messages, form contents, names, e-mail addresses and health information are removed before logging. Only the platform's technical administrators have access to the server log data; Vercel deletes it automatically once the contractually agreed retention period has expired.

A Data Processing Agreement pursuant to Article 28 GDPR has been concluded with Vercel (Vercel Inc., USA).

Where personal data is transferred outside the European Union, such transfers are based on appropriate safeguards pursuant to Article 46 GDPR, in particular the European Commission's Standard Contractual Clauses.

Vercel has its security measures confirmed regularly through independent SOC 2 Type 2 audits. The data center operators used by Vercel are certified, among others, under ISO 27001.

Audience measurement with Vercel Web Analytics

To see which pages of the website and platform are visited and how often, we use Vercel Web Analytics. The required script is loaded from our own domain and reports each page view to our own domain, where Vercel analyses it. The following is processed:

  • the page visited, as a page type only (e.g. "/organizations/[organizationId]/events"): internal identifiers, access codes of share links and query parameters are removed in your browser and never transmitted
  • the referring website, if you came to us from another website
  • browser, operating system and device type, derived from the browser identifier (user agent)
  • the country, derived from the IP address

The IP address is not stored. To group page views by the same person within one day, Vercel derives a non-reversible hash from the IP address and browser identifier, which is recalculated daily; recognition across several days or across other websites is therefore not possible. Vercel Web Analytics does not set cookies and does not create entries in browser storage. The script only checks whether an entry "__va_attribution" exists in browser storage; Atraxis does not create it. Names, e-mail addresses, platform content or membership of an organization are not transmitted, and we do not link the analysis to your user account. We only receive aggregated figures, e.g. views per page type, country or browser.

The processing is based on our legitimate interest in designing and improving the website and platform according to need, pursuant to Article 6(1)(f) GDPR. Vercel deletes the data once the contractually agreed retention period has expired. The Data Processing Agreement and Standard Contractual Clauses mentioned above apply. You may object to audience measurement at any time (see Section 20); technically, you can also prevent it by blocking scripts under "/_vercel/insights/" in your browser.


13. Databases and Authentication via Supabase and Neon

We use Supabase for database services, authentication, and backend infrastructure.

Data is stored in a data center in Frankfurt am Main, Germany.

A Data Processing Agreement pursuant to Article 28 GDPR has been concluded with Supabase (Supabase Pte. Ltd., Singapore). Where personal data is processed outside the European Union, for example during support access, this is based on the European Commission's Standard Contractual Clauses.

Data transfers are encrypted, and stored data is protected through technical and organizational security measures.

A backup copy of the database is created daily and kept for seven days. Uploaded files (e.g., photos) are not included in these backups; deleted files therefore cannot be restored.

Support database at Neon

We store the data of Atraxis Support (see section 6) separately from the rest of the platform in a database at Neon, attached images in Neon's object storage (not public, only retrievable through Atraxis). Data is stored in a data center in Frankfurt am Main, Germany. You still sign in with your Atraxis user account; Neon does not receive any credentials.

A Data Processing Agreement pursuant to Article 28 GDPR has been concluded with Neon (Neon, Inc., USA). Where personal data is processed outside the European Union, for example during support access, this is based on the European Commission's Standard Contractual Clauses. Data transfers are encrypted.


14. Error Monitoring via Sentry

We use Sentry to detect, analyze, and resolve technical errors. No performance or usage analysis takes place.

As part of this monitoring, the following data may be processed:

  • Browser and device information
  • Error type, internal error codes, and stack traces
  • Technical context data about the page or request involved (without query parameters)
  • Internal identifiers of the affected organization and records

Before an error report leaves our application, credentials, cookies, and form contents are removed. The text of error messages is not transmitted unless it is a fixed, technical standard message without content data; this keeps contact details, health-related information, and free text out of error reports. Sentry additionally filters sensitive values on its servers. IP addresses are not stored.

Processing is based on our legitimate interest in error resolution and the secure operation of the platform pursuant to Article 6(1)(f) GDPR.

Data is processed and stored within the European Union (Sentry EU Data Residency). A Data Processing Agreement pursuant to Article 28 GDPR has been concluded with Sentry (Functional Software, Inc., USA). Where data is nevertheless transferred to the United States, this is based on the EU-U.S. Data Privacy Framework and the European Commission's Standard Contractual Clauses.


15. Cookies and Browser Storage

Atraxis does not use tracking, analytics, or advertising cookies. All entries listed here are set and read exclusively by Atraxis itself and are not transmitted to third parties. Audience measurement with Vercel Web Analytics works without cookies and without its own entries in browser storage (see Section 12).

Cookies

NamePurposeContentRetention
atraxis-auth-token or sb-…-auth-token (possibly split into .0, .1, …)Sign-in and maintaining the session; valid for atraxis.app and the Atraxis applications under this domain (e.g. account.atraxis.app, support.atraxis.app), so that one sign-in covers all of themAccess and refresh token of the sign-inuntil logout, at most 400 days
atraxis-auth-token-code-verifier or sb-…-auth-token-code-verifierSecuring sign-in and password reset linksRandom valueuntil the process is completed
themeSelected appearance (light/dark)light or dark1 year
localeSelected languagede or en1 year
activeOrganizationId, activeSelfServiceOrganizationIdMost recently selected organizationInternal identifier of the organization1 year
costumeAssignmentsEventId_…, makeupAssignmentsEventId_…, makeupScheduleEventId_…, makeupAvailabilityEventId_…, makeupArtistMappingEventId_…, makeupReportsEventId_…Most recently selected event in costume and makeup planningInternal identifier of the event1 year
atraxis_share_…Password-protected share link: remembers the correct password for this linkCheck value (not the password)12 hours

Browser storage

NamePurposeContentRetention
assignments-matrix:selected-team:…, assignments-matrix:name-format, assignments-matrix:overview-collapsed:… (sessionStorage)Display settings in planning: selected team, name format, collapsed sectionsInternal identifier of the team or the selected settinguntil the browser tab is closed
cast-manager:auto-unassigned-dismissed:… (localStorage)Not showing notices in planning again once readInternal identifiers of the notices readuntil deleted in the browser
atraxis.cloud.view, atraxis.cloud.sortKey, atraxis.cloud.sortDirection (localStorage)View and sorting in the Atraxis CloudSelected settinguntil deleted in the browser

The login cookies are strictly necessary for using Atraxis; signing in is not possible without them. The same applies to the cookie of a password-protected share link: without it the password would have to be entered again on every visit. The other entries only store settings and selections you made yourself so that they are kept for your next visit. Atraxis can also be used without them; the selection then has to be made again each time.

The legal basis for storing and reading these entries is Section 25(2) No. 2 TDDDG, as they are necessary for the function you explicitly requested - signing in or keeping your settings. The associated processing of personal data is based on Article 6(1)(b) GDPR for signing in and on our legitimate interest in user-friendly operation pursuant to Article 6(1)(f) GDPR for the settings. You can delete all entries at any time via your browser settings.


16. Email Delivery

We use Resend to send emails.

The following data may be processed:

  • Name
  • Email address
  • Content of sent messages

Processing is carried out exclusively for the delivery of system-related emails, notifications, and invitations, and for forwarding contact form enquiries to our mailbox.

A Data Processing Agreement pursuant to Article 28 GDPR has been concluded with Resend (Plus Five Five, Inc., USA).

Resend is a company headquartered in the United States. Transfers are based on the EU-U.S. Data Privacy Framework, under which Resend is certified, and the European Commission's Standard Contractual Clauses.


17. AI Service from OpenAI

We use an AI service from OpenAI to draft reminder emails to cast members whose profile information is incomplete.

Only the names of the missing profile fields (e.g., "shoe size") and the reminder number are sent to OpenAI. Names, contact details, profile contents, and health-related information are not sent; the name is inserted within our application only after drafting. If only health-related information is missing, no AI service is used.

In addition, when adding consumables, the makeup team can take up to four photos of a product or its barcode; the AI service suggests product details such as name, brand and package size from them. Only these photos are sent. Before sending, they are downscaled and stripped of all metadata (for example location and device), and they are stored neither by us nor in our OpenAI account. The feature is meant for product photos; users are asked to photograph only the product. If a barcode is readable, we additionally query the open product database Open Beauty Facts; only the barcode number is sent, no personal data.

On request ("Search the web"), the AI service can also search the internet live for a material's manufacturer page and shop offers. Only the material's brand, product name and package size are sent, plus the country "Germany" for relevant results – no photo and no personal data. The links and prices found are only displayed; only a link the person explicitly chooses is stored.

The contracting party is OpenAI Ireland Ltd.; a Data Processing Agreement pursuant to Article 28 GDPR has been concluded with OpenAI. Processing may also take place in the United States; transfers are based on the European Commission's Standard Contractual Clauses. Requests are not stored in our OpenAI account and are not used to train AI models. OpenAI may retain requests for up to 30 days for abuse detection.

For billing and cost control, we count per organization how often each AI feature was used and how many tokens and web searches it consumed. Only these figures are stored, together with the organization, feature, model and time – neither content nor the person who used the feature. The entries are deleted automatically after 24 months.

Processing is based on our legitimate interest in efficient communication and materials management pursuant to Article 6(1)(f) GDPR.


18. Signing of Stage Licences by Amazon Web Services

Licences for Atraxis Stage are signed in the AWS Key Management Service in the Stockholm region, Sweden. The signing key never leaves this service. Only the licence details are transmitted, i.e. internal identifiers of the organization, the activation and the device, and the term; names, email addresses or device names are not transmitted.

A Data Processing Agreement pursuant to Article 28 GDPR is in place with Amazon Web Services (Amazon Web Services EMEA SARL, Luxembourg). Should data nevertheless be transferred to the United States, this is based on the EU-U.S. Data Privacy Framework and the European Commission's Standard Contractual Clauses.

Processing is based on Article 6(1)(b) GDPR.


19. Data Retention

Personal data is stored only for as long as necessary for the respective processing purposes or as required by applicable legal retention obligations.

Once the purpose no longer applies, the data will be deleted unless statutory retention obligations prevent deletion.

In particular, the following retention periods apply:

Data TypeRetention Period
User accountsuntil contract ends
Applicationsanonymized 6 months after closing
Application photos from forms not submitted24 hours
Audit logs24 months
Reminder emails to cast members12 months
Assignments confirmed despite an allergy warning12 months after confirmation
Mask issuance (hand-outs, returns, defects)5 years after return or handling of the defect
Artist times (check-in, check-out, billing status)Season plus 1 year (deleted on January 1 of the year after next)
Filled-in documents and forms (incl. signature)5 years after completion or submission, otherwise after assignment or withdrawal
Notification delivery log30 days after sending
Contact form enquiries12 months after receipt
Support requests (Atraxis Support) including attached images and technical details24 months after closing
Account details in Atraxis Supportonce no support requests are stored and after 24 months without use
Files in the Atraxis Cloud (with all versions)until deleted by the organization
Deleted files and folders of the Atraxis Cloud30 days in the trash, then permanently
Aborted uploads to the Atraxis Cloud1 day
IP addresses on password attempts for share links2 days at the latest
Activation requests for Atraxis Stage (codes, verification requests)1 day after expiry
Issued licences for Atraxis Stage30 days after the licence expires
Released or deactivated Stage devices365 days after release
Log of Stage device licensing730 days
IP addresses on activation requests and code entries for Atraxis Stage1 day
Database backups7 days

These periods are enforced by an automatic daily deletion run.


20. Rights of Data Subjects

Under applicable law, data subjects have the following rights:

  • Right of access (Article 15 GDPR)
  • Right to rectification (Article 16 GDPR)
  • Right to erasure (Article 17 GDPR)
  • Right to restriction of processing (Article 18 GDPR)
  • Right to data portability (Article 20 GDPR)
  • Right to object (Article 21 GDPR)
  • Right to withdraw consent at any time with future effect

21. Right to Lodge a Complaint

Data subjects have the right to lodge a complaint with a supervisory authority regarding the processing of their personal data.

The competent supervisory authority for our company is:

The State Commissioner for Data Protection of Lower Saxony
Prinzenstraße 5
30159 Hannover
Germany


22. Changes to this Privacy Policy

We reserve the right to amend this Privacy Policy where necessary due to technical, legal, or organizational changes.

The current version is always available within the platform.


23. Responsibilities of Organizations

Atraxis is used by organizations such as theme parks, event operators, museums, and other institutions to manage applicants, employees, cast members, and staff scheduling.

The respective organization is generally responsible for the lawfulness of the personal data entered and processed within Atraxis.

Where Atraxis processes personal data on behalf of an organization, such processing is carried out exclusively on the basis of a Data Processing Agreement pursuant to Article 28 GDPR and in accordance with the organization's instructions.

Data subjects may contact either the respective organization or us. Where we process personal data solely on behalf of an organization, we will forward such requests to the responsible organization.