What exists today
One flagship product, fully public-facing.
Voryn already has its own product page, privacy policy, terms, support page, and App Store path. The studio site is where those surfaces stay coherent instead of drifting apart.
About
This site exists to give the products a stable public home: one place for the app page, privacy policy, support path, and product writing that explains what is real today.
Right now the clearest expression of the studio is Voryn, an iPhone capture tool for people who think out loud and want the result to stay useful. That focus is deliberate. The goal is not to inflate the studio with a maze of placeholder brands or unrelated landing pages. The goal is to make one real product legible and maintainable.
That is also why the site keeps the surrounding surfaces close to the product itself. Privacy, terms, and support are treated as maintained parts of the app system rather than afterthought documents pasted into a footer.
What exists today
Voryn already has its own product page, privacy policy, terms, support page, and App Store path. The studio site is where those surfaces stay coherent instead of drifting apart.
Why start here
Independent software is easier to trust when the claims stay close to the actual app: what capture feels like, what export exists, what privacy language is justified, and where support really lives.
How support works
For product issues, use the app-specific support page whenever possible. For general inquiries, partnerships, or press, email [email protected].
Studio posture
The technical stack is intentionally compact, but the real commitment is operational: keep public information stable, keep product claims inspectable, and make it easy for users to know what the software does before they commit to it.
Current standard
Every app should have a readable landing page, product-linked privacy language, and a support path that asks for enough context to make the reply useful.
Current focus
The site is English-first today because that is the fastest route to a stable public product surface, but the underlying structure is designed to support a broader content system as the studio grows.