Booking requests and responses are available. Booking deposits, funding, arrival verification, escrow payouts, refunds and automatic settlement are currently unavailable. Recording a dispute does not freeze on-chain funds. The available contract does not enforce recipient restrictions, dispute locks or timed releases. Escrow workflow descriptions below are not current service or protection guarantees. Subscription and credit-pack BTC, ETH and Base USDC/EURC checkout is separate and requires verified treasury configuration and blockchain observers.

Silkly.top Statutory Compliance & European Privacy Standards

Platform Privacy Policy

Comprehensive disclosure regarding personal data governance, European data sovereignty, zero-telemetry media sanitization, and GDPR compliance.

Updated: September 2, 2026EU GDPR & Dutch UAVGHost: Amsterdam & Paris
EU Data Sovereignty

100% hosted in Amsterdam & Paris. Insulated from extraterritorial surveillance and US CLOUD Act mandates.

Zero Biometrics Stored

3D Didit facial scans verified on-the-fly. No raw biometric templates or ID scans stored on Silkly databases.

In-Memory EXIF Scrub

All photos are stripped of GPS geotags, camera serials, and timestamp metadata before cloud persistence.

72-Hour Closure Grace Period

Reversible account closure requests with a 72-hour grace period and purpose-based retention review.

Operating Entity & DomicileAmsterdam, The Netherlands
Corporate Body:Silkly B.V. (in formation)
Primary Privacy Desk:hi+compliance@silkly.top
Section 1

Data Controller & Statutory Framework

1.1 Data Controller Identification: Silkly B.V. (in formation) ("Silkly," "Platform," "we," "us," or "our") operates the website silkly.top and its associated Progressive Web Application ("PWA") as the primary Data Controller under Regulation (EU) 2016/679 of the European Parliament and of the Council (General Data Protection Regulation - GDPR) and the Dutch GDPR Implementation Act (Uitvoeringswet Algemene verordening gegevensbescherming - UAVG).

1.2 Infrastructure Domicile & Data Sovereignty: All core platform infrastructure, application servers, relational databases, and object storage buckets are provisioned and hosted strictly within European Union member states (Amsterdam, The Netherlands and Paris, France). This architecture guarantees strict European data sovereignty, full GDPR compliance, and insulation from foreign extraterritorial surveillance requests such as those issued under the United States CLOUD Act.

1.3 Dedicated Privacy Office: For all inquiries, data access requests, or statutory rights enforcement under Chapter III of the GDPR, users may contact our designated Data Protection desk directly at hi+compliance@silkly.top.

Section 2

Categories of Personal Data Processed

2.1 Searcher (Client) Account Data:

  • Authentication Credentials: Valid email address, encrypted password hash generated using bcrypt (12 rounds), and cryptographically signed session tokens.
  • Account Customization: Optional account first name and last name stored to personalize authenticated dashboards and greetings.
  • Multi-Factor Authentication: Time-Based One-Time Password (TOTP) seed secrets, emergency backup recovery codes, and verification attempt counters.
  • Web3 Wallet Identifiers: Public blockchain wallet addresses on the Base network connected to initiate self-custody smart contract booking deposits.
  • Booking & Transaction History: Time-stamped booking reservations, doorstep verification states, dynamic release timestamps, and closed-loop review submissions.

2.2 Lister (Provider) Profile Data:

  • Professional Directory Details: Professional display name, biography, services offered, lifestyle tags, baseline rates, supported currencies (USD, EUR, GBP, CAD, AUD), and travel tour dates.
  • Geographic Location Data: Base city name, region, country code, and approximate latitude and longitude coordinates utilized for directory search indexation and Haversine distance matching. Silkly does not collect, record, or track continuous real-time GPS device telemetry.
  • Direct Encrypted Contact Channels: External contact handles voluntarily published by the provider (public contact email, Telegram username, Signal phone number, and WhatsApp number).
  • Identity Verification Records: Legal first name and legal last name confirmed via Didit identity verification, alongside cryptographic verification tokens. Raw identity documents and biometric scans are not stored in our application database.
  • Payout Wallet Address: Public Web3 wallet address designated to receive automated, non-custodial smart contract settlements on Base.

2.3 System Telemetry & Operational Identifiers:

  • Network Identifiers: Internet Protocol (IP) addresses processed strictly in volatile memory to enforce progressive authentication rate-limiting, mitigate automated credential stuffing, and prevent brute-force abuse.
  • Web Push Subscription Endpoints: Voluntary Application Server Identification (VAPID) push tokens enabling native lock-screen notifications on iOS and Android devices.
Section 3

Legal Bases for Processing under GDPR

3.1 Performance of a Contract (GDPR Article 6(1)(b)): Processing account credentials, maintaining published directory listings, coordinating booking requests, validating proximity handshakes, and executing smart contract escrow settlements.

3.2 Compliance with Legal Obligations (GDPR Article 6(1)(c)): Retaining corporate records, maintaining transaction audit trails for tax reporting with the Dutch Tax Administration (Belastingdienst), and cooperating with lawful warrants issued by Dutch courts.

3.3 Legitimate Interests (GDPR Article 6(1)(f)): Enforcing platform security, preventing automated bot scraping via IP rate limiting, blocking duplicate or stolen images via perceptual hashing, and protecting directory integrity against fraud.

3.4 Explicit Consent (GDPR Article 6(1)(a) & Article 9(2)(a)): Administering voluntary biometric identity verification via Didit, subscribing to browser push notifications, and publishing voluntary contact channels on public directory cards.

Section 4

Mandatory Identity Verification & Biometric Processing (Didit)

4.1 Universal Lister KYC Requirement: To ensure community safety, prevent identity fraud, combat human trafficking, and guarantee complete compliance with child protection directives, 100% of prospective Listers (Providers) must successfully complete identity verification before directory listings, media files, or calendar availability can be activated.

4.2 Third-Party Verification Infrastructure: Identity verification is conducted directly by Didit (Didit Me S.L., Madrid, Spain), an established European identity verification provider operating under strict European Union GDPR and AML compliance standards. The verification workflow encompasses:

  • Optical Character Recognition (OCR) extraction and validation of an authentic, unexpired government-issued photo identity document (passport, national identity card, or driver's license).
  • Three-dimensional (3D) passive facial liveness scanning to detect synthetic deepfakes, static screen displays, printed masks, and digital spoofing attempts.
  • Algorithmic one-to-one (1:1) facial biometric comparison between the live portrait capture and the credential photo.
4.3 Zero Biometric Storage Architecture:In strict adherence to GDPR Article 5(1)(c) (Data Minimization) and Article 9 (Special Category Data), Silkly B.V. (in formation) does not store raw biometric templates, mathematical face vectors, or full high-resolution government identity document scans within its core relational PostgreSQL database or local application servers. Didit transmits only an authenticated cryptographic verification token, the verification outcome status (Approved or Declined), and verified legal name confirmation via encrypted server-to-server webhooks.

4.4 Processor Data Retention: Didit retains underlying verification audit documentation solely in accordance with statutory European AML, KYC, and fraud-prevention obligations, functioning as an independent data processor bound by a comprehensive Data Processing Agreement (DPA).

Section 5

Automated Media Pipeline & Server-Side Privacy Protections

5.1 In-Memory Server-Side Media Pipeline: To guarantee absolute location privacy and protect content creators from digital stalking or physical tracing, all photographs and short video clips uploaded to Silkly are routed through a server-side, in-memory processing pipeline prior to cloud object persistence.

5.2 100% EXIF and GPS Metadata Removal: The processing pipeline parses all uploaded image binary streams and permanently strips:

  • All Exchangeable Image File Format (EXIF) metadata tags.
  • Global Positioning System (GPS) latitude, longitude, and altitude coordinates.
  • Camera hardware serial numbers, lens models, and device operating system fingerprints.
  • Original creation timestamps and camera software settings.

5.3 Image Optimization & Modern Formats: Following metadata scrubbing, image assets are compressed, normalized, and converted into privacy-sanitized WebP format to reduce data payloads, eliminate invisible tracking steganography, and optimize client delivery across the Edge Content Delivery Network (Bunny.net).

5.4 Perceptual Duplicate Hashing (pHash): Uploaded media is analyzed using a 64-bit Discrete Cosine Transform perceptual hashing algorithm. This generates a numerical fingerprint of the visual composition to identify duplicate, stolen, or previously blacklisted images across unrelated accounts, effectively eliminating catfishing and unauthorized photo reuse while preserving zero raw visual telemetry in search indexes.

5.5 Dynamic Verification Watermarking: Verified profile images receive a dynamically scaled SILKLY VERIFIED watermark composited directly into the image binary server-side. This watermark serves to deter unauthorized third-party commercial scraping, prevent re-publication on unverified adult directories, and protect creator intellectual property.

Section 6

Non-Custodial Blockchain & Transaction Telemetry

6.1 Decentralized Smart Contract Architecture: Silkly operates a non-custodial booking escrow architecture deployed on the Base blockchain network. Booking deposits are locked and settled peer-to-peer using canonical Circle USD Coin (Base USDC) or Euro Coin (Base EURC) via autonomous smart contracts.

6.2 Public Ledger Transparency & Immutability: Users acknowledge and understand that public blockchains are decentralized, immutable public ledgers. Transactions submitted to the Base network—including wallet addresses, transaction hashes, timestamps, and contract call parameters—are recorded permanently across distributed network nodes. Silkly possesses no technical capability to alter, redact, overwrite, or delete transaction data recorded directly on the blockchain.

6.3 Pseudonymous Wallet Tracking: Silkly associates a user's public Web3 wallet address with their internal account record solely for the technical execution of booking authorizations, auto-release timers, dispute arbitration, and subscription verification. Silkly does not require, collect, or store private cryptographic keys, seed phrases, or external exchange login credentials.

6.4 Ephemeral Doorstep Handshake Tokens: The dynamic HMAC-SHA256 rotating QR codes and 4-digit mutual PINs utilized for physical arrival verification are generated using time-sensitive nonces. Once proximity is validated and the transaction transitions to verified status, handshake nonces expire automatically and are purged from volatile server memory.

Section 7

Data Retention, Reversible Closure & Erasure Review

7.1 User-Initiated Erasure Rights: Under Article 17 of the GDPR (Right to Erasure), every registered Searcher and Lister maintains the autonomous right to request the permanent deletion of their account and all associated personal data via the Security Settings portal at /dashboard/security.

7.2 The 72-Hour Reconsideration Grace Period:

  • Instant Directory Delisting: The moment account deletion is confirmed by the user, the account status transitions immediately to hidden, directory profiles are suppressed from public search indexes, and direct URL routing returns an HTTP 404 or deactivation interstitial.
  • Reversible Grace Window: The account enters a seventy-two (72) hour grace period. During this period, the user may authenticate and cancel the closure request. Existing account restrictions and listing publication controls still apply.

7.3 Account Closure and Retention Review:

  • Closure: After the grace period, eligible accounts close without erasing records. Unresolved financial workflows block closure. Automatic permanent deletion is disabled.
  • Retention Review: Retained records remain identifiable and linked to their original IDs. An ADMIN must document a justified purpose; no blanket 24-month retention hold is applied.
  • Evidence and Media: Preservation holds and applicable retention requirements remain in effect. Available stored records and media can be included in access-controlled ADMIN exports.
  • Authorized Review: Proposed reviews occur 24 calendar months after closure or case resolution for justified records. Earlier required erasure, longer statutory retention and accounting archive requirements require appropriate review.
7.4 Active Escrow Deletion Block:Accounts associated with active, funded, proximity-verified, or disputed escrow bookings cannot initiate account deletion. The platform deletion endpoint rejects deletion requests with an HTTP 400 Bad Request error until all pending smart contract escrows have settled and closed, ensuring dispute evidence remains fully accessible to both parties during arbitration.
Section 8

Cookies, Local Storage & Tracking Telemetry

8.1 Zero Commercial Ad Trackers: Silkly operates with zero commercial advertising trackers, third-party behavioral profiling cookies, retargeting pixels, or invasive analytics platforms (such as Google Analytics or Meta Pixel). We do not sell, rent, monetize, or broker user browsing patterns or personal data to data brokers or advertising exchanges.

8.2 Strictly Necessary Functional Tokens:

  • Secure Authentication Cookies: Encrypted HTTP-only JSON Web Tokens (JWT) maintaining authenticated session state across requests (auth_token and session cookies) configured with strict SameSite protection.
  • Security Nonces: Cryptographic Cross-Site Request Forgery (CSRF) tokens protecting sensitive form submissions and API mutations.
  • Ephemeral Handshake Tokens: Time-sensitive cryptographic nonces utilized to generate dynamic rotating 60-second HMAC QR codes for doorstep arrival verification, which are purged from volatile server memory upon completion.
  • Progressive Web Application (PWA) Storage: Local storage tokens caching service-worker application shell assets and user interface theme preferences to enable high-speed offline performance.

8.3 Client Storage Management: Users maintain full control over client-side storage and may inspect, block, or delete cookies and local storage items at any time through their device browser settings. Note that disabling strictly necessary session cookies will prevent login and dashboard access.

Section 9

Third-Party Sub-Processors & Data Transfer Domiciles

9.1 Strict European Domicile Standard: All third-party sub-processors engaged by Silkly operate under formal Data Processing Agreements (DPAs) in compliance with GDPR Article 28, with core infrastructure nodes situated strictly within the European Union:

Cloud Compute, Database & Object Storage:Scaleway S.A.S. (Paris, France and Amsterdam, The Netherlands) — Cloud VPS infrastructure, managed PostgreSQL database clusters, and private S3-compatible object storage vaults.
Edge Routing, Anycast DNS & Content Delivery:BunnyWay d.o.o. / Bunny.net (Ljubljana, Slovenia) — Sovereign European Anycast DNS routing, DDoS traffic filtering, SSL certificate termination, and edge media caching.
Biometric Identity & 3D Liveness Verification:Didit Me S.L. (Madrid, Spain) — Biometric liveness validation, document OCR verification, and 1:1 facial matching operating under Spanish and EU data protection standards.
Transactional Communications:Proton AG (Geneva, Switzerland) — Zero-access encrypted transactional SMTP mail relaying utilized for essential system notices and account recovery.
Web Push Notification Delivery:Apple Push Notification Service (APNs) and Google Firebase Cloud Messaging (FCM) — Utilized strictly as pass-through delivery pipelines for cryptographically signed, zero-payload VAPID push alerts dispatched to mobile devices.
Section 10

Enforceable Data Subject Rights under GDPR

10.1 Statutory Rights Framework: Pursuant to Chapter III (Articles 12 through 23) of Regulation (EU) 2016/679 (GDPR) and the Dutch UAVG, every user maintains enforceable rights regarding their personal data held by Silkly B.V. (in formation):

  • Right of Access (Article 15): The right to request confirmation as to whether personal data concerning you is being processed, and to obtain a structured copy of that data.
  • Right to Rectification (Article 16): The right to rectify inaccurate personal information or update incomplete profile attributes, rates, and contact channels directly via your account settings.
  • Right to Erasure / Right to be Forgotten (Article 17): Account closure requests have a 72-hour reversible grace period. Erasure requests require preservation and retention review; automatic hard deletion is disabled.
  • Right to Restriction of Processing (Article 18): The right to restrict data processing under specific statutory grounds, such as disputing data accuracy or challenging the lawfulness of processing during dispute arbitration.
  • Right to Data Portability (Article 20): The right to receive personal data provided to us in a structured, commonly used, and machine-readable JSON format, or request transmission to another controller where technically feasible.
  • Right to Object (Article 21): The right to object at any time to processing based on legitimate interests under Article 6(1)(f).
  • Right to Withdraw Consent (Article 7(3)): Where processing is grounded in explicit consent (such as biometric verification via Didit or voluntary push notification endpoints), you maintain the right to withdraw consent at any time without affecting the lawfulness of processing based on consent before its withdrawal.

10.2 Procedure for Exercising Rights:

  • To submit a formal Data Subject Access Request (DSAR) or exercise your statutory rights, email hi+compliance@silkly.top with the subject line "GDPR Rights Request".
  • To protect account integrity and prevent unauthorized data exfiltration, requests must originate from the registered email address associated with the account.
  • In accordance with GDPR Article 12(3), Silkly responds to substantiated requests within one (1) calendar month of receipt.
Section 11

International Data Transfers & Cross-Border Safeguards

11.1 European Data Residency Guarantee: Silkly maintains its primary compute servers, managed PostgreSQL databases, and encrypted S3-compatible media vaults within the European Union (Amsterdam, The Netherlands and Paris, France). We do not transfer, mirror, or replicate core personal data to third countries that lack an adequacy decision from the European Commission.

11.2 Insulation from Foreign Surveillance Laws: By anchoring all storage infrastructure within European Union borders and enforcing client-side cryptographic hashing, Silkly structures its technical topology to insulate user records from foreign extraterritorial discovery mandates, including 18 U.S.C. 2713 (the United States CLOUD Act).

11.3 Public Blockchain Exemption Notice: Blockchain transaction records (wallet addresses, smart contract execution timestamps, escrow state transitions) published to the decentralized Base network exist across global distributed validator nodes. Blockchain transactions are decentralized, publicly visible, and structurally outside the unilateral custody, geographic containment, or deletion capability of Silkly B.V. (in formation).

Section 12

Supervisory Authority, Amendments & Contact

12.1 Right to Lodge a Statutory Complaint: In accordance with GDPR Article 77, if you believe that the processing of personal data relating to you infringes European data protection legislation, you have the right to lodge a formal complaint with a supervisory authority, particularly in the EU Member State of your habitual residence, place of work, or place of the alleged infringement. In The Netherlands, the competent lead supervisory authority is:

Autoriteit Persoonsgegevens (Dutch Data Protection Authority)

Bezuidenhoutseweg 30
2594 AV Den Haag, The Netherlands
Telephone: (+31) (0)70 888 85 00
Website: autoriteitpersoonsgegevens.nl

12.2 Policy Revisions: Silkly B.V. (in formation) reserves the right to amend this Privacy Policy periodically to reflect technological advancements, updates to data processing architecture, or evolving European jurisprudence. Any modifications will be posted directly to silkly.top/privacy with an updated revision date. Continued engagement with the platform following posted amendments constitutes recognition of the revised practices.

12.3 Data Protection Office & Compliance Desk:

For any questions, statutory rights requests, or regulatory communications regarding our data protection policies, contact our dedicated compliance desk:

  • Corporate Entity: Silkly B.V. (in formation)
  • Postal Domicile: [Registered Office Address in Amsterdam, The Netherlands – to be updated upon KVK registration]
  • Data Protection & Compliance Email: hi+compliance@silkly.top
  • General Operating Inquiries: hi@silkly.top