Contact OXEFY
Choose the enquiry type that best matches your request. Product, services, partnership, platform-review, privacy, and security enquiries are routed through the appropriate OXEFY workflow.
Enquiry categories
Each category has an internal routing target, required context, priority, and sensitive-data warning. Routing targets are workflow labels, not public email addresses.
Questions about OXEFY products, product ownership, product pages, or future product direction.
Do not include passwords, API keys, tokens, private keys, payment-card data, government ID, health data, or sensitive personal data.
Questions about Vocalis features, platform access, data handling, user control, or product-review context.
Do not include platform passwords, account secrets, access tokens, private keys, or content that should not be shared through a general enquiry.
Questions about AI product development, SaaS, automation, content systems, advisory, MVP, or fitness-technology services.
Share only the context needed to assess fit. Do not include confidential credentials, customer records, or regulated data.
Partnership, collaboration, business-development, or ecosystem conversations.
Do not include confidential deal terms, passwords, private documents, or financial account details.
Provider review requests for LinkedIn, Meta, Google, payment providers, API providers, or partner review teams.
Include provider name, product/application, review reference, requested evidence, and relevant public URL when useful. Do not include secrets or private keys.
Questions about privacy foundations, data categories, rights routing, deletion process planning, or contact-data handling.
Do not include unnecessary sensitive personal data. Use concise context and wait for an appropriate channel if detailed information is needed.
Security, vulnerability, suspicious activity, or product-security reporting.
Do not include credentials, passwords, API keys, tokens, private keys, payment-card data, or exploit code through a general form.
Founder, company, product, publishing, or media-related questions.
Do not include embargoed or confidential material until an appropriate channel is confirmed.
General company or business questions that do not fit the other categories.
Keep the message concise and avoid secrets, regulated data, or private account details.
Contact form
Activation requirements
Until secure transport is active, the website shows enquiry routing, public trust links, and setup status instead of a live submission flow.
Floor No. 6, Ruia Chambers, In front of Amanora Gold Towers, Amanora Park Town, Hadapsar, Pune - 411028, Maharashtra, India.
Platform and API review
Platform and API reviewers can use public routes for product, ownership, policy, and security context while the delivery workflow is being configured.
Security reporting
Security reporting is routed through Contact until a dedicated security mailbox is confirmed.
Privacy guidance
When the form is activated, OXEFY will use enquiry information to review, route, and respond to the request. Retention, deletion, recipient routing, and final privacy wording remain pending owner and legal review.
Review Privacy Policy foundation Review Data Deletion InstructionsResponse expectations
Response expectations will be published after mailbox ownership, routing, working hours, escalation paths, and support process are confirmed.
Contact FAQ
These answers are written for the current secure-transport-pending state.
No. The contact form interface is prepared, but delivery is disabled until secure transport and recipient routing are confirmed.
Recommended domain mailboxes exist in the internal A7 plan, but they are not published until created, verified, and approved as public.
Provider name, product/application, review reference, requested evidence, and relevant public URL are useful. Secrets and private credentials should not be submitted.
Use concise non-sensitive context through the Contact route. OXEFY may request more information through a secure channel after triage.
No public response-time promise is made until mailbox ownership, routing, working hours, and escalation processes are confirmed.
Verification links
Use these public routes while contact transport and domain mailboxes are being configured.