How we intend to handle your clients’ information.
Benefits data is sensitive, and a brokerage is accountable for it. These are the commitments shaping how the product is being built. They are design principles for software in development — not certifications, and not a compliance statement.
Minimum-necessary data
The analysis a renewal requires is mostly about populations, not individuals. The platform is being designed to work with de-identified or minimum-necessary data wherever the analysis allows, and to ask for identifiable detail only where it genuinely changes the answer.
Source traceability
A figure that can't be traced is a figure you can't defend. The design intent is that outputs point back to the document and the field they came from, so a number in a recommendation can be followed to its origin rather than taken on faith.
Visible, editable assumptions
Every model rests on assumptions — trend, enrolment, credibility, timing. Ours are meant to be shown rather than buried, and changed by the broker when their judgment differs from the default.
Broker review before anything leaves
Nothing is intended to reach an employer without the broker reviewing and approving it. The platform is being built to prepare and support a recommendation, not to issue one.
Evidence and advice kept apart
What the data shows and what you advise are different things, and conflating them is how analytical tools mislead. The product should keep the observation and the recommendation visibly distinct.
Uncertainty stated, not smoothed over
Where the inputs are incomplete or the data doesn't support a conclusion, the right output is to say so. A confident answer built on thin evidence is worse than a stated gap.
What we don’t claim yet.
Aelana does not currently hold any security or compliance certification. We are not claiming HIPAA compliance, SOC 2, HITRUST, or adherence to any specific security standard, and we won’t until it is genuinely in place and independently verified.
We also have no paying customers, no validated results, and no benchmarks drawn from customer data. Every product example on this site uses a fictional employer and invented figures.
If you need to know exactly what is implemented today before a conversation is useful, ask us directly and we’ll tell you plainly.
Questions about data handling?
If your firm has requirements we’d need to meet, those are useful to hear early — while the architecture is still being decided.