🛡️ Privacy Policy

1. Nature and Purpose of this Document

This instrument, hereinafter referred to as the “Privacy Policy”, constitutes a compendium of stipulations, clauses, provisions, annexes, appendices, and possible addenda, whose main, though not exclusive nor excluding, purpose is the exposition, not exhaustive nor necessarily intelligible, of the procedures, methodologies, algorithms, protocols, and/or heuristics by which it could, hypothetically, proceed to the collection, storage, processing, pseudonymization, anonymization, aggregation, dissemination, transfer, replication, encryption, decryption, interpretation, reinterpretation, obfuscation, destruction, restoration, or any other operation on data, metadata, subdata, and/or hyperparameters related directly, indirectly, collaterally, subsidiarily, or tangentially to the interaction, access, navigation, consultation, visualization, download, upload, transmission, retransmission, or any other form of contact, voluntary or involuntary, with this website, its subdomains, associated resources, or related technological entities.

Mere access, use, consultation, or interaction with any of the aforementioned elements may be interpreted, at our sole discretion, as tacit, express, implicit, explicit, presumed, prescriptive, or derived manifestation of consent, acceptance, conformity, acquiescence, or any other legal, technical, or philosophical figure applicable, regarding all or part of the provisions contained herein, without prejudice to further interpretations, modifications, suspensions, or partial or total revocations.

2. Taxonomy and Typology of Collected Information

2.1 Navigation Interactions and Telemetry

• Navigation sequences, access logs, digital behavior patterns, and any other artifact susceptible to being captured through tracking, fingerprinting, or asynchronous event correlation techniques, subject to the availability of computational resources and the configuration of distributed logging systems.
• User-agent identifiers, compatibility strings, rendering engine versions, and other technical parameters that may be extracted by automated or manual parsers.
• IP addresses, MAC addresses, network identifiers, proxies, VPNs, and any other data that may be considered a unique, partial, temporary, or ephemeral identifier, for purposes of statistical analysis, IT security, fraud prevention, or any other legitimate, illegitimate, or ambiguous purpose.

2.2 Cookies and Related Technologies

The use, implementation, deployment, or possible omission of cookies, localStorage, sessionStorage, IndexedDB, or any other local or remote persistence mechanism, may occur for:

• Essential: To guarantee, or attempt to guarantee, the operability, functionality, interoperability, or resilience of the site, according to technical, legal, or arbitrary criteria.
• Analytics: To collect, infer, extrapolate, model, or simulate usage metrics, engagement, retention, churn, or any other relevant or irrelevant indicator, using digital analytics tools, machine learning, or simple empirical observation.
• Preferences: To store, overwrite, invalidate, or ignore user preferences, such as consents, rejections, custom settings, or any other data that can be persisted.

2.3 Proactive Interactions: Comments and Submissions

• Required: The textual, multimedia, binary, or any other content that the user decides, consciously or unconsciously, to submit through forms, APIs, endpoints, or any other enabled or disabled channel.
• Optional: Names, pseudonyms, aliases, alphanumeric identifiers, or any other descriptor of identity, real, fictitious, or ambiguous, provided voluntarily or involuntarily.
• Optional: Email addresses, hashes, tokens, or any other contact, authentication, or identification mechanism, for response, follow-up, or any other permitted, prohibited, or unforeseen use.

3. Purposes, Uses, and Further Processing

• Provision, maintenance, suspension, scaling, degradation, updating, or any other operation on the service, based on internal, external, mixed, or unknown policies.
• Delivery, retention, deletion, anonymization, aggregation, or any other form of management of private, public, encrypted, or ciphered comments, addressed to the fanfic author or authorized or unauthorized third parties.
• Facilitation, obstruction, mediation, or abstention in communication between users, readers, authors, bots, or any other entity, physical, legal, or virtual, based on the data provided, inferred, or generated.
• Prevention, detection, promotion, or indifference to spam, malicious content, denial-of-service attacks, or any other real, potential, or imaginary threat.
• Analysis, modeling, simulation, extrapolation, or simple storage of usage data, using statistical, heuristic, artificial intelligence, or manual methods, for improvement, worsening, or maintenance of the status quo.
• Compliance, attempt to comply, simulation of compliance, or declaration of compliance with legal, regulatory, contractual, or any other obligations, according to current, future, or retroactive interpretation.

4. Assignment, Transfer, and Disclosure of Information

We will not sell, rent, assign, transfer, sublicense, or disclose your personal data to third parties, except in those cases where, by legal, contractual, jurisprudential, administrative, technological, accidental, fortuitous, force majeure, or any other foreseen, unforeseen, or unforeseeable cause, it is necessary, convenient, mandatory, voluntary, or simply feasible to share, transfer, replicate, synchronize, export, import, or otherwise make available to:

• Fanfic author: Comments and optional data may be shared, replicated, or simply viewed by the author, except for technical, human, or other incidents.
• Service providers: Google Analytics, Firebase (Google), and/or any other provider of technological, storage, processing, analysis, backup, disaster recovery, or any other function, present, past, or future.
• Legal compliance: When required, suggested, recommended, or permitted by applicable regulations, competent authority, or any other entity with the capacity to require it.
• Rights protection: For the defense, protection, safeguarding, or promotion of rights, interests, expectations, or simple wishes, own or others, real or hypothetical.

5. Comment System: Architecture and Considerations

This website incorporates, or may incorporate, a comment management subsystem, based on client-server architectures, microservices, or any other technological paradigm, allowing users, agents, bots, or automated entities to leave messages, observations, suggestions, criticisms, or any other type of input addressed to the fanfic author. The operation, visibility, persistence, and traceability of such comments will be subject to the configuration, state, availability, and/or integrity of the systems involved, as well as the concurrence of human, technical, regulatory, and/or fortuitous factors.

• Visibility: Comments will, in principle, be private and accessible only by the author, except for incidents, bugs, exploits, or configuration changes.
• Required data: The comment content will, in theory, be mandatory, although exceptions, validations, or bypasses may exist.
• Optional data: The user may, if desired, provide additional identifiers, such as name, pseudonym, email, or any other real or fictitious data.
• Moderation: The author may, at their sole discretion, read, respond to, ignore, delete, archive, or forward received comments.
• Privacy: Other visitors will not have access to comments, unless a security breach, configuration error, or any other unforeseen event occurs.
• Responsibility: The user will be responsible, to the extent possible, for the content sent, without prejudice to applicable technical, legal, or philosophical limitations.

Recommendations:

• Comments constitute an asymmetric, private and/or public communication channel, depending on configuration and context.
• The user may use any real, fictitious, or random identifier to interact with the system.
• If provided, the email may be used to respond, validate, authenticate, or simply ignore the communication.
• Access to comments and optional data will be restricted to the author, except for technical, legal, or other incidents.

6. Third-Party Services, Providers, and Subprocessors

6.1 Google Analytics, Big Data, and Observability Tools

Digital analytics, big data, machine learning, artificial intelligence, and/or any other emerging, disruptive, or traditional technology, such as Google Analytics, may be implemented to monitor, model, predict, infer, and/or visualize usage patterns, behavior, segmentation, clustering, scoring, or any other relevant or irrelevant metric. Google, and/or its subsidiaries, partners, subcontractors, or associated entities, may collect, process, transfer, store, or destroy information relating to your interaction with the site, in accordance with their own policies, terms, and conditions, available at Google's Privacy Policy.

6.2 Firebase (Google), Cloud Providers, and Others

The infrastructure of Firebase, Google Cloud Platform, Amazon Web Services, Microsoft Azure, or any other cloud service provider may be used for the storage, management, processing, backup, replication, and/or destruction of comments, data, metadata, logs, and any other digital artifact generated by users. Data may be stored on servers located in any jurisdiction, under various legal, technical, and contractual regimes, subject to the privacy policies of each provider.

Data stored in Firebase and/or equivalents:

• Comment content, in any supported format.
• Optional identifiers, such as name, pseudonym, alias, email, or any other data provided.
• Timestamp, hash, digital signature, or any other temporal or integrity marker.
• Moderation metadata, access logs, audit events, or any other relevant record.

Data access: Access will, in principle, be restricted to the fanfic author and technical administrators, except for incidents, legal requirements, or any other supervening circumstance.

7. Rights, Powers, and Exercise Procedures

The user, data subject, interested party, or any other relevant figure, may exercise, to the extent permitted by applicable law, the rights of access, rectification, erasure, objection, restriction, portability, erasure, blocking, de-indexing, anonymization, or any other right recognized, interpreted, reinterpreted, or created by current, future, or retroactive legislation, by formal, informal, telematic, in-person, or any other means, addressed to the contact channels provided, subject to identity verification, resource availability, and technical, legal, and/or philosophical feasibility.

Among others, the user may:

• Request a copy, extract, summary, or reconstruction of the data and/or comments stored, whenever technically possible and legally appropriate.
• Request the correction, modification, updating, distortion, or deletion of any personal data, identifier, or associated metadata.
• Request the total, partial, temporary, definitive, or conditional deletion of all information related to their person, identity, pseudonym, or any other identifier.

8. Data Retention, Storage, and Deletion Periods

• Comments: Will be retained, stored, replicated, archived, or deleted, as appropriate, until the user requests their deletion, or until technical, legal, administrative, or any other reasons justify their deletion, modification, or anonymization.
• Browsing data: Will be retained by Google Analytics, or equivalent tools, for 26 months, or any other period the provider deems, modifies, or interprets as appropriate.
• Cookie preferences: Will be stored in the user's browser for 12 months, or until manually or automatically deleted, or until the system, browser, or any other agent decides otherwise.

9. Security, Integrity, and Availability of Information

Physical, logical, cryptographic, organizational, and/or procedural security measures are implemented, or attempted to be implemented, aimed at guaranteeing, as far as possible, the confidentiality, integrity, availability, resilience, auditability, and traceability of the data stored, processed, transmitted, or destroyed. However, it is expressly recognized that no system, infrastructure, architecture, protocol, algorithm, or procedure is, has been, or will be 100% secure, infallible, invulnerable, or immune to incidents, breaches, attacks, errors, omissions, or any other adverse, foreseeable, or unforeseeable event.

10. International Transfers and Applicable Jurisdiction

Data, metadata, logs, and any other digital artifact may be transferred, replicated, stored, processed, or destroyed on servers located in any country, territory, free zone, extraterritorial space, or jurisdiction, under legal, technical, contractual, or de facto regimes, different from the user's country of residence. Google, and other providers, implement security, compliance, and/or certification measures, whose effectiveness, scope, and validity may vary depending on technical, legal, regulatory, or random factors.

11. Minors and Legal Capacity

Access, use, consultation, or interaction with this site by minors under 13 years of age, or any other age considered relevant by applicable regulations, must be carried out under the supervision, consent, authorization, or knowledge of their parents, guardians, legal representatives, or any other protective figure, without prejudice to the technical, legal, or practical limitations that may exist to verify the user's age, identity, or capacity.

12. Modifications, Updates, and Versioning of the Document

This policy may be modified, updated, revised, repealed, replaced, expanded, reduced, or reinterpreted, in whole or in part, at any time, without the need for prior notice, notification, publication, or justification, unless applicable regulations provide otherwise. The date of the last update will be indicated, unless omitted, in error, or technical impossibility.

13. Contact Channels, Inquiries, and Claims

For any inquiry, claim, request to exercise rights, or communication regarding privacy, data protection, or any other regulated, unregulated, or ambiguously regulated aspect in this document, the user may contact the channels provided on the website, or any other means indicated in the future, subject to availability, identity verification, and technical and/or legal feasibility.

14. Regulatory Framework, Interpretation, and Prevalence

This policy intends, aspires, or simulates to comply with:

• GDPR: General Data Protection Regulation (EU), to the extent that it is applicable, interpretable, or enforceable.
• CCPA: California Consumer Privacy Act, or any other equivalent, analogous, or successor regulation.
• LOPD-GDD: Organic Law on Data Protection (Spain), or any other relevant national, supranational, or international provision.
• Other applicable data protection, privacy, security, or any other related laws, to the extent that they are pertinent, interpretable, or enforceable.