Community Guidelines
Rules for safe, respectful, and lawful use of community, collaboration, chat, and shared workspace features.
1. Purpose of the Community Guidelines
This Community Guidelines explains how Urmate handles community spaces, chat, comments, collaboration, study groups, shared projects, and user interaction in a practical and transparent manner for users in India and other eligible locations. The purpose is to reduce confusion before a purchase, request, application, partnership, or complaint is made. It also protects the business by recording clear rules on verification, timelines, misuse, documentation, approvals, and cases where a request may be refused.
Users should read this page before relying on any assumption made from advertisements, screenshots, informal chats, or third-party claims. If a product page, invoice, written contract, or law gives a user a stronger right than this page, that specific document or law may apply to that extent.
2. Scope and Applicability
This page applies to community spaces, chat, comments, collaboration, study groups, shared projects, and user interaction connected with the website, dashboard, paid plans, free trials, digital tools, AI features, templates, support conversations, and partner or admin-managed services. It covers ordinary user requests as well as special cases involving respectful conduct, spam prevention, content safety, moderation, reporting abuse, and account action.
Users should not assume that one policy applies to every transaction or service type. A future enterprise agreement, custom statement of work, reseller contract, or written partner agreement may override parts of this general page for the specific customer or partner named in that agreement.
3. User Responsibilities
Users must provide accurate information, use the correct account, preserve proof, and contact support within a reasonable time when an issue appears. Important records may include order ID, invoice ID, transaction reference, registered email, screenshots, browser details, timestamps, relevant URLs, conversation history, and a clear explanation of what happened. A request made without basic proof may take longer or may be rejected after review.
Users should not send altered screenshots, fake payment proof, misleading timelines, abusive language, or unrelated personal data. flyingdarkdev may close requests that appear fraudulent, duplicated, threatening, spammy, or designed to bypass the product rules rather than resolve a genuine issue.
4. Verification Before Action
flyingdarkdev may verify identity, account ownership, payment status, usage history, entitlement records, and policy compliance before taking action under this Community Guidelines. Verification protects users from unauthorized account changes and protects the business from fraud, false complaints, chargeback misuse, and accidental disclosure of private information. The level of verification depends on the request and the risk involved.
Users should reply from the registered email wherever possible and provide only necessary proof. If verification fails, the business may refuse account changes, refunds, cancellations, access restoration, deletion requests, partner approvals, or grievance actions until the required information is provided.
5. Timelines and Review Process
The review timeline depends on the type of request, completeness of information, payment gateway status, provider response time, business days, holidays, and whether security or legal review is required. Simple requests may be resolved quickly, while disputed transactions, alleged misuse, data requests, partner reviews, account compromise, or complaints involving third parties may take longer. Acknowledgement is not the same as approval, refund, restoration, or acceptance of liability.
Users should keep one active thread and respond to clarification requests in time. flyingdarkdev may pause or close a request if the user does not respond, sends inconsistent information, or raises the same issue repeatedly without new facts.
6. Documentation Required
The user may be asked to provide documents or details that are reasonably connected to the request. For payment matters, this can include invoice ID, order ID, transaction reference, amount, date, payment method, and gateway status. For account matters, it can include account email, affected URL, device details, screenshots, and steps to reproduce. For partner, career, or legal matters, additional business or identity information may be required.
Users should redact unrelated sensitive data and must not submit forged, altered, or misleading records. Documents are reviewed only for the relevant matter and may be retained where needed for audit, legal, security, accounting, or fraud-prevention purposes.
7. Non-Eligible or Restricted Cases
Some requests under this Community Guidelines 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 Community Guidelines 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 Community Guidelines 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 community spaces, chat, comments, collaboration, study groups, shared projects, and user interaction. 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 Community Guidelines
This Community Guidelines 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 Community Guidelines 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.
16. Community Moderation
Community features should be used for learning, collaboration, support, and productive discussion. Harassment, hate, threats, explicit abuse, spam, impersonation, illegal content, doxxing, phishing, malware, manipulated media, fake offers, and repeated disruption are not allowed. Moderation may include warnings, content removal, feature limits, group removal, account suspension, or permanent ban depending on severity.
Users should report harmful content with screenshots, URLs, usernames, and context rather than retaliating. flyingdarkdev may preserve moderation records and cooperate with appropriate authorities where legally required or where serious harm, cyber crime, fraud, or safety risk is involved.
Useful official resources
These are external official resources. Urmate is not responsible for their content, process, uptime, or availability.