Privacy

Your career history is personal.

This notice describes the current Sulog Start implementation. Product behavior should remain aligned with this notice as the service evolves.

What Sulog may collect

Campaign and referral attribution, a visitor/session identifier, your selected career intent, location, employment status, recent role, education and context you choose to provide. You may also provide a CV and contact details such as email or mobile number.

Why Sulog uses it

To create and maintain your candidate state, generate a first useful result, support later career decisions, measure activation and service cost, protect public endpoints from abuse, and improve the product.

AI processing

When enabled, Sulog uses OpenAI to process submitted context and generate structured career outputs. Do not submit information you do not want processed for that purpose.

Storage and service providers

The current production architecture uses hosted application infrastructure, a private object store for submitted documents and a server-side database for candidate and product state. Access credentials and service-role keys are not exposed to the public browser.

Research data is separate

Public community research is not used to silently create candidate profiles. Raw research identities stay in the research layer. Shared research evidence is aggregate or anonymized.

Your choices

A CV is optional. Some intake context is optional. Sulog records consent before profile processing and contact follow-up. Self-service privacy controls are still being expanded, so do not submit information you do not want retained as part of your Sulog candidate record.

What Sulog does not sell

Sulog is a for-profit service, but its commercial model is paid career search and decision support. The product is not designed around selling identifiable candidate data to advertisers or employers.

Changes

This notice will change as account controls, additional channels, payment features and market integrations are introduced. Material changes should be reflected here before the related feature becomes public.