Minimal structure, no names
Just what the assistant needs not to miss the point when it matters. Marital status, children yes or no, city, profession. No third-party identifiers. If you write names, the system rejects them.
What it captures
Structure, not biography. Marital status with seven options (including "prefer not to say"), whether you have children yes or no, how many and in which generic age bands, your city and profession. One row per user, transversal to all your profiles.
Why it matters
When you ask an AI to help plan your 8-year-old daughter's birthday, it matters that it knows she's 8 — not what her name is. Structure is actionable. The specific name is exposure without value to the AI.
How it's built
Single form, free editing. Re-verification every 6 months with a soft banner in the dashboard — no nagging, just a reminder. Confirming takes one click.
🔒 Privacy — rule zero
This layer NEVER stores names of children, partners, bosses, or other people. If you include them in any free field, the backend validator rejects the request with a 422 error and clear message. Structure yes, names no, no exceptions.
FAQ
- Why can't I put names?
- Because they expose third parties who haven't consented. The AI works just as well with "my 8-year-old daughter" as with "Mary, 8". The name only adds risk, no value.
- Is it included in all plans?
- Yes. Essential, Premium and Professional all include vital context.
- What if I divorce or move?
- You edit the row. The layer updates and the AI injects the new state in the next conversation.
- When will I be asked to reverify?
- 6 months after last verification. Friendly banner, blocks nothing.