Privacy Policy
Version: 1.0
Effective date: 31 October 2026
Language: English
1. Controller and scope
The controller is Riccardo Consolandi, operator of Tape Music Stories and PNAM. For data-related requests: riccardo.consolandi.eng@gmail.com.
This policy covers the editorial website, PNAM Library, accounts, and model publication and management. It distinguishes these activities from local work carried out with PNAM Studio and audio processing in RealNAM. Accessible features depend on service availability and the release used.
2. Data processed
Browsing and security. Servers, proxies and hosting process the technical data needed to receive requests, such as network address, requested resource, times and errors. Application protections against abuse use counters and derived references; these are not automatically considered anonymous. The application does not maintain a dedicated collection of user agents to profile visitors. Infrastructure logs are separate from application data.
Accounts and profiles. Data processed includes email, username, password hash, identifiers, status, roles, operation times and the declaration of being at least 18 years old. The password is processed for authentication and stored as a salted hash, not as a plaintext password. Adulthood is self-declared: identity documents, date of birth or biometric data are not ordinarily requested. Display name, biography and other profile fields are optional within the limits of the interface.
Sessions and recovery. Data processed includes session references, request protections, verification, recovery or email-change tokens, expiry, revocations and data needed for communications. Authorisation secrets are not exposed in the catalogue.
Studio connection. Approval in the browser links a device request to the account and enables a limited token. The server records references, permissions, times and revocations. Studio receives the account and status information provided by the connection, without receiving passwords, email or web cookies under the API contract. Credentials entered on the sign-in page are processed by the web service. Connecting does not automatically upload a model.
Contributions. Data processed includes descriptive drafts, original .pnam and .pnam.sig files, filenames, hashes, sizes, metadata, artwork present in the file, author references, status, revisions, checks and attestations. Files may contain data entered by the author; a signature does not guarantee their absence. The Library does not rewrite the signed file to anonymise it.
Declarations and preferences. Versions of the Terms, Sharing Policy, rights and adulthood declarations are recorded separately, with action references. Likes privately associate an account with a model; the public sees the total, while the user sees their own choice. You can remove a like; account closure deletes its associations.
Reports and decisions. Ordinary reports involve the reported model, category, details, any evidence and optional contact information; if authenticated, the reporter reference is included. Communications sent to the general contact address involve the sender's contact details and information provided, including any grounds of unlawfulness, content locations and rights declarations. The ordinary form does not require a separate good-faith declaration or all the information of a legal notice. Decisions, reasons, review requests, acknowledgements of receipt, change proposals and relevant administrative notes are recorded. Evidence links are not automatically downloaded by the server.
Downloads. The application counter for models is aggregated by file/revision and day; it contains no identifying list of downloaders, IP addresses or user agents. The absence of this data from the counter does not mean there are no hosting logs. A count does not certify that the recipient received the complete file.
3. Purposes and bases for processing
The purposes and bases for processing are:
| Purpose | Relevant basis and limits |
|---|---|
| Creating and managing accounts, connecting Studio and performing requested operations | Performance of the relationship with the user or steps requested before entering into it, for necessary data |
| Managing submissions, requested public attribution and distribution of approved content | Performance of the requested service, limited to necessary data and available publication rights |
| Security, abuse prevention, reports, moderation and defence of rights | Legitimate interest in service security and protection of rights, assessing necessity, proportionality and the interests of those involved |
| Responding to requests and correspondence | Handling the request and, depending on its content, pre-contractual steps, performance of the relationship or a legitimate interest in responding |
| Compliance required by law | Legal obligation, only where applicable to the specific case |
| Any optional processing requiring consent | Specific, freely given, informed and withdrawable consent, without incorporating it generally into acceptance of the Terms |
Reading the policy, declaring rights in a model, accepting a contract and authorising optional processing are distinct acts. No retroactive consents are attributed. No sale of data, behavioural advertising, commercial newsletters or advertising profiling is provided for.
PNAM does not use submissions, merely because they are submitted or published, for model training, dataset creation, research or internal R&D. Any future programme will be separate and voluntary and will require dedicated conditions and choices. Technical checks, security, moderation, backup and recovery have distinct purposes. This undertaking by the operator does not impose restrictions on third parties' rights in content lawfully obtained under CC0.
4. Necessary and optional data
Without necessary data it is not possible to provide accounts, authentication or specific requested actions. Public browsing and downloads do not require account creation. A biography and other optional fields are not necessary for browsing alone.
Ordinary reports may be submitted without an account; contact information is optional in the ordinary form, but its absence may prevent clarification and individual replies. A legal notice requires the information prescribed by applicable law, subject to specific exceptions: these requirements must not be confused with those of the community report. Do not voluntarily send passwords, tokens, identity documents or irrelevant information about other people. Any identity checks for data-related requests must be proportionate.
5. Public visibility and recipients
The public author profile is separate from private identity and appears with at least one approved and currently distributable model. The public sees a separate author identifier, username, any display name and biography, and approved models and metadata. The catalogue does not expose email, private identifiers, registration date, avatars or unapproved profile links. Downloaded files make the data actually contained in those files available.
Individual likes, reporter contact details, private notes and security records are not public lists. Affected users see only information made available in their own decision process. Publication may enable third-party copies that cannot technically be recalled.
The operator accesses data needed for administration and moderation. Technical providers may process data strictly necessary for their respective service, according to applicable roles and contracts; authorities and legally entitled parties may receive data in cases provided by law. Data is not sold.
6. Cookies, media and local devices
The language preference, sessions and temporary Studio connection code are described in the Cookie and Local Storage Information. The website does not automatically load analytics, advertising pixels, Google Fonts or remote YouTube thumbnails.
The Spotify player is loaded only after a user choice and may communicate technical data to the provider or use its own storage. Before loading, the panel states that the player is third-party content and that loading it connects the browser to Spotify. The choice is not stored for subsequent visits; the removal command does not delete data already transmitted or stored by the provider. Ordinary links to external services open their respective websites under their own conditions.
Studio stores projects, preferences and submission-recovery references locally; local processing does not automatically send captures, checkpoints or entire project folders to the Library. RealNAM loads models and processes audio according to the release and settings. Loading a model locally in RealNAM does not, by itself, send the model or audio to the Library.
7. Providers, data locations and transfers
Hosting. For hosting services covered by the Spaceship Data Processing Addendum, Spaceship, Inc. and its affiliates act as processor on behalf of the controller. The services may involve website data, databases, logs and backup copies. Data may also be processed in the United States; in relevant cases, the DPA provides for the standard contractual clauses applicable to transfers, including controller-to-processor clauses. A server's physical location does not imply that all processing or access remains exclusively within the European Economic Area. Also consult the Spaceship Privacy Policy.
Gmail correspondence. The support contact uses Gmail/Google. Messages and related technical data are also processed by the email service under the conditions applicable to the account. Google may process information on servers in different countries: consult the Google Privacy Policy and the information on account region and provider. This policy does not attribute a Google Workspace service or separate processing agreement to the contact.
The Gmail address is the correspondence contact and does not identify a transactional email provider for the Library. Communications and decisions accessible in the personal area are distinct from email delivery; a queued record does not demonstrate that the recipient received a message.
8. Retention
Data is retained according to the following rules, distinguishing credential validity, evidence retention and file deletion.
| Category | Retention |
|---|---|
| Active accounts and published content | For the time necessary for the service; removal or closure starts the relevant processes |
| Data no longer necessary after account closure | Deletion or minimisation within 30 days; relevant evidence follows the specific categories |
| Expired/revoked sessions and tokens | Deletion within the prescribed maximum of 30 days from the relevant event, with earlier deletions; this does not extend credential validity |
| Rate limits | Deletion within 24 hours after the end of the window |
| Inactive drafts | Eligible for deletion after 12 months; account closure deletes drafts |
| Pending submissions | Up to 90 days, unless relevant handling remains open |
| Rejected files | 180 days from the relevant final decision |
| Removed files | A maximum of 180 days from removal, unless retention is justified |
| Quarantine copy after publication | Up to 180 days from publication, without deleting a public file that remains distributable |
| Reports | 3 years from closure |
| Moderation history | 3 years from the final decision, taking review into account |
| General security and audit events | 12 months from the event |
| Technical/test residues | A maximum of 30 days, with earlier deletion where possible |
| Genuinely non-identifying download aggregates | No predetermined period; they may be deleted with the file |
| Application/access logs managed directly by PNAM | For the time necessary for technical management, security and investigation of incidents, limiting relevant data and distinguishing it from the audit and moderation evidence above |
| Infrastructure logs and other records managed by the provider | For covered data, the Spaceship DPA uses the period necessary to provide the covered services or required by law; this criterion is separate from PNAM application-data periods |
| Ordinary correspondence and support | While handling the request and for 12 months after its closure; subsequently, only data necessary for legal obligations, security, disputes or protection of rights, for a period consistent with those purposes |
Ordinary support retention does not replace the specific periods for reports, moderation or other proceedings: an email exchange necessary for a case follows the relevant purpose and period, without automatically extending retention of the entire mailbox. Ordinary deletion or minimisation must also be applied to manual correspondence management.
A dispute, incident or legally relevant request may require specific, justified retention with restricted access; it does not authorise indiscriminate retention. Residual references may be pseudonymous and still linkable, not automatically anonymous.
9. Closure, copies and backups
Account closure revokes credentials and connections, deletes drafts, hides the profile and stops public distribution of its models. It does not mean immediate deletion of every piece of evidence or backup. The account's likes are deleted. The sole administrator's inability to self-delete without administrative continuity does not exclude privacy requests to the controller.
Backup copies are separate from active data and are not a public project archive. An earlier copy may contain data subsequently deleted. A restore is subject to the relevant deletions, restrictions and revocations before data is made available again. Users are not offered permanent storage or guaranteed file recovery.
Removal from the catalogue does not delete copies already obtained by third parties or automatically revoke rights in validly shared content.
10. Security and decisions
PNAM uses access controls, credential hashing, limited authorisations, private storage and file checks. No measure guarantees absolute freedom from incidents or data loss. Do not disclose credentials to anyone claiming to be support, and retain copies of your work.
PNAM does not make decisions based solely on automated processing that produce legal effects concerning the user or similarly significantly affect them. Automated security and compatibility checks may technically prevent a request or submission, but publication and moderation decisions follow the processes described by the service. No advertising profiling is performed. To challenge an issue, use the available reporting and review channels.
11. Rights and contacts
In the cases and within the limits provided by law, you may request access, rectification, erasure, restriction and portability of data, object to processing based on legitimate interests and withdraw any consent given without affecting prior processing. These rights do not apply indiscriminately to every item of data or retention obligation.
Write to riccardo.consolandi.eng@gmail.com describing your request without sending secrets. Proportionate information may be requested to identify the request and verify that it concerns your data. Requests will be handled within legal time limits; any permitted extensions will be justified and communicated. You may lodge a complaint with the Italian Data Protection Authority or the competent authority under applicable law.
Policy updates will be identifiable by date and version; they do not automatically authorise new purposes or turn acknowledgement into general consent.