TENALIA · 2026-09-27
Updated: 27 September 2026 · free public beta · access wording corrected on 13 October 2026
TENALIA is operated by Christian Tenuzzo as an individual.
Christian TenuzzoContact and privacy: support@tenalia.ch
This notice describes TENALIA's free public beta with registration without a personal invitation or invitation code, and publicly accessible pages. Accounts are intended for ages 16 and above, with prior guardian permission for minors. Paid creator subscriptions and a general newsletter are not currently part of this operation.
We process email address, sign-in method, age group, country of residence, invitations and document acknowledgements, plus session, MFA and security data for access and account protection. Music and community functions use profiles, songs, artwork, rights/AI declarations, favourites, playlists, follows, reactions, comments and notifications. Support messages, reports and technical logs support assistance, security and review of violations. Hosting and security providers process technical connection data such as IP address, time and browser information when pages are accessed.
Deliberately published creator profiles, songs and visible comments are public. Private drafts, account settings, favourites and notifications are not public; authorised operators may process them where required for operation, support or security. Creators see their own followers in management. Country of residence is not displayed on the public profile or inferred from IP address. Aggregated audience-country statistics suppress groups below five listeners and show larger groups in ranges of five, not lists of individual listeners.
Sign-in and protection functions use cookies or browser storage. For separate public play counting, reporting a play stores a random browser identifier in the “tenalia_play_visitor” cookie for up to 365 days and processes it as a hash. Quality Plays for charts instead use the internal account ID of signed-in listeners; guests do not create Quality Play sessions. This is not anonymous processing. The browser also stores your analytics choice, up to five recent search terms and last seen dashboard counts without automatic expiry, until you change them or clear the relevant browser data. Separately, optional product analytics measures limited login/upload events and active usage/listening time only after your explicit consent. Those events contain random session identifiers, not names, email addresses or song contents; small groups are suppressed and raw data is deleted within seven days. No advertising tracking or screen recording. On your first visit, choose “Allow analytics” or “Continue without analytics”. Change your choice at any time under “Privacy settings” in the footer without limiting access. The choice applies to this browser; clearing browser data resets it and optional analytics remains off until renewed consent. Turning it off discards unsent events; previously submitted data remains subject to the retention period. The switch does not disable separate play counting, security logs or technically necessary processing.
We use Supabase for sign-in, database and profile media (Zurich project region), Vercel for the web application, Cloudflare R2 for music media and Turnstile for bot protection, Resend through Supabase SMTP for account email, and Hostpoint for domain and support email. Our backups are encrypted before storage in Google Drive. GitHub Actions and a private Discord channel support operational alerts. Despite regional storage, providers and subprocessors may process data abroad, particularly in EU/EEA countries, the USA and, for Supabase, Singapore. Provider documents below describe their processing and intended transfer mechanisms. A fully confirmed country- and service-specific contract review is not yet available; this notice is not evidence that all transfers have been reviewed. Please send questions about specific recipients and safeguards to support@tenalia.ch.
When you request translation, DeepL receives the selected public text (comment, community post, creator bio, song description, lyrics or public playlist description), without additional account data. The original remains unchanged. Comment translations are cached server-side; translations of the other text areas remain only in the open view. Google sign-in exchanges the account information required to sign in; it does not open public registration. Social-media connections are used only at a creator's express request, not for automatic public posts without approval. Password checks send Have I Been Pwned only the first five characters of the password hash, never the password or email address.
Account data and content are retained for use of the service and handling requests. Deletion requests are handled via support@tenalia.ch; automatic self-service account deletion is not currently available. Our retention policy provides for ordinary support email for 90 days after case closure, redacted attachments for 30 days and closed moderation cases normally for twelve months. Necessary contract/consent records are retained for their purpose and normally for no more than three years afterwards; specific disputes or legal duties may require a documented exception. Full automatic implementation is not yet active; reviews and deletion requests are handled manually. These periods do not claim automatic cleanup has already occurred.
Our encrypted backup is configured for retention review after seven days. Older backups still exist; seven days is not currently a guaranteed final deletion period for all copies. Backups are not used as active user data. Deletions and withdrawals must be reconciled before restoration. The current Supabase Free plan includes no accessible project backups. Internal provider copies, cloud versions and trash may have different periods; their complete retention periods have not yet been confirmed.
You may request access, correction and deletion and, where applicable, restriction, portability and object to processing. You may withdraw consent for the future. We appropriately verify identity before sensitive disclosures. Where GDPR applies, necessary contractual processing uses Article 6(1)(b), legally required processing (c), and purpose-limited security/operational processing legitimate interests under (f); consent-dependent processing requires (a). This does not replace any required cookie consent. Otherwise applicable Swiss data protection law governs. You may complain to the FDPIC or a competent data protection authority, particularly in your EU country of residence. Contact support@tenalia.ch about your rights.
We update this notice when processing changes. A privacy notice is not blanket consent. Publication gives no new consent for existing accounts and changes no previous recorded acknowledgements. New registrations record the displayed document version and time.
The separate total counter stores daily counts without names, account IDs, IP addresses or countries. A short-lived session hash prevents duplicates; no new tracking cookies or individual sign-in histories. Optional usage analytics and consent remain unchanged. Daily counts are kept for up to twelve calendar months. Activation requires database, retention and privacy review; complete coverage is not guaranteed. Replay protection requires a fresh password/Google sign-in within ten minutes.
TENALIA uses this separate server-side total counter for operational community-growth and return-usage statistics, independently of optional product analytics. The operator has decided to rely on the legitimate interest in data-minimised operational statistics (Article 6(1)(f) GDPR where applicable); Swiss data protection law otherwise applies. No advertising, individual user profiles or new browser identifiers. The temporary session hash is deleted by hourly maintenance, normally within 90 minutes; daily totals are kept for at most twelve calendar months. Privacy questions and objections: support@tenalia.ch.
Raw data is deleted within seven days. Turning measurement off discards unsent events; already sent data follows the retention period. Summaries are restricted to authorised operators with two-factor authentication. Protected daily summaries of successful and failed logins without session identifiers are retained for up to twelve calendar months. Small groups remain suppressed. We ask for consent again for this change; an existing refusal remains effective.
