Aquest document és vinculant en anglès; aquesta pàgina mostra el text en anglès.
Aprovat per SMARTEDTECH SL (propietari) · En vigor des del 1 de novembre de 2026
VUNZY Privacy Notice
1. Controller and data roles
1.1 Platform data. The Operator, SMARTEDTECH SL, Carrer Agricultura, 16, 1º, 9ª, 08320 El Masnou, Barcelona, Spain, is the controller of personal data processed to operate the platform: account, identity verification, acceptance records, payments, security, support, communications and analytics.
1.2 Provider supply data. Where a provider, asset licensor or sponsor supplies services, licences or sponsorship to a Vunz owner through the platform, that party is an independent controller of the data it needs for that supply (deal order, delivery and invoicing records), and the Operator is a controller of the platform-level record of the transaction. Each party complies with its own obligations; neither acts for the other.
1.3 Processor services. Where the Operator processes personal data on behalf of a business customer under the customer's instructions (for example an institution tenant's staff and cohort data), the Data Processing Agreement (DAT-01) applies and governs; it is signed as part of the order.
1.4 Sharing between SET platforms. Personal data is not shared with any other platform operated by the Operator or its group unless you enable the specific destination in your settings. Enabling one destination does not enable others, and you may disable it at any time.
1.5 International transfers. Personal data is stored in the European Economic Area. Where a processor outside the EEA is used, the transfer is covered by Standard Contractual Clauses listed in the subprocessor annex (DAT-02).
1.6 Data protection contact: Data Protection Contact — SMARTEDTECH SL, privacy@vunzy.net. A Data Protection Impact Assessment is maintained for the cohort, presence and profiling processing described in clauses 4 and 5 (registry reference dpia_ref, document VUNZY-DPIA-COHORT-PRESENCE); its conclusions are reflected in the thresholds stated in this notice.
2. Purposes, legal bases and data
| Purpose | Data | Legal basis | Your control |
|---|---|---|---|
| Account creation, authentication, tenant and role management | Name, email, password hash, role, tenant, acceptance records | Art. 6(1)(b) contract; Art. 6(1)(c) for acceptance evidence | Account settings; closure |
| Vunz creation, idea testing, connections, measured outcomes | Vunz content, selected sources, test parameters, results, connection requests, outcome entries | Art. 6(1)(b) contract | Private by default; you choose preview and publish |
| Subscriptions, deals, invoicing | Plan, billing email, payment-provider reference, invoices, deal orders | Art. 6(1)(b) contract; Art. 6(1)(c) tax and accounting | Account billing page |
| Security, abuse prevention, platform integrity | IP hash, user-agent hash, security logs, acceptance proof | Art. 6(1)(f) legitimate interest (documented assessment) | Object at privacy@vunzy.net |
| Support and complaints | Messages, case reference, order reference | Art. 6(1)(b) contract; Art. 6(1)(f) | Support route |
| Optional analytics | Usage events (see Cookie Notice) | Art. 6(1)(a) consent — purpose analytics_optional | Cookie banner "Manage"; footer link |
| Marketing email | Email, preferences | Art. 6(1)(a) consent — purpose marketing_email | One-click unsubscribe; account settings |
| Personalised recommendations and ranking of connections (profiling) | Vunz topics, activity, declared interests | Art. 6(1)(a) consent — purpose profiling_recommendation | Account settings; off by default |
| Research cohorts and model improvement | Pseudonymised Vunz and outcome data | Art. 6(1)(a) consent — purpose research_contribution, under the participant notice VNZ-01 | Account settings; off by default |
| Optional presence (region-level cohort) | Coarse region, time window | Art. 6(1)(a) consent — purpose presence_cohort (VNZ-01) | Account settings; off by default; revocable |
2.1 Mandatory fields are marked on each collection screen. Accepting the Member Account Terms is contract formation; it is not consent to any optional purpose. Each optional purpose has its own unticked control and its own withdrawal route.
2.2 The Operator does not use your Vunz content, uploads or conversations to improve models except under the research_contribution purpose, which you may withdraw at any time without affecting the service.
3. Prohibited evaluations
3.1 The platform is not used to identify individuals or to evaluate individuals for employment, credit, insurance, housing or health decisions. No consent control and no licence enables such processing on this platform.
3.2 No decision producing legal or similarly significant effects on you is taken solely by automated means. Where a Vunz, test or recommendation feeds a decision with legal, financial or safety effect, the decision is taken by you or by an authorised human reviewer.
4. Profiling and recommendations
4.1 Profiling for recommendations and connection ranking runs only when you have granted the profiling_recommendation purpose. Without it, recommendations use only the non-personal parameters stated on the listings page (MKT-01).
4.2 You may withdraw the purpose at any time in account settings; the profile derived from your data is deleted within 30 days of withdrawal.
4.3 The logic used is described on the recommendations page in plain language, and you may request human review of any recommendation at support@vunzy.net.
5. Cohorts, presence and publication
5.1 Participation in research cohorts is voluntary and governed by the participant notice for the specific study (VNZ-01), which states purpose, data, duration, sponsor and withdrawal rights. Withdrawal at any time is effective for future processing and does not affect services.
5.2 Aggregated or statistical results may be published; no result identifies a participant.
5.3 Where a study involves special-category data, it proceeds only under an explicit consent form and, where required, ethics approval stated in the notice.
5.4 Cohort and presence outputs are published only in aggregated form. A group is published only when it contains at least 5 participants (minimum-n 5); presence data expires and is purged no later than 24 hours after collection; adjacent or differenced queries that would isolate fewer than 5 participants are refused. Exact location is never shown to anyone.
5.5 Presence is off by default, separately opted into, and revocable at any time. Presence is not available to persons under 18.
5.6 The Operator does not collect special-category data for cohorts under this notice. A study that would require it is run only under its own explicit consent form.
6. Public-source business records
6.1 Business records displayed from attributed public sources are labelled "unclaimed / public source", limited to the fields permitted by the source licence, and processed on the basis of a documented legitimate-interest assessment. The business concerned receives the Art. 14 information through the record page and may claim, correct or remove the record at /legal/privacy-rights.
6.2 The platform does not copy or reproduce business databases whose licence prohibits it.
7. Recipients
7.1 Processors acting under the Operator's instructions: hosting, authentication, email delivery, payment processing, model inference and support tooling. The current subprocessor list, with function and location, is published at /legal/subprocessors and maintained under DAT-01 Annex C and DAT-02.
7.2 Independent recipients: the provider, asset licensor or sponsor party to a deal you enter (only the data needed for that deal); payment service provider for the purpose of payment; public authorities where required by law.
7.3 Other SET platforms: only per clause 1.4.
8. Retention
8.1 Account data is kept for the life of the account and deleted or anonymised within 90 days after closure, except where a longer period is required by law (tax and accounting records: 6 years; acceptance and consent records: 5 years after the end of the relationship, as evidence of compliance; records subject to a legal hold: until the hold ends).
8.2 Conversation logs, recordings and uploads not linked to an active contract are deleted no later than 12 months after the last interaction, and earlier on your request, unless a legal hold applies.
8.3 Backups are rotated on a cycle not exceeding 35 days; data deleted from production is removed from backups at the end of the cycle.
8.4 Where a provider is an independent controller, its own retention rules apply to its records.
8.5 Presence data: purged no later than 24 hours after collection. Research cohort data: pseudonymised for the study duration stated in VNZ-01, then aggregated or deleted. Profiling data: deleted within 30 days of withdrawal of the profiling_recommendation purpose.
9. Your rights
9.1 You may request access, rectification, erasure, restriction, portability and object to processing, and withdraw any consent prospectively as easily as it was given, through /legal/privacy-rights, privacy@vunzy.net or the postal address in the Legal Notice.
9.2 The Operator verifies identity proportionately (normally by confirmation from the account email) and responds within one month, extendable by two further months for complex requests with notice of the reason within the first month.
9.3 Erasure is limited only by the legal retention periods in clause 8.1, and the Operator states the scope and duration of any limit.
9.4 You may lodge a complaint with the Agencia Española de Protección de Datos (www.aepd.es) or with the supervisory authority of your habitual residence.
10. Security
10.1 The Operator applies tenant isolation, least-privilege and multi-factor access for privileged roles, encryption in transit and at rest, append-only acceptance and audit records, and tested restore procedures (DAT-01 Annex B).
10.2 Personal-data breaches are assessed on awareness; where the GDPR threshold applies the AEPD is notified within 72 hours and affected persons without undue delay (DAT-03).
11. Changes
11.1 The Operator may amend this notice for legitimate reasons: changes in law, in the service, in security or fraud prevention, in the payment provider, or to clarify wording. The Operator notifies you of material changes by email and in-product at least 30 days before they take effect (immediately where required by law or security).
11.2 A new purpose or a new category of recipient is enabled only after notice and, where consent is the basis, after your separate consent.
11.3 Every version is archived with its date and content hash at /legal/privacy/v/.