Privacy Notice

Launch notifications

19 October 2026

If you ask for a launch notification, Technabit e.U. processes your email address, chosen language, request and confirmation times, and the version of the purpose text you accepted. We use this information with your consent to confirm the request and send one BoothWall launch announcement, not a general newsletter.

Confirm using the link in our email within 24 hours. Unconfirmed requests are deleted after 7 days. Confirmed requests are kept for at most 180 days after confirmation. You can withdraw consent and remove your request using the removal link in our confirmation or launch email, or contact hello@boothwall.com. Withdrawal does not affect earlier lawful processing.

Cloudflare hosts the request records and protects the form. Resend processes the recipient address and message to deliver email. Processing is not promised to stay exclusively in the EEA. Existing copies in an inbox cannot be recalled. We do not add open or click tracking to these messages.

To limit abuse, the service briefly stores a purpose-specific, keyed identifier derived from the network address, not the raw address, for up to 24 hours. The form is optional, does not grant product access, and does not require an account. Your rights and our contact details in this notice also apply to these requests.

1. Responsibility and contact

Technabit e.U. – Development Studio, owned by Danijel Dedić, Riedelstraße 1/10, 6330 Kufstein, Austria, is responsible for processing host-account, billing, service-security and website data for its own purposes. Contact: hello@boothwall.com.

For event content processed on a host’s instructions, we act as a processor where data-protection law applies to that relationship. The organiser is responsible for deciding the purposes of collection and display and informing attendees. A strictly personal or household event may fall outside some controller obligations; that does not remove our own responsibilities for our service operations.

The Host Data Processing Agreement describes processing on behalf of hosts. Contact us if you are unsure who should handle a request; we can help identify the relevant wall and organiser.

2. Information processed

Guest contributions

A photo, an optional caption, any selected category, and operational information such as wall/photo identifiers, upload time, approval and removal state, reactions where available, and retention deadlines. Guests do not need to provide an account, name or email simply to contribute a photo.

Photos can contain personal information about the uploader and other people, as well as embedded metadata in the uploaded original. A guest viewing copy is not the same file as that original.

The upload process includes a declaration about showing the photo. It does not establish the uploader’s authority to give consent for everyone pictured. The organiser must provide the information and obtain permissions required for the event’s actual use.

Host accounts and connected displays

Verified email and profile details; enabled sign-in identifiers and protected credential records; account, membership, invitation and session records; wall settings; and display-pairing, device-name, connectivity and command records needed to manage connected screens.

A co-host invitation contains the invited email address and is valid for seven days. The host can revoke or resend it. Acceptance requires signing in with the invited email address.

Purchases, support and withdrawal

Order and subscription details, billing references, currency and amounts, invoice references, the agreed document version and agreement evidence, withdrawal statements and correspondence, and records needed to resolve a refund or other obligation.

Stripe receives payment information on its hosted page. We receive payment and billing information needed to administer the purchase; we do not provide a BoothWall form for entering card details.

Security and technical requests

Cloudflare processes network/request information to deliver and protect the service. BoothWall uses a pseudonymous abuse-control identifier derived from the sender’s IP address with a server-held secret, date and purpose. It is not anonymous: an address may be tested against it by someone who has the necessary secret.

Security emails. When we email you about sign-in or account-security activity, the email can show when it happened, the browser and operating system used (for example "Chrome on macOS") and an approximate city and country for that request, as Cloudflare's network estimates them from the connection. The location can be wrong, and we don't store your IP address for it. We keep the browser, operating system and approximate location in our security record and queued email copy for 30 days, or until your account closure completes if that is sooner, and then delete them; the record of the event itself stays. Copies already delivered to an inbox are not recalled. To notice a sign-in from a new browser, we also keep an unreadable fingerprint of each browser and operating system you have used (at most 20), deleted when your account closure completes.

3. Purposes and legal bases

We process account and plan information to provide and administer the contract, or take requested steps before it (GDPR Article 6(1)(b)). Billing, accounting and other mandatory records are processed to comply with legal obligations (Article 6(1)(c)).

Service security, abuse prevention, handling correspondence and establishing or defending claims can be based on our legitimate interests (Article 6(1)(f)): keeping the service and users safe, responding to requests, and resolving disputes. You may object to processing based on legitimate interests.

Event-content processing follows the organiser’s documented instructions. Where consent is the organiser’s legal basis, it must cover the actual audience and uses and can be withdrawn for future processing. Hosts may have another valid basis depending on the event and their relationship with attendees. This notice does not choose that basis for every host.

Providing the account and transaction information necessary for a purchase is required to operate that account or purchase. Guest photos, optional captions and optional sign-in providers are choices; do not upload information you do not want processed in the ways described.

4. Who can view event content

The host determines the approval mode and audience settings. If approval is required, pending photos are not ordinarily shown to guests. A host may instead enable publication of uploads without individual review.

Approved photos can be visible to people with the wall’s address and on its connected displays. A wall that is not listed in the showcase is unlisted, not access-controlled by a password. Someone can forward the link.

Recap sharing is a separate setting. Switching it off restricts the recap route; it does not make the wall’s other approved-photo views private.

When guest-original access is off, guests receive a generated viewing copy rather than the approved original through the covered media routes. When it is on, those routes may supply the approved original. Authorised management and paired-display paths can retain access to originals.

These controls do not prevent screenshots, saving a delivered image, sharing a link, or retaining a copy already obtained. The service does not revoke files held by another person or device.

5. Optional AI assistance

Where offered and enabled by the host, a thumbnail supplied during upload and the wall’s category labels are sent to Cloudflare Workers AI to produce review suggestions, including image/category and caption suggestions. The guest’s caption is not sent as the model prompt input in this pipeline.

The thumbnail is not independently guaranteed to represent the uploaded original. Suggestions can be wrong and are not a content-safety assurance. AI suggestions do not themselves approve or reject publication; the host’s publication setting and moderation decisions govern that.

Suggestions are associated with the photo and included in its deletion process. This processing is not used by BoothWall to make decisions producing legal or similarly significant effects about an individual.

6. Providers and international processing

Cloudflare provides hosting, storage, databases, service delivery and email; Workers AI is used only for enabled AI assistance. Stripe provides payments and associated billing/security services. Google participates if you choose Google sign-in.

These providers can also act for their own security, compliance or other independently determined purposes, as explained in their notices. Stripe and Google are not treated as our event-photo sub-processors merely because they are used for payments or sign-in.

Processing is not restricted exclusively to Austria or the EEA. Transfers that require safeguards must be covered by an applicable mechanism, such as European Commission standard contractual clauses or an adequacy decision covering the recipient and transfer.

Information about the safeguards applicable to a particular transfer can be requested from hello@boothwall.com.

7. Storage and security

Photos, thumbnails and viewing copies are stored in Cloudflare R2. Associated application data is stored in Cloudflare databases. We use transport encryption, access controls, scoped account/display authority and deletion processes appropriate to the service.

No absolute security, screenshot prevention, EU-only hosting, independent security certification, or zero-retention by every provider is promised by this notice.

The service permits brief private caching of guest viewing copies and instructs browsers not to cache original-media responses. Already downloaded images, browser memory and display-local copies may persist independently. Deleting a photo does not recall those copies.

8. Retention

Photos and walls

The purchased plan states the photo-retention period. Event Pass retention is anchored to the scheduled event end; subscription photo retention is anchored to upload. The service records deadlines, restricts further access after expiry, and runs background deletion of media and associated operational data. Failed storage deletions are retried.

Removing a photo or wall initiates its deletion process. A minimal record and necessary transaction references may remain. Deletion does not recall recipients’ existing copies.

Accounts and closure

Account information is retained while needed to operate the account. Account deletion removes the profile, invitations and credentials through the closure process, subject to unresolved obligations and lawful retention.

Once closure actually completes, a minimal closure contact record, including the email address, is kept for 30 days before deletion. This prevents an older in-flight action restoring the closed identity. Stable internal identifiers and required financial records can remain.

Financial and other evidence

Invoices and accounting records are generally retained for seven years from the end of the relevant calendar year, and longer where Austrian tax rules require it for pending proceedings.

Agreement versions, withdrawal statements and records needed to resolve an outstanding purchase or claim are kept separately where necessary to demonstrate the transaction, meet a legal obligation or establish/defend a claim. Their period depends on the record’s purpose, applicable legal period and whether a matter remains open; it is not an indefinite right to keep the whole account.

Security and abuse-prevention records are retained only as needed for the relevant operational/security purpose or an active investigation. Contact us for the applicable retention information about a particular record.

9. Cookies and browser storage

BoothWall uses necessary cookies and local browser storage for sign-in, identity checks, purchase recovery and display pairing where applicable. On HTTPS, identity cookies use Secure, HttpOnly and SameSite protections and are restricted to the management host. The sign-in flow cookie lasts up to ten minutes; sessions end according to their expiry or revocation.

Purchase recovery information can remain in the tab’s session storage while a purchase is unresolved. A previous sign-in may have used the legacy bw_session cookie.

The reviewed website and app do not include analytics or advertising trackers. Fonts are served from our pages. Google sign-in and Stripe payment pages have their own processing and notices.

10. Requests, removal and account deletion

A guest can remove the submitted photo from the immediate upload confirmation screen while that removal capability remains available. Leaving or reloading it, or starting another upload, can lose that capability. There is no account-based list of the guest’s previous submissions.

The host can remove photos. You can also contact the host or hello@boothwall.com. Tell us the wall and photo concerned; avoid sending more personal information than necessary. We may ask for proportionate information to identify the content or verify authority.

Hosts can request account deletion in Account → Delete account. Recent identity verification is required. The receipt in that tab reports progress and unresolved work. Submitting the request does not mean erasure has finished; payment or legal obligations can delay completion.

11. Your rights

Subject to the conditions of applicable law, you may request access, correction, erasure, restriction, portability and information about safeguards, object to legitimate-interest processing, and withdraw consent for future processing without affecting earlier lawful processing.

We respond without undue delay and generally within one month. Where a lawful extension is needed for complexity or volume, we explain it within the first month. You may complain to the Austrian Datenschutzbehörde or the supervisory authority for your habitual residence, workplace or the alleged infringement.

For event content controlled by a host, we will assist with the request or direct it to the organiser where appropriate.

12. Changes and contact

We publish a dated version when this notice changes. A material new use of personal data requires its own lawful basis and any notice required by law; publishing a new notice is not a substitute for that.

Privacy contact: hello@boothwall.com.