Privacy Policy

1. Controller

The controller of PINKBLCK is Aurelio Cusimano, acting as a natural person. For matters concerning personal data protection: privacy@pinkblck.com.

2. Data

Account, profile, Experiences, Nodes, manual tags, media, interactions, messages, reports and technical/security data may be processed.

3. Purposes

Account operation, content publication, search, social interactions, messaging, safety, moderation, support and legal compliance.

4. Legal bases

Contract, legal obligation, legitimate interests for security and rights protection, and consent where required.

5. Public visibility

Public profiles/content may be visible without login and indexed by search engines when technically enabled.

6. On-demand translation

When a user chooses translation, text may be sent to an external translation service following the user’s action.

7. Providers

Hosting/database infrastructure currently uses Aruba services. Other providers may support email, security, backups, push notifications or consented analytics and must be documented before use.

8. International transfers

Appropriate GDPR transfer mechanisms are assessed when providers process data outside the EEA.

9. Retention

Data is kept for the service relationship and only as long as needed afterwards for law, safety and rights protection. Specific internal retention schedules must be finalised before launch.

10. Messaging

Messages/attachments are processed to deliver and secure conversations.

11. Reports

Reports may include reporter, reported content and screenshots.

12. Minors

PINKBLCK is not intended for users under 14.

13. Security

Risk-appropriate technical and organisational measures are used.

14. Rights

GDPR rights include access, rectification, erasure, restriction, portability, objection, consent withdrawal and supervisory-authority complaint.

15. Automated decisions

No solely automated legally significant decisions are declared in the current configuration.

16. Cookies

See Cookie Policy and the Privacy & Cookie preferences centre.

17. Changes

Material changes will be communicated appropriately.

18. Linked public pages and imports from external services

When a user links a supported public page or channel, PINKBLCK may process the provider, public URL/name, external identifier, link status, synchronisation/publication settings, last-sync time and identifiers needed to prevent duplicate imports.

For imported content, PINKBLCK may process the external content ID and URL, public title, description/text, thumbnail, date and other public metadata needed to create and display the PINKBLCK Experience and retain the original-source reference.

For YouTube, public-channel checks may be performed through server-side requests to Google/YouTube services/APIs. When an external thumbnail is loaded directly by the browser, the provider may receive technical request data under its own terms and notices.

The purpose is to provide the requested linking, checking and importing function and prevent duplicates. Essential requested functions rely on performance of the service; optional browser technologies are handled under the Cookie Policy.

If a provider later requires OAuth authorisation or access tokens for additional functions, PINKBLCK will process only the technical credentials necessary for the connection, with appropriate security and until no longer needed or revoked.

19. Profile visibility and conversation management

For fields where PINKBLCK provides visibility controls, such as location, country and linked public pages, the platform also processes the relevant preference to determine whether the information is displayed to other users or visitors through the available feature.

Messaging processes participant and conversation identifiers, messages, attachments where used, dates and technical information needed for delivery, ordering, read status, messaging limits, security and conversation management.

When a participant removes a conversation from their view, PINKBLCK may record the information needed to stop displaying the previous session to that participant. This action does not automatically delete the messages from the other participant’s view.

If the same participant later starts a new session with the same account, PINKBLCK may use participation timestamps to display only messages belonging to the new session. Earlier data may continue to be processed for the other participant and, where necessary, for security, legal obligations or the protection of rights.

Actual retention of messages and attachments remains subject to the general criteria in this Policy and to any available deletion features.