> For the complete documentation index, see [llms.txt](https://docs.simplebooth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.simplebooth.com/platform/data-processing-practices.md). # Data Processing Practices This overview provides a high-level summary of Simple Booth's data handling practices. These practices are subject to change. For specific regulatory compliance needs or detailed security questionnaires, please contact our support team directly. We can provide a list of data sub-processors upon request for customers subscribed to the [**Select plan**](https://www.simplebooth.com/plans). *** ### Storage & Security * **Data Residency**: All data and backups are stored in the United States, specifically within the AWS region US East 1 (Ohio). * **Encryption**: * **In Transit**: All data is encrypted using TLS version 1.2. * **At Rest**: Our primary database is encrypted using AES-256. *** ### Data Retention & Deletion * **General Retention**: We retain data indefinitely by default to ensure your historical event data remains available. * **Manual Deletion**: Users can delete their entire account at any time. * **PII Purging**: For users on the [**Select plan**](https://www.simplebooth.com/plans), tools are available to purge Personally Identifiable Information (PII) at-will. Once initiated, data is typically deleted within a few hours, though it may persist in encrypted backups for up to 14 days. * **Participant Requests**: Participants may request the removal of specific photos or records by emailing . *** ### Information Collected #### Participant Data * **Required**: Photos or videos, depending on your booth configuration. * **Optional**: Email addresses and phone numbers used for digital delivery. * **Custom Data**: Any specific fields added to your "Data Capture" forms for marketing purposes. {% hint style="info" %} You can run a booth using only QR code delivery to avoid capturing any emails or phone numbers. {% endhint %} #### Customer (User) Data * **Account Info**: Any PII entered during sign-up, in account settings, or provided during the sales process. * **Digital Identifiers**: We track IP addresses for account logins and generate unique device identifiers to manage your HALO hardware. * **Analytics**: We use Google Analytics to track how participants interact with galleries. This data is used for performance trends and is not linked to specific individuals. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.simplebooth.com/platform/data-processing-practices.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.