Who we are
Shrooms Tribe is operated by Deep Play Studio LTD, company number 14781253, at 102–104 Katherine Road, London, England, E6 1EN. Contact info@deepplaystudio.com about this policy or your data.
This policy covers the current free-first app and its service. This version has no Apple sign-in, paid credits or in-app purchases. Some artwork may be unavailable to save.
Information we use
Browsing loads catalogue information and artwork from our service. Search words and filters are sent to return results. Our providers process the network requests needed to deliver this content.
When you first add a favourite, save feed preferences or request a download, the app creates a guest identity. The app stores its identifier and credential in device-only Keychain storage. The server keeps the identifier and a hash of the credential. There is no sign-in or guest-recovery service in this version.
Favourites and selected interests and colours belong to that guest identity. They provide Saved and preference-based recommendations. The service also records favourite and download-grant events with guest and artwork identifiers and a time. We use those events for diagnostics and support. A download grant records authorised access, not a completed Photos save. Removing a favourite does not remove an earlier event.
The app does not send optional view or search analytics events. It still sends searches needed to return results. We do not use these operational events for advertising or cross-service profiling.
If you email support, we receive your email address, message and any attachments you choose to send so we can handle the request.
For UK data protection purposes, our basis for this processing is our legitimate interests in providing the guest features you request, operating and troubleshooting the service, and responding to support or privacy requests. You may object to processing based on legitimate interests.
On your device
The app caches recent catalogue and search results, the latest search words and filters, favourites and preview thumbnails. A successful search replaces the search snapshot; otherwise it can remain until the system removes the cache. These caches are excluded from device backup and may be stale. This flow does not cache private download URLs or downloaded original files.
Private history contains metadata for up to 30 recent views and 30 completed export records, not image files or Photos-library identifiers. Export history is shown for the current guest and does not prove an image remains in Photos. History is excluded from device backup. Clear it in Settings → Private history. Theme and motion preferences are stored in local app preferences.
Photos and sharing
Saving an eligible artwork requires a download grant and add-only Photos permission. The app does not read your photo library or automatically set system wallpaper. You can browse and preview without Photos access and manage permission in iOS Settings.
Sharing prepares a public artwork preview and title for the destination you choose. It does not share your guest credential or private download grant. Temporary share files are removed after completion or cancellation, or during later cleanup after an interrupted session. The destination handles its own copy.
How long information is kept
Guest information
We keep your guest identifier, credential hash, favourites and preferences until you delete the guest. There is no automatic inactivity expiry in this version. An inactive identity, or one whose credential is lost, can remain on the service until it is deleted.
Operational events
There is currently no automatic age-based expiry for favourite and download-grant events. Guest-linked events remain in the service database until the guest is deleted. Removing a favourite does not remove the earlier event. These event records are separate from the favourites list.
Support correspondence
Email messages and attachments are stored separately from guest records. The app does not apply a timed deletion rule to email, and correspondence can remain after a request is resolved until it is separately removed. Deleting a guest does not delete support mail. Contact us to ask for email correspondence or attachments to be removed. The mail provider, forwarding destinations and email clients can hold separate copies.
Backups and recovery copies
We have not configured scheduled database backups or point-in-time recovery for this app. This does not establish that the hosting provider has no recovery copies. The current service does not maintain a separate restore-deletion suppression record. Guest deletion removes the live service records described below; it does not certify erasure from every provider-held recovery copy.
Guest deletion does not immediately remove provider-operated logs or recovery copies. Their processing is described below. We do not promise that all provider-held copies disappear at the same time as live guest records.
Delete a guest account and data
Open Settings → Delete guest account and data and review the confirmation. The service removes the guest record, its favourites, preferences and associated account and event records. After server confirmation, the app removes that guest’s cached favourites, export receipts and stored credential.
Recent-view history remains separately clearable. Deletion does not remove public catalogue artwork, images already in Photos or copies shared elsewhere. Manage those copies in Photos or the destination where you shared them.
Interrupted deletion requests
For seven days after confirmed deletion, the service keeps a SHA-256 hash of the former credential and an expiry time solely to confirm an interrupted deletion response. This proof has no guest UUID, plaintext credential or profile. It is not used for analytics or to recreate an account. Retrying does not renew its expiry.
The proof stops being accepted at seven days. A maintenance process removes expired proof; processing work, downtime or database errors can delay physical cleanup. This proof only confirms an interrupted deletion response; it is not a record for restoring or recreating the guest.
If deletion is interrupted, the app keeps the pending credential and pauses guest actions so you can retry. A rejected or expired credential is not treated as confirmation of deletion. Removing the app or starting another identity does not itself delete the old server identity.
Service providers and logs
We use Railway for the app service and PostgreSQL database, Cloudflare R2 for catalogue artwork storage and delivery, and Hostinger for inbound support-email delivery. Providers process connection and service information needed to handle requests, which can include IP addresses, request times and paths, user-agent information and service results. Email routing and email clients may hold additional correspondence copies.
Our application request tracing records method, path, request ID and response information. It does not intentionally add request bodies, search query strings or session credentials to those request spans. Provider-operated access and security records are separate.
Our current Railway plan makes 30 days of log history available to us. A log-history window is not a guarantee of physical erasure. Providers may hold separate records for service operation, security and recovery under their own retention processes. The in-app deletion action does not itself erase those records. Contact us if you need help with information held in those systems.
Questions and privacy requests
Email info@deepplaystudio.com for privacy questions or help with your information. Do not send session credentials or private download links. We cannot promise to recover a lost guest identity.
The in-app deletion action is the normal way to initiate guest deletion; email is not a replacement for that action. You can also revoke Photos permission through iOS Settings, clear local history in the app and manage images or shared copies separately.
Depending on where you live, you may have rights to ask for access, correction, a copy, restriction or deletion of your information, or to object to processing. Contact us to exercise these rights. In the UK you can also complain to the Information Commissioner’s Office.
Support and practical help ↗