Privacy Policy
Brand Teamwear Designer
This policy explains how this application handles information and how to contact us about privacy.
Information we process
Brand Teamwear Designer stores your team names, event names, player numbers, sport, uniform colours, patterns, emblem and sponsor choices, placement rules and project selections on your device. Language, tips, sync choices, references to uploaded exports and pending deletion identifiers are stored locally. Exported presentation images are created in temporary device storage and, when you request it, saved to Photos or passed to the iOS share sheet. The app does not read your photo library. Optional cloud sync sends project snapshots and exported PNG images to our backend. A random installation secret is stored in the device Keychain and sent over HTTPS for authorization; the backend stores a SHA-256 namespace derived from it, not the secret itself. Server records include resource identifiers and creation/update timestamps. Railway receives network requests, including IP addresses and ordinary connection information needed to host the service. There are no user accounts, advertising or analytics SDKs.
How we use information
Local processing lets you design, autosave, reopen, compare, check and export rugby and basketball uniforms offline. Optional server storage provides copies of projects and images for the same installation and supports deletion of those copies. The installation secret authorizes access to private records. We use request limits and minimal operational error information to protect availability and diagnose service failures. The public website serves this policy and health information without requiring a secret, cookies or a login.
Service providers and sharing
Railway hosts the application backend and its persistent storage and may process infrastructure and request logs while providing that service. The backend logs startup events and error request identifiers/codes; application code does not deliberately log authorization secrets, project bodies or image bodies. Infrastructure logging is controlled by Railway and is not claimed to have a fixed retention period here. There is no analytics, advertising, email delivery or external design service in the app. When you use Photos or the share sheet, Apple and recipients or apps you choose process the exported image under their own practices. We do not make private projects or exports publicly accessible; image retrieval requires the installation secret.
Data retention
Device projects remain until you delete them, remove the app or device storage is otherwise cleared. Temporary exported files may remain until data deletion or iOS removes temporary storage. Photos copies and copies shared to other apps remain under your control in those destinations. Server snapshots and images remain until you delete them using this installation; no automatic expiration is currently implemented. Operational logs may remain according to Railway infrastructure settings. We do not operate a separate application backup service or promise an infrastructure backup retention duration. If infrastructure backups exist, deletion from live storage may not immediately remove historic backup copies, which remain subject to the hosting provider lifecycle.
Deleting your information
You can delete individual projects in Projects. If this installation has used cloud storage, project deletions are queued locally for the next successful sync. Settings offers Delete all projects & exports, which deletes all live server records for the installation before clearing local projects when cloud storage has been used. If the server cannot be reached, the app reports failure and retains local data so you can retry. Deleting a project does not delete previously exported server images; use Delete all projects & exports to remove those images too. Deleting within this app does not remove images already saved in Photos or shared elsewhere. Uninstalling alone does not send a server deletion request. The Keychain secret is not a login and access cannot be restored after its loss. The privacy contact is fern.dacres@icloud.com; do not send the installation secret by email.
Permissions and your choices
Photos add-only access is requested only after you select Save to Photos. It is used solely to add the presentation image, not to browse existing photos. You can deny or withdraw permission in iOS Settings; projects remain saved and the share sheet is still available. No location, camera, microphone, contacts or notification permission is requested. Cloud sync is optional and initially disabled. You can disable further automatic sync in Settings; existing server copies remain until you request deletion.
Your privacy rights
You can view, edit, export and delete your projects in the app. Depending on applicable law, you may also have rights to access, correct, delete, restrict or object to processing, obtain a copy, or complain to a data protection authority. Contact fern.dacres@icloud.com for privacy questions or rights requests. We may need sufficient non-secret information to identify the relevant data; there is no email account directory and we cannot associate an email address with an installation automatically. We cannot recover authorization after the installation secret has been lost.
Security
The app uses HTTPS for backend communication, a cryptographically random installation secret in the device Keychain and server-side namespace checks on every private resource request. Local project writes are atomic and use iOS file protection. Server projects and images are stored in SQLite on a persistent Railway volume with input validation, quotas and request limits. The raw secret is not embedded as a common app credential and is not stored in the server database. These measures reduce risk but no storage or transmission system is guaranteed completely secure. There are no advertised security certifications.
Children’s privacy
The app is a design utility for team managers, coaches, designers and enthusiasts, rather than a service directed specifically to children. It does not require a child name, birth date or account. School-team examples are fictional design content. Avoid putting unnecessary personal information about players, especially children, into team names, event text or exported images. If you believe inappropriate personal data has been submitted, contact fern.dacres@icloud.com and use the in-app deletion controls where available.
Changes to this policy
We may update this policy when product processing or hosting practices change. The effective date on this page identifies the current version. Material changes will be reflected in the updated policy accessible from Settings and this public page. Review it before choosing optional cloud sync or sharing an export.