Contact Vowise
Need help with Vowise? Start with the route that matches your question. Product setup and troubleshooting often have a faster answer in Help or Docs. For account, billing, privacy, product feedback, or partnership questions that need a person, send Vowise a message with enough context to understand the request — but never include passwords, API keys, full payment-card details, or unrelated sensitive transcripts.
Quick Support Routing & Security Policy
Common setup and app issues can be solved immediately via Help and Docs. For manual review, provide your platform, what happened, and account email. Never send passwords, private keys, or unmasked sensitive transcripts.
Find the Best Contact Route
To resolve questions quickly and protect private information, review the specific guidance for each topic before sending a message.
Product Help & Troubleshooting
If recording, transcription, installation, Shortcuts, API access, sync, media capture, or another product workflow is not working, start with the Help Center and Troubleshooting guide.
Information to include:
- •Your operating system and platform (Web, Mac, Windows, iOS, Android)
- •The Vowise app version or build number if visible
- •The action you attempted and what happened instead
- •A safe screenshot or concise error message if available
Account & Billing Questions
Get direct support for your account status, subscription plan, renewal, cancellation, invoice/receipt, or credit refund requests.
Information to include:
- •The registered email address associated with your Vowise account
- •Where the purchase was made (Web, Apple App Store, or Google Play)
- •Transaction order identifier or receipt date (no card numbers)
Privacy & Data Requests
Submit questions or requests regarding personal data processing, audio recordings, transcription retention, analytics preferences, or account deletion.
Information to include:
- •Specific privacy question or statutory data subject request
- •Account identification email for verification
Product Feedback & Ideas
Found a workflow that is confusing, missing, or slower than it should be? Tell us about your use case and how Vowise can better support your personal knowledge flow.
Information to include:
- •Your concrete workflow or daily use case
- •What you tried to accomplish and what felt friction-heavy
- •The expected outcome that would solve your problem
Partnerships & Business Inquiries
For creator collaborations, software integrations, enterprise deployments, tool directories, or media inquiries, tell us about your proposal.
Information to include:
- •Overview of your organization, audience, or platform
- •Proposed collaboration scope and tangible next steps
- •Key decision or timeline for initial review
Before Sending: General Checklist
Vowise handles speech, audio, and personal thinking. Protecting your privacy and account security requires clear boundaries before any message is transmitted.
What to include in your message
- ✓What you are trying to accomplish
- ✓The relevant platform or purchase surface
- ✓The first step that failed or the question that needs a decision
- ✓A safe screenshot or short error message with private text obscured
- ✓Your account email only when account lookup is actually needed
What to NEVER send
- ✕Account passwords, OTPs, or recovery keys
- ✕Secret API keys or cloud service tokens
- ✕Full payment card numbers, expiry dates, or CVV security codes
- ✕Full private audio recordings, medical notes, or sensitive transcripts
- ✕Unrelated personal identifiers or third-party private data
Concrete Examples by Category
Technical or Sync Issue
Recommended format:
“Windows 1.1.x. I saved a note on desktop around 14:10 UTC and cannot see it on iOS. I already signed out and back in once. Screenshot attached with private text hidden.”
Avoid doing this:
Pasting complete raw transcript logs containing sensitive conversations, or sending your account password.
Subscription or Billing Inquiry
Recommended format:
“My account email is [email protected]. The subscription was purchased through Apple App Store on Oct 12. I need assistance with invoice receipt lookup.”
Avoid doing this:
Sending full 16-digit credit card numbers, CVV security codes, or asking support to override platform-level App Store refund policies.
Partnership or Integration Proposal
Recommended format:
“We develop [Product]. We would like to explore an export workflow or joint case study. Next step: a 20-minute product review call next week.”
Avoid doing this:
Mixing urgent end-user app bugs into a partnership pitch or submitting vague requests without organizational context.
Send Vowise a Message
Select the appropriate topic and share the necessary context. Our support and partnerships team will follow up via email.
Official Contact Channels
Whether you need technical troubleshooting, billing support, privacy actions, or partnership discussions, every message is reviewed by our team.
Privacy note: Never send passwords, full payment card numbers, secret API keys, or full private transcripts in your message.
Frequently Asked Questions
Everything you need to know about reaching Vowise, response paths, and safety practices.
How should I contact Vowise for product support, billing, privacy, or partnerships?
Choose the path that matches your request: start with the Help Center (/help) and Troubleshooting guide (/docs/support/troubleshooting) for self-serve setup and recovery; contact support with your account email and purchase surface for billing, subscription, or refund questions; use the privacy path after reviewing the Privacy Policy (/privacy-policy); or submit structured feedback and partnership proposals through the contact form.
What details should I include in a technical support request?
Include your platform (Web, macOS, Windows, iOS, or Android), the app version or build number if visible, the exact action you attempted, what you expected to happen, what occurred instead, the approximate timestamp, and a safe screenshot or error message if available. Never send passwords, secret API keys, authentication tokens, full card details, or private transcripts.
Where should billing, cancellation, refund, or account questions go?
Submit your inquiry through the contact form or email [email protected], specifying your account email address and purchase surface (Web, Apple App Store, or Google Play). Pricing, subscription terms, and refund eligibility are governed by the applicable Vowise Terms of Service and store policies.
Where should privacy or data-handling questions go?
Review the current Vowise Privacy Policy (/privacy-policy) first. For personal data inquiries, transcript storage questions, or deletion requests, contact support using the privacy topic with only the minimal details necessary to identify and resolve your request.
How do I submit product feedback or business partnership inquiries?
For product feedback, describe the specific workflow, what you tried to accomplish, and the result you expected. For creator partnerships, integrations, distribution, or business proposals, provide an overview of your organization, the proposed collaboration, and the immediate decision to discuss.
What sensitive information should never be sent in a support message?
Never include passwords, secret API keys, authentication tokens, full payment-card numbers, CVV security codes, or full private transcripts in any general contact message or screenshot.
Looking for a product answer rather than waiting for a person?
The Help Center, product documentation, and troubleshooting guides stay available 24/7 while support requests are being reviewed.