Complaint Policy
How users can raise complaints about billing, accounts, service issues, misuse, content, or privacy concerns.
Step 1: Contact Support First
A user should first contact Urmate through the published support channel before raising the matter elsewhere. The first message should explain the issue in plain language, mention the affected account, and state what resolution the user is asking for. This helps the support team separate technical issues, billing issues, content disputes, misuse reports, and privacy requests without unnecessary delay.
The user should avoid sending repeated messages across multiple channels unless the issue is urgent or the first channel is unavailable. Duplicate complaints may slow down review because the team has to match conversations, verify identity, and avoid acting on incomplete or conflicting information.
Step 3: Internal Review
flyingdarkdev reviews complaints based on the information provided, account records, payment records, product logs, and applicable policy. The team may classify a complaint as billing, privacy, safety, content, service availability, partner dispute, legal notice, or general support. The classification can change if new facts appear during review. Internal review does not mean that every complaint will be accepted exactly as requested.
Users should respond to clarification requests within a reasonable time so the matter can move forward. If a user refuses verification, submits incomplete documents, or uses abusive language, the review may be paused, closed, or escalated for safety handling.
Step 4: Response Timeline
Urmate aims to reply to ordinary support and complaint requests within a practical business timeline. A first acknowledgement may be sent earlier, while final resolution may take longer where payment gateways, infrastructure providers, AI providers, banks, or third-party systems are involved. Security, privacy, account takeover, and payment failure reports may require identity checks before any action is taken.
Users should keep the same email thread active and provide requested proof promptly. No response timeline should be read as a guarantee of a specific outcome, refund, account restoration, or legal decision because each matter depends on facts and applicable law.
Step 5: Escalation
If the first support response does not resolve the matter, the user may escalate by emailing grievance@urmate.tech. The escalation message should include the original support ticket, registered email, issue summary, requested resolution, and any evidence already shared. Escalation is meant for unresolved matters, privacy concerns, serious safety issues, and complaints where the user believes the first response missed important facts.
Users should not open unrelated tickets just to create pressure or bypass verification. flyingdarkdev may combine duplicate threads, reject abusive escalations, and preserve records where misuse, fraud, chargeback abuse, or policy violation is suspected.
Step 6: External Remedies Where Applicable
If a complaint remains unresolved and the user has a lawful basis, the user may use official government or legal channels that apply to the matter. For consumer matters, the National Consumer Helpline may be relevant. For cyber crime, fraud, account compromise, or online abuse, the National Cyber Crime Reporting Portal may be appropriate. These external resources are controlled by their respective government authorities and have their own processes.
Urmate cannot file a government complaint on behalf of a user unless a separate written arrangement exists. Users remain responsible for choosing the correct external forum, submitting truthful information, and understanding that official authorities may ask for additional proof or identity verification.
7. Non-Eligible or Restricted Cases
Some requests under this Complaint Policy may not be eligible for approval even when the user is dissatisfied. Common restricted cases include consumed digital credits, completed custom work, user-side configuration mistakes, repeated policy abuse, account suspension for serious violations, unsupported use cases, provider outages outside direct control, late requests, missing proof, and requests that contradict checkout terms or written agreements.
Users should review product details and plan limits before purchasing or using features. flyingdarkdev may still offer support, workaround guidance, credit adjustment, or goodwill resolution where appropriate, but such action does not create a permanent obligation or precedent for future cases.
8. Fraud, Abuse, and Misuse
The platform treats fraud prevention seriously because misuse harms genuine users and increases costs for the service. Misuse can include fake accounts, repeated refund attempts after heavy use, chargebacks filed without contacting support, false complaints, threatening messages, coupon abuse, stolen payment instruments, account sharing, bot activity, fake partner claims, or attempts to access services without valid payment.
Users should raise honest issues with accurate facts and should not use complaint channels as pressure tactics. flyingdarkdev may deny requests, suspend accounts, preserve evidence, block payment methods, limit future purchases, or report serious misuse to appropriate authorities where legally permitted.
9. Third-Party Dependency
Many Urmate features depend on third-party services such as payment gateways, AI providers, hosting providers, analytics systems, email services, OAuth providers, and infrastructure vendors. A third-party outage, delay, pricing change, model issue, API limit, bank reversal, or verification requirement may affect the timing and outcome of a request. The business will make reasonable efforts to coordinate where required, but it cannot control external systems.
Users should understand that external provider timelines are separate from internal support timelines. Where a matter depends on a payment gateway, bank, government portal, or provider, final handling may be subject to that third party's records, rules, and investigation process.
10. Communication Standards
Users and support staff are expected to communicate respectfully and clearly during review. A firm complaint is acceptable, but abusive, threatening, discriminatory, defamatory, spam-like, or harassing communication may lead to limited support, account restrictions, or escalation for safety review. The business may consolidate multiple tickets about the same issue to avoid duplicate work.
Users should use the published support or grievance email and avoid contacting team members on personal channels. flyingdarkdev may preserve communications where required to investigate fraud, abuse, safety threats, legal notices, payment disputes, or repeated misuse of support resources.
11. Internal Decision Making
Decisions under this Complaint Policy are made after considering account records, payment records, product logs, user submissions, provider responses, and applicable policy. The reviewer may approve, reject, partially approve, request more information, offer a workaround, or escalate the matter. A decision is not based only on user dissatisfaction; it depends on facts, proof, eligibility, service status, and policy terms.
Users may ask for one reasonable re-review if they provide new information or show a clear error. Repeated requests without new evidence may be closed to protect support resources and avoid inconsistent handling.
12. Business Protection
This Complaint Policy is intended to protect users while also protecting flyingdarkdev from unclear claims, misuse, operational loss, and avoidable disputes. The policy does not remove rights that cannot be excluded under applicable law, but it records the practical conditions under which the business will review requests. It also explains where the business may need to refuse a request because of abuse, missing proof, third-party limits, or legal obligations.
Users should keep their own records and should not rely only on memory or informal chat messages. The business may update internal processes, templates, verification standards, and timelines as the product grows, provided published user-facing policies remain reasonably clear.
13. Limitation of Liability
To the extent permitted by applicable law, flyingdarkdev is not liable for indirect loss, lost profit, loss of data, loss of opportunity, reputational harm, or business interruption connected with complaints about service issues, billing, content, misuse, safety concerns, privacy requests, and partner conduct. This limitation is especially relevant where the issue results from user error, third-party provider failure, bank delay, internet outage, unsupported use, failure to read plan terms, policy misuse, or reliance on AI output without review. Mandatory legal rights are not limited where law does not allow limitation.
Users should maintain backups, check outputs, and avoid using the service as the only system for critical obligations. Where liability cannot be fully excluded, it will be limited in the manner stated in the Terms and Conditions unless applicable law requires otherwise.
14. Changes to this Complaint Policy
This Complaint Policy may be updated when products, payment methods, providers, laws, business processes, or operational risks change. The latest version will show a Last Updated date. Future changes normally apply going forward, but some changes may also apply to open requests where required for legal compliance, security, fraud prevention, or to correct an obvious error. Material changes may be communicated through the website or dashboard where practical.
Users should review the policy before making a purchase, submitting a request, or entering a partnership. Continuing to use the service after an update may be treated as acceptance where applicable law permits.
15. Escalation and Contact
Questions under this Complaint Policy should be sent to support@urmate.tech; unresolved or serious concerns may be escalated to grievance@urmate.tech. The message should include the registered email, issue type, timeline, proof, requested resolution, and any previous ticket reference. This allows the team to review the history without starting from zero and reduces the chance of a wrong decision.
Users may approach official portals where legally applicable after internal review or where the matter requires official action. These policies are provided for general business transparency and user information. They should be reviewed by a qualified legal professional before production use. External portals are not controlled by flyingdarkdev, and their content or availability may change without notice.
Useful official resources
These are external official resources. Urmate is not responsible for their content, process, uptime, or availability.