Providers and subprocessors
Concise register for the JOOOOB service. It keeps transparent where website, email, feedback and operational data may pass.
Register
| Provider | Role | Status | Potential data | Use | Note |
|---|---|---|---|---|---|
| Aruba S.p.A. | Hosting, domain, email | Active | Website technical data, voluntarily sent email | Website publishing and mailboxes | Not used for marketing analytics. |
| Google Search Console | Indexing | Active | Technical data and public URLs | Domain verification, sitemap and Google presence | Not a replacement for marketing analytics. |
| Microsoft Clarity | Behavioural analytics and usability | Only after Measurement consent | Technical interactions, clicks, scrolling and recordings with sensitive fields masked | Identify friction on public pages and in the purchase path | Excluded from the questionnaire, private dashboards, administration and storage. |
| Google Forms / Sheets | Service feedback | Optional | Client ID and non-sensitive feedback answers | Measure usefulness, clarity, personalisation and willingness to purchase | The form must not ask for CVs, phone numbers, LinkedIn or sensitive data. |
| Configured AI/API provider | Analysis and assisted writing support | To be confirmed based on operations | Minimised CV/profile, questionnaire and candidate-provided context | Generate or improve requested reports | Purpose-limited use. No automated eligibility decision. |
| GitHub | Code repository and technical documentation | Active for code | No real candidate data | Versioning website, templates and principles | Real data, CVs, questionnaires and reports must not be committed. |
| Optional candidate-provided source | Not a default subprocessor | Only public profile/link if explicitly provided | Voluntary professional context | No hidden scraping, credentials, cookies, spam or automation. |
Update rule
If a new provider starts processing client data, this register must be updated before operational use or as soon as the provider becomes stable.
When in doubt, treat the item as USER_CONFIRMATION_REQUIRED until verified.