Yes — and that is exactly what the split is for. Verification and everyday activity are deliberately kept apart. Your Core ID is the verified, high-trust side of your identity. Your aliases are the anonymous side you actually use day to day.
What verification touches: KYC verification is attached to your Core ID. It moves you through three states — unverified, pending, and verified — and a verified identity carries an associated trust score.
What services actually see: When you sign in somewhere with an alias, that service does not receive your Core ID. Because everyday activity runs through an unlimited number of aliases rather than one single identifier, different services cannot cross-reference your behaviour across the internet.
Even for developers, it is gated: Reading KYC status and trust score through the API requires a specific sensitive-data permission that has to be requested explicitly and granted — it is not part of ordinary profile access.
A simple rule of thumb: Use an alias by default. Reach for the Core ID only where a service genuinely needs a verified, high-trust identity.