adbopVENUE STUDIO
ADBOP · EFFECTIVE 22 OCTOBER 2026
Data retention
Retention periods, account closure, encrypted remote buffers and copies on devices or in backups.
We apply POPIA's purpose and retention limits. The periods below describe the application's retention rules. Expiry stops access even if an expired database row is waiting for cleanup. Scheduled deletion depends on the hosting scheduler running; exceptional legal holds are restricted to information actually needed for the legal duty or dispute.
| Record | Retention and deletion |
|---|---|
| Accounts, venue details and settings | While the account is open. Account closure removes the account's live business/venue records and associated credentials. An Agent's confirmed closure includes all its managed venues and venue-client accounts. |
| Adverts and earlier music uploads | Until deleted or the account closes. A removed advert's file remains while an active publication still needs it, then is purged. Old music uploads remain private and are not playable. Account closure deletes associated server media. |
| Publications | While the account is open. Archived publications are eligible for pruning after 90 days, provided an active device/publication does not still require them. |
| Device state | Latest state replaces previous state; account/device deletion removes associated live records. Device credentials are revocable. |
| Website and support sessions | Website sessions last at most seven days; support visits at most one hour. Sign-out, password/security changes and account closure end sessions as described in Account security. |
| Codes and links | Pairing codes: three minutes. Signup/email/Agent codes: ten minutes. Password-reset links: one hour; verification links: 24 hours; invitations: 48 hours. Codes are single-use and access ends on consumption/expiry. Cleanup generally runs every ten minutes; consumed invitation/link records may remain up to 90 days for delivery/security reconciliation. |
| Phone-control frames and input | End-to-end encrypted payloads are temporarily stored in the private database. One current frame replaces the previous frame. Input expires after 15 seconds and is removed when polled. Disconnect, session replacement, device revocation or closure removes the session. Sessions expire after 15 minutes; remaining expired rows are purged by periodic cleanup, normally within a further ten minutes. No session decryption keys are stored by the relay. Encrypted copies may also remain in restricted backups until those backups expire. |
| Email queue and delivery records | Queued content is encrypted and erased on delivery or expiry. Completed delivery records are eligible for deletion after 90 days. |
| Failed sign-ins and lockouts | Lockouts last 15 minutes after the relevant limit; inactive counters are cleaned after a day. |
| Audit and support records | Application audit records and support notes are pruned after 730 days. Venue-linked records may be removed with the venue; retained account/admin audit records can be detached from deleted user identifiers. Necessary complaint correspondence may be retained until resolved and for an applicable claim period. |
| Payment records if paid service launches | Only required billing/tax/transaction records are retained for the applicable statutory period, generally five years for relevant tax records, and longer where a lawful audit, dispute or hold requires it. This does not justify retaining unrelated account content. |
| Hosting logs and backups | Restricted hosting logs and backups follow the hosting provider's configured retention. Deletion from the active application does not immediately remove an existing backup or provider log. We restrict restored data and reapply relevant deletion requests after restoration. Ask the Information Officer for the retention applicable to your data; we do not promise an unverified backup-erasure deadline. |
| Guest mode | Guest settings stay temporary and the isolated browser profile is cleared on exit. Connectivity checks produce normal hosting logs; websites you open process requests under their own notices. |
| Device and PC copies | Downloaded content/browser profiles may remain locally until the device is signed out, app/browser data is cleared or files are replaced. adbop cannot erase a disconnected device remotely. The app is unavailable offline and checks access again when connected. Signing out of the website does not sign out a music provider. |
Closing your account
In Account security, confirm the account name and current password. Agent confirmation also identifies the managed venues to be deleted and requires an acknowledgement. Closure removes sessions, venue-client/team accounts associated solely with those venues, adverts, playlists, publications and device credentials. It preserves an independent account or administrator identity that is not part of the closure. The confirmation says “Your account has been closed.” Clear disconnected devices and export any content you need before closure. Subscriptions capable of further charging must be resolved first. For access, correction, deletion or a justified retention concern, contact Andrew Harwood at drew@adsbop.com.
Operator and contact details
Andrew Harwood, Dillon Harwood and Thea Sinclair, trading as adbop.
Operated by Andrew Harwood, Dillon Harwood and Thea Sinclair.
Physical and service address: 44 Riviera Road, Uvongo/Margate, South Africa.
Telephone: +27836962435.
Information Officer: Andrew Harwood, drew@adsbop.com. General support: support@adsbop.com.
adbop is operated by Andrew Harwood, Dillon Harwood and Thea Sinclair, trading as adbop at https://adsbop.com. For questions, requests or complaints about this page, email support@adsbop.com.