1. Scope
This policy applies to the current HubForMusic testing site and its live features, including EPK Maker, Project CRM, Venue Finder, Song Links, Artist Sites, Calendar, and Setlist Studio.
2. No account system
The current version does not provide user accounts, password logins, subscriptions, or payment processing. The app itself also does not currently include advertising or a built-in analytics dashboard.
Depending on where the site is hosted, the hosting provider or deployment owner may still keep standard server, network, or access logs.
3. Data stored in your browser
Some tools store working data locally in your browser so the app can keep functioning during use.
- EPK Maker stores the current draft payload in browser storage, including entered text and uploaded images converted for preview/export use.
- Project CRM stores board data, cards, notes, custom fields, and uploaded attachments in browser storage.
- Calendar stores calendar items, tags, custom fields, and file attachments in browser storage.
- Setlist Studio stores show details, song rows, poster settings, and calculated runtime output in browser storage.
- Venue Finder stores temporary local search and photo caches in browser storage to improve speed and reduce repeat requests.
- Song Links and Artist Sites may use session storage to temporarily remember the most recently generated public URL during the current browser session.
4. Data sent to HubForMusic servers
Two tools currently send submitted data to server-side endpoints:
- Song Links sends release titles and platform URLs to the link creation API so a public smart link can be generated and stored.
- Artist Sites sends artist names, bios, links, YouTube embeds, and uploaded image data so a public artist page can be generated and stored.
Based on the current implementation, that data may be stored in server files or a configured key-value storage provider, depending on deployment settings.
5. Public pages and shared content
Song Links and Artist Sites are intended to create public-facing pages. If you submit data to those tools, the resulting public URL may expose the submitted content to anyone who has the link.
Do not submit confidential information, private personal information, or content you do not want publicly accessible through those publishing tools.
6. Third-party services used by current features
The current site integrates with external services that may receive limited request data when features are used.
- Venue Finder queries mapping and venue-related services including OpenStreetMap/Overpass, Nominatim, Photon, Wikidata, and Wikimedia Commons.
- Venue Finder can request approximate device location from your browser, but only if you choose the location feature yourself.
- Artist Sites may display YouTube embeds supplied by the user.
- Site assets may load from third-party providers such as Google Fonts or Leaflet CDN where used by the page.
Those third-party services operate under their own terms and privacy policies.
7. Clipboard and device access
The current site may request clipboard access when you use copy buttons for generated links. It may also request file access when you choose images or attachments, and geolocation access when you ask Venue Finder to use your location.
These actions are initiated by user interaction rather than automatically in the background.
8. Retention and deletion
Browser-stored data remains on the device until cleared by the browser, replaced by newer data, or removed by the user.
Server-stored public content may remain available until removed by the deployment owner or overwritten according to the behavior of the relevant tool and storage system.
9. Security and testing status
This is a testing-stage deployment. Reasonable care may be taken, but no guarantee is made that storage, transmission, uptime, or deletion workflows are production-complete.
Use caution and avoid submitting sensitive or regulated information.
10. Requests about data
For testing builds, any privacy, correction, or removal request should be directed to the person or team operating the specific deployment you are using.
11. Changes to this policy
This policy may be updated as the product changes. The live functionality of the site should be treated as the baseline for interpreting this testing policy.