Privacy
Make clear what information is needed, why it is used, and what choices people have. Define collection, AI processing, retention, and deletion practices before public release.
OUR MISSION
More agency.
Less overwhelm.
For more people.
Develop affordable, accessible applications that help neurodivergent people, individuals with disabilities, and families manage everyday life.
Support should fit the person using it.
People bring different strengths, capacities, responsibilities, and ways of processing the world. Our aim is to build useful assistance without making a single way of working the standard everyone has to meet.
Build for possibility.
Design for real life.
OUR DESIGN COMMITMENTS
Care belongs in the details.
These principles guide the choices we’re making as we develop our products.
Affordability
Design for practical value at an accessible price. Communicate costs and limits clearly so people can decide whether the product fits their needs and budget. Pricing is still being developed.
User autonomy
Make suggestions easy to understand, adjust, and decline. A person should be able to pause, change direction, or decide that a task can wait without being pressured by the product.
Inclusive design
Consider cognitive, sensory, and physical needs together. Prioritize clear language, manageable choices, keyboard access, readable interfaces, and control over unnecessary motion.
Accessibility is part
of the starting point.
People shouldn’t have to work harder to get the support they need.
For this website, that means clear structure, readable contrast, keyboard navigation, responsive layouts, and respect for reduced-motion preferences. Across our products, we aim to make accessibility an ongoing practice.
Our design target is WCAG 2.2 Level AA. We welcome feedback about anything that makes the experience difficult to use.
Read our accessibility statementRESPONSIBLE ASSISTANCE
Trust comes from
understandable choices.
Assistive tools may be used in personal moments. These are the product decisions we intend to make explicit as the applications develop.
Know what is being shared
Explain the information needed for a feature, whether processing happens locally or through a service, and what is retained. Ask for permissions in the context where they matter.
Review the important details
Keep suggestions distinguishable from source information. Make room to correct a summary, verify a deadline, or reject a proposed action before relying on it.
Choose the level of support
Let people control what is communicated, who can access their information, and which connections they use. Caregiver involvement should have clear boundaries.
PRIVACY & ACCESSIBILITY QUESTIONS
What we can say today.
What happens to information entered into the website demo?
The AddvancedFocus prototype keeps selections and return notes in the current page’s memory. They are not sent to an AI service or saved to browser storage. Leaving the product page or refreshing clears them.
What happens when I email Biro.dev?
An email link opens your email app. The message is sent only when you choose to send it, and it passes through your provider and Biro.dev’s inbox. Contacting us does not subscribe you to a mailing list.
Will the applications use local or cloud AI?
The technical design is not finalized. We intend to explain processing, retention, user controls, and the limits of offline functionality for each product before public release. No particular AI provider or processing arrangement is announced here.
Has this website been certified accessible?
No certification or completed conformance audit is claimed. WCAG 2.2 Level AA is the design target. The draft includes structural, keyboard, contrast, and reduced-motion provisions, but a complete browser and assistive-technology review is still required.
How can I report an accessibility barrier?
Email founder@biro.dev with the page and what made it difficult to use. If helpful and comfortable, include the device, browser, or assistive technology involved. A short description is enough to start the conversation.
Send accessibility feedbackTHIS WEBSITE, RIGHT NOW
Try the idea.
Your notes stay here.
The concept runs in your browser. There is no sign-up, live AI request, analytics script, or marketing cookie in this draft.
Return notes and example selections stay in page memory. They are not sent anywhere or saved to browser storage, and they disappear when you leave the product page or refresh.
This describes the website demo. The future product’s data practices will be published separately before release.
A CONNECTED VISION
Useful on its own.
Connected by choice.
The long-term goal is shared support without requiring the entire suite.
We envision optional sharing of accessibility preferences, authorized reminders, and relevant context across Biro.dev products. Each connection should be understandable, permission-based, and controlled by the person using it.
Affordability, privacy, accessibility by design, and offline functionality where practical are intended foundations of the product family. Core accessibility should be part of the experience, rather than a premium upgrade.
This is a future design direction. Cross-product connections and offline capabilities have not been released; pricing and technical details remain in development.
HELP SHAPE WHAT COMES NEXT
Better support starts
with real conversations.
Share an everyday challenge, a question, or a perspective that could make our work more useful.
Talk with the founder