FAQ

A focused guide to accuracy, input methods, privacy, and subscription rules
Feb 13, 2026

YlanAI FAQ

A focused guide to accuracy, input methods, privacy, and subscription rules.

1. Quick Start

What does YlanAI do, and what problems is it best for?

YlanAI is a structured analysis assistant for decision support.
It is most useful when you need priority, timing, and risk-aware action planning.

What should I prepare before starting?

Prepare these first:

  • calendar type (Gregorian or Lunar)
  • birth time (as precise as possible)
  • birthplace (at least city-level)
  • one focused core question
Should I use Gregorian or Lunar? How should leap month be written?

Either is accepted, but calendar type must be explicit.
For Lunar input, always specify leap month or non-leap month.

I already have Four Pillars. Do I still need Gregorian/Lunar input?

Usually no.
If Four Pillars are accurate, submit Four Pillars directly with gender tag, hour branch, and birthplace.

Is birthplace/timezone important? Do I need true solar time?

Yes. Birthplace affects timezone and boundary mapping.
True solar time is recommended for borderline time cases.

2. Birth Hour and Accuracy

Why must birth hour be accurate? What changes if it is off?

Birth hour can affect chart structure and phase rhythm, which may change:

  • risk ranking
  • action order
  • timing-window judgment
What if my birth hour is uncertain?

Use a range-comparison workflow:

  1. provide a plausible hour range
  2. run nearby hour charts
  3. keep conclusions stable across variants
  4. validate with real life events
Why is my Four Pillars result different from other platforms?

Common causes:

  • timezone or DST handling differences
  • true solar time setting differences
  • leap-month handling differences
  • date-boundary conversion differences

Align parameters first, then compare.

What does "accuracy" mean in YlanAI? Is any result guaranteed?

Accuracy here means consistent inference, clear explanation, and actionable recommendations.
It does not mean guaranteed outcomes.

What if output does not fit my experience?

Use this correction loop:

  1. recheck input precision
  2. narrow to one core question
  3. add real-world constraints
  4. rerun and compare differences

3. Prompting and Report Use

How do I ask questions more effectively?

Ask one goal at a time and provide complete input context.
Include at least: Four Pillars, gender tag, birth hour, birthplace, current residence, and the output type you want.

Bazi: Renyin Renyin Renyin Renyin, Male, Tiger hour
Birthplace: Manhattan, New York, United States
Current residence: Toronto, Ontario, Canada
Please provide a structured view of wealth tendencies, risk boundaries, and practical actions for reference.
What modules can appear in one analysis?

Modules are not fixed and may change by version, question type, and input completeness.
Common modules include core profile, career, relationship, wealth, rhythm guidance, and action list.

How should I read the report without misinterpreting it?

There is no mandatory fixed order.
A practical path is: conclusion and scope -> reasons and risks -> actions and review point.

How long does one analysis take? What controls output length?

Most first-pass outputs return within minutes.
Length depends on question complexity, input quality, follow-up depth, and module coverage.

Do follow-ups improve quality? How do I follow up efficiently?

Yes, if focused.
Change one variable per follow-up and compare strategy shifts.

4. Boundaries and Safety

Which topics should not rely on YlanAI as the only basis?

Do not use as sole basis for:

  • medical decisions
  • legal decisions
  • compliance decisions
  • major financial commitments
  • investment advice or return guarantees
Can I treat this service output as a final conclusion?

This service output is generated automatically by AI and may contain errors, omissions, or content that does not fit individual circumstances, and it is not medical, legal, or investment advice.
You should make independent decisions based on your real situation and objective information. For medical, legal, compliance, and major financial matters, consult qualified professionals.

Will YlanAI make deterministic claims about disease, lifespan, or accidents?

No. YlanAI does not provide deterministic prediction for disease diagnosis, lifespan, or accidents, and does not treat any output as a medical or legal conclusion.
The reason is simple: these topics are high-risk and must rely on real-world evidence plus professional evaluation. Deterministic AI claims can mislead users, create panic, and lead to poor decisions.
If you care about these areas, this service can only provide reminders at the lifestyle and risk-management level, such as stress and routine guidance, phase-based risk alerts, and practical response ideas. It does not replace professional judgment.
For health, legal, compliance, and major financial matters, consult qualified professionals and rely on real examinations and evidence.

Can minors use YlanAI? Is guardian guidance needed?

Minors should use it under guardian guidance.
Output should not be the sole basis for major education or life decisions.

If I am anxious or emotionally overwhelmed, when should I seek help?

If symptoms persist, daily function drops, or self-harm thoughts appear, seek licensed mental health support or local emergency resources first.

5. Privacy and Data

Will my birth information be stored, leaked, or publicly exposed?

In analysis scenarios, YlanAI does not publicly expose your submitted input.
Input is not used for unrelated external publication.

Can I delete history records? How do I clear data?

Yes.
If history is enabled in your account context, remove entries from your history page based on available UI options.

Is my data used for training or shared with third parties?

No. YlanAI does not use your birth details, prompts, or chat records for model training, and does not sell or share them with any third party.
By default, we do not retain your personal inputs or conversation content for long-term storage; you can also delete conversations or clear history anytime in the product.
Unless required by law or explicitly authorized by you, we do not retain or provide such content externally.

6. Subscription and Credits

Why subscribe or buy packages? What do I get?

Plans provide usable credits and stable usage capacity for different usage frequencies.

What are credits? How much is charged per request?

Credits are the billing unit.
Current rule: one full analysis request is counted as 100 credits.

What counts as one request? How are follow-ups billed?

A request is counted when a full inference run is triggered.
Follow-ups that trigger a new full run are billed again.

What happens to unused credits at cycle end?

Current rule: remaining credits are cleared at expiry and do not roll over.

What if I run out of credits?

You can:

  • upgrade your subscription
  • purchase additional credits
Can I upgrade, downgrade, or cancel? When does it apply?

Subscription management is supported.
Effective timing depends on current billing and payment-provider rules.

Monthly vs yearly plans: what is different? Can I switch?

Main differences are billing cycle and unit economics.
Yearly plans usually have lower unit cost. Switching depends on active billing rules.

Do you support refunds? When can compensation apply?

Consumed service is generally not eligible for unconditional refunds.
For duplicate charges or platform-side exceptions, submit a support ticket for review and compensation handling.

7. Common Issues

Send failed, lag, or no response. What should I do?

Try this order:

  1. refresh and retry
  2. check network and extension conflicts
  3. split long input into smaller submissions
  4. retry outside peak traffic
Chart generation failed or says data is incomplete. What now?

Recheck:

  • calendar type
  • leap-month flag for Lunar dates
  • completeness of birth time and birthplace
  • timezone consistency
Why are credits consumed faster than expected?

Common causes:

  • high-frequency follow-ups
  • repeated reruns of the same task
  • too many goals in one request

Efficiency tip: ask one core question at a time, then iterate in steps.