Grievance and Complaint Redressal Policy
1. Purpose
This Grievance & Complaint Redressal Policy (“Policy”) explains how individuals, customers, organizations, attendees, speakers, rights holders, and other affected persons may submit complaints, grievances, appeals, or concerns relating to services provided by CRUD INFOSYSTEMS PRIVATE LIMITED, operating under the brand name The cRUD Company (“cRUD”, “The cRUD Company”, “Company”, “we”, “us” or “our”).
This Policy is intended to provide a clear and accessible process for:
- general complaints;
- product grievances;
- privacy complaints;
- account or organization enforcement appeals;
- abuse reports;
- security-related concerns;
- copyright or intellectual-property complaints;
- billing-related complaints;
- complaints concerning webinar content or conduct;
- complaints relating to unlawful or harmful activity;
- other matters requiring formal review.
2. Scope
This Policy applies to complaints involving:
- The cRUD Company website;
- cRUD Webinar;
- cRUD-hosted webinar pages;
- registration pages;
- live sessions;
- replay or on-demand content;
- account administration;
- customer support;
- billing;
- communications;
- privacy;
- security;
- user-generated content;
- policy enforcement;
- other cRUD Services that reference this Policy.
3. Who may submit a grievance
A grievance may be submitted by:
- an Account holder;
- an Organization administrator;
- an Attendee;
- a speaker;
- a host;
- a webinar organizer;
- a Customer;
- a rights holder;
- a person affected by content or conduct on cRUD;
- an authorized representative;
- another person with a legitimate complaint concerning use of the Services.
4. General grievance contact
General grievances should be sent to:
Where a complaint is submitted to another cRUD address, we may internally route it to the appropriate function.
5. Specialist contacts
Certain complaints should preferably be submitted through the following channels:
Privacy and data-rights complaints
Security vulnerabilities or incidents
Copyright or intellectual-property complaints
Billing or refund issues
General support
Legal notices
A person will not ordinarily lose the right to have a complaint considered merely because it was initially sent to the wrong cRUD mailbox.
6. What information should be included
Where reasonably possible, a grievance should include:
- complainant name;
- email address;
- Account email, if applicable;
- Organization name, if applicable;
- relevant webinar or URL;
- relevant user or Organization;
- description of the issue;
- date or approximate date;
- supporting evidence;
- desired resolution;
- any prior support or complaint reference.
7. Emergency complaints
Where a complaint concerns an urgent risk involving:
- child sexual exploitation;
- credible imminent violence;
- active cyberattack;
- serious fraud;
- ongoing account compromise;
- other immediate serious harm;
the complainant should provide the available information without waiting to collect every possible detail.
cRUD may prioritize emergency matters ahead of ordinary grievances.
8. Acknowledgement
Where practicable, cRUD will acknowledge receipt of a formal grievance or complaint.
Acknowledgement does not mean:
- the complaint has been accepted as true;
- wrongdoing has been established;
- a particular remedy will be provided.
9. Initial review
After receiving a grievance, cRUD may conduct an initial review to determine:
- nature of the complaint;
- urgency;
- whether cRUD has jurisdiction or control;
- whether another specialist process applies;
- whether additional information is required;
- whether interim action is necessary.
10. Classification
A grievance may be categorized as:
- general service complaint;
- account complaint;
- privacy complaint;
- abuse report;
- security matter;
- intellectual-property complaint;
- billing dispute;
- enforcement appeal;
- legal complaint;
- safety matter;
- customer-controlled content complaint.
This classification is administrative and may change during review.
11. Requests for further information
We may ask the complainant for information reasonably required to understand or verify the complaint.
Failure to provide material requested information may limit our ability to investigate.
However, we will not request unnecessary information merely to discourage a complaint.
12. Identity verification
Where a grievance seeks:
- disclosure of personal information;
- Account restoration;
- Account deletion;
- billing changes;
- security-sensitive action;
- access to confidential information;
we may verify the identity or authority of the requester.
13. Authorized representatives
Where a person acts on behalf of another individual or Organization, we may require evidence of authorization.
14. Investigation
Depending on the complaint, cRUD may review:
- Account information;
- Organization information;
- activity logs;
- security logs;
- Customer Content;
- webinar records;
- communication records;
- billing records;
- abuse reports;
- support history;
- relevant technical information.
The scope of review will depend on the nature of the complaint.
15. Fairness
Where a complaint makes allegations against another user or Organization, cRUD may, where appropriate:
- seek their response;
- request clarification;
- consider available evidence;
- avoid unnecessary disclosure of complainant information.
cRUD is not required to conduct a court-style proceeding for every platform complaint.
16. Interim measures
Where reasonably necessary, cRUD may impose temporary measures while a complaint is being investigated.
These may include:
- temporary Account restriction;
- temporary suspension;
- disabling outbound email;
- restricting webinar publication;
- disabling content;
- limiting payment functionality;
- revoking access tokens;
- restricting integrations.
Interim action is not necessarily a final finding of wrongdoing.
17. Serious safety action
Where there is credible serious risk, cRUD may act immediately without waiting for completion of an ordinary grievance process.
18. Possible outcomes
Following review, cRUD may:
- take no action;
- provide information;
- correct an error;
- issue a warning;
- request remediation;
- restore access;
- remove or disable content;
- restrict functionality;
- temporarily suspend an Account;
- permanently terminate an Account;
- suspend or terminate an Organization;
- block an associated domain;
- provide a refund or credit where applicable;
- deny a refund;
- refer the matter to another process;
- preserve evidence;
- report or disclose information where legally required.
19. No guaranteed outcome
Submitting a grievance does not guarantee that cRUD will provide the remedy requested.
The outcome will depend on:
- evidence;
- applicable policy;
- law;
- technical capability;
- contractual rights;
- seriousness of the issue.
20. Abuse reports
Complaints alleging prohibited use should be assessed under the Acceptable Use Policy:
https://www.thecrudcompany.com/trust-center/acceptable-use-policy
21. Privacy grievances
Privacy grievances may concern:
- data collection;
- consent;
- correction;
- deletion;
- access;
- retention;
- marketing preferences;
- unauthorized disclosure;
- data security.
Privacy complaints should preferably be sent to:
22. Data Principal rights
Where a privacy complaint also constitutes an exercise of statutory privacy rights, cRUD will process it in accordance with applicable privacy law and the Privacy Policy.
23. Marketing complaints
A complaint about unwanted cRUD marketing may be handled through:
- unsubscribe controls;
- communication preferences;
- privacy contact;
- grievance process.
24. Operational communications
A request to stop optional marketing does not automatically stop essential:
- security;
- billing;
- account;
- legal;
- transactional;
- webinar-operational communications.
25. Security complaints
Security issues should be sent to:
Examples include:
- suspected vulnerability;
- compromised Account;
- credential exposure;
- malicious activity;
- unauthorized access.
26. Responsible security reporting
Security researchers should not conduct unauthorized destructive testing or access data that they are not authorized to access.
The absence of a public bug-bounty program does not authorize unrestricted testing.
27. Copyright complaints
Copyright and intellectual-property complaints should be submitted through:
and will be handled under:
https://www.thecrudcompany.com/trust-center/copyright-ip-infringement-takedown-policy
28. Billing grievances
Billing complaints may include:
- duplicate charge;
- incorrect amount;
- failed refund;
- renewal dispute;
- cancellation issue.
These should preferably be sent to:
29. Billing policy interaction
Billing grievances are also governed by:
https://www.thecrudcompany.com/trust-center/billing-cancellation-refund-policy
30. Account-enforcement appeals
A user or Organization affected by:
- suspension;
- termination;
- content restriction;
- domain blocking;
- other enforcement;
may request review by contacting:
31. Information for an enforcement appeal
An appeal should include:
- Account email;
- Organization;
- enforcement notice;
- relevant date;
- explanation;
- evidence;
- reason the user believes the decision should be changed.
32. Appeals do not automatically stay enforcement
Submitting an appeal does not automatically restore:
- Account access;
- content;
- email sending;
- webinar operation;
- Organization functionality.
Where continued access presents material risk, restrictions may remain in place.
33. Repeated appeals
We may decline repeated appeals that:
- raise no materially new information;
- are abusive;
- are intended primarily to obstruct enforcement.
34. Restoration after successful appeal
Where cRUD determines an enforcement decision was incorrect, we may:
- restore the Account;
- restore Organization access;
- remove restrictions;
- restore content;
- provide another appropriate remedy.
35. Webinar-content complaints
A person may complain about content appearing through a customer-operated webinar.
cRUD may consider:
- whether the content violates our policies;
- whether it is unlawful;
- whether the organizer controls the issue;
- whether valid legal process is required.
36. Customer responsibility
Not every disagreement with webinar content is a cRUD platform violation.
Customers are generally responsible for:
- webinar statements;
- speakers;
- marketing claims;
- offers;
- external links;
- Customer Content.
37. Ordinary commercial disputes
cRUD does not generally arbitrate ordinary disputes between:
- webinar organizers and attendees;
- Customers and their clients;
- speakers and organizers;
unless cRUD policies, law, billing, fraud, or safety issues are directly involved.
38. Defamation complaints
Where a complaint alleges defamation or reputational harm, cRUD may:
- review applicable policy;
- request supporting information;
- act on valid legal process;
- take action where the content independently violates another policy.
cRUD does not ordinarily determine complex defamation disputes without appropriate legal basis.
39. Illegal-content complaints
Where a complaint concerns alleged illegal content, cRUD may:
- review the complaint;
- seek legal guidance;
- restrict content where required;
- act upon valid governmental or judicial directions.
40. Government and law-enforcement requests
Government or law-enforcement requests should be directed to:
and should contain sufficient legal authority and identifying information.
41. Preservation
cRUD may preserve relevant records where reasonably necessary in connection with:
- legal disputes;
- abuse;
- security;
- fraud;
- investigations;
- valid government requests.
42. Confidentiality
We will seek to handle grievances with appropriate confidentiality.
However, complete confidentiality cannot be guaranteed where disclosure is required to:
- investigate;
- provide procedural fairness;
- comply with law;
- protect users;
- respond to authorities.
43. Reporter identity
Where appropriate and legally permitted, cRUD may avoid disclosing the identity of an abuse reporter.
44. No retaliation by cRUD
cRUD will not intentionally penalize a person merely for making a good-faith complaint.
This does not prevent action where the person independently violates cRUD policies.
45. False or malicious complaints
Knowingly false or malicious complaints intended to:
- harass;
- extort;
- disrupt competitors;
- trigger wrongful enforcement;
may themselves violate cRUD policies.
A complaint is not malicious merely because it is ultimately unsubstantiated.
46. Complaint records
We may retain records of grievances including:
- complainant;
- subject;
- date;
- evidence;
- classification;
- actions;
- outcome;
- appeals.
Retention will be governed by applicable law and our Data Retention & Deletion Policy.
47. Personal data in complaints
Personal data contained in grievances is processed under our Privacy Policy:
https://www.thecrudcompany.com/trust-center/privacy-policy
48. Complaint analytics
We may use aggregated grievance information to:
- identify recurring product problems;
- improve policies;
- identify abuse trends;
- improve safety.
49. Response times
cRUD aims to address grievances promptly.
Response time may depend on:
- urgency;
- complexity;
- evidence;
- legal requirements;
- third-party cooperation.
50. Statutory timelines
Where applicable law prescribes a specific grievance-response or action timeline, cRUD will follow the legally applicable requirement.
51. IT Rules compliance
Where cRUD is treated as an intermediary for a particular activity, applicable grievance-redressal obligations under the Information Technology framework may apply.
The current Indian IT Rules require covered intermediaries to publish details of their grievance mechanism and Grievance Officer and prescribe response/action obligations for specified complaints. The exact statutory obligation depends on cRUD's legal classification and the type of complaint. (meity.gov.in)
52. Grievance Officer
Where applicable law requires cRUD to formally designate a Grievance Officer, the applicable name and contact details will be published on the website and in this Policy.
Until a formal designation is required and completed, complaints may be submitted to:
53. Privacy grievance escalation
Where applicable under the Digital Personal Data Protection framework, an individual may have statutory avenues for grievance redressal beyond cRUD's internal process.
54. External remedies
Nothing in this Policy prevents a person from exercising rights available under applicable law.
55. Law enforcement emergencies
If competent authorities contact cRUD regarding an emergency, we may respond in accordance with applicable law.
56. Customer-controlled complaints
Where a grievance concerns processing controlled primarily by a cRUD Customer, we may direct the complainant to that Customer.
Examples include:
- why a Customer collected a registration field;
- how a Customer used exported attendee data;
- why a Customer sent a particular marketing message outside cRUD.
57. Assistance to customers
Where cRUD acts as a processor/service provider, we may reasonably assist customers in responding to valid privacy or legal complaints.
58. Grievances involving multiple organizations
Where a complaint concerns multiple Customers or third parties, we may separate the issue into distinct reviews.
59. Complaints involving external services
If the issue arises from a third-party service independently controlled by another provider, cRUD may direct the complainant to the relevant provider.
60. Availability of evidence
cRUD cannot guarantee that all historical information will remain available indefinitely.
Evidence may be subject to:
- deletion;
- retention cycles;
- legal obligations;
- technical limitations.
61. Customer-provided evidence
Persons submitting evidence must not unlawfully provide:
- stolen credentials;
- illegally intercepted communications;
- unlawfully obtained private information.
62. Sensitive evidence
Complainants should avoid sending unnecessary:
- passwords;
- payment credentials;
- highly sensitive identifiers.
Where evidence contains sensitive information, only the minimum reasonably necessary information should be provided.
63. Child-safety reports
Child-safety complaints will be treated as high priority.
cRUD may:
- restrict access immediately;
- preserve evidence;
- investigate;
- notify competent authorities where required or permitted.
64. Violent-threat reports
Credible imminent threats may receive immediate safety-oriented review and escalation.
65. Fraud reports
Fraud complaints may trigger:
- payment review;
- Account restriction;
- identity verification;
- evidence preservation.
66. Spam complaints
Spam complaints may result in:
- sender review;
- list provenance review;
- suppression;
- outbound-email suspension;
- Account enforcement.
67. Abuse complaints from email recipients
A recipient of cRUD-powered communications may report unwanted or abusive email through:
or any available unsubscribe/reporting mechanism.
68. Support complaints
Complaints about ordinary technical support may initially be handled through:
and escalated to grievance if unresolved.
69. Customer service escalation
Where a user is dissatisfied with support, they may request escalation through the grievance channel.
70. Complaint priority
We may prioritize based on:
- child safety;
- imminent violence;
- active security incidents;
- significant fraud;
- legal deadlines;
- privacy breaches;
- Account enforcement;
- ordinary service disputes.
71. No guarantee of compensation
A successful grievance does not automatically result in monetary compensation.
Any refund, credit, or other financial remedy is governed by:
- Billing Policy;
- contract;
- applicable law.
72. Service credits
Where a grievance concerns availability or service failure, cRUD may provide a credit where appropriate.
No automatic SLA credit exists unless separately agreed.
73. Complaints concerning policy updates
Users may submit feedback or complaints concerning changes to cRUD policies.
However, cRUD retains the right to modify policies in accordance with the Terms and applicable law.
74. Complaint withdrawal
A complainant may tell cRUD that they no longer wish to pursue an ordinary complaint.
cRUD may nevertheless continue review where:
- serious safety concerns exist;
- fraud is involved;
- legal obligations require action;
- serious abuse affects others.
75. Anonymous complaints
cRUD may consider anonymous complaints.
However, anonymity may limit:
- verification;
- follow-up;
- ability to provide a response.
76. Good-faith reporting
We encourage good-faith reporting of:
- abuse;
- security issues;
- privacy concerns;
- unlawful activity.
77. Enforcement confidentiality
cRUD may not disclose every detail of enforcement decisions because of:
- privacy;
- security;
- legal obligations;
- confidentiality;
- reporter protection.
78. Outcome communication
Where appropriate, we may inform the complainant that:
- the matter was reviewed;
- action was taken;
- no violation was identified;
- more information is required.
We may not disclose confidential disciplinary details concerning another Customer.
79. Internal escalation
Complex grievances may be escalated internally to:
- Company management;
- privacy function;
- legal function;
- security function;
- finance function.
At the current startup stage, these functions may be performed by the same authorized director or a small number of persons.
80. Conflict of interest
Where practicable, a person directly involved in the subject matter of a serious complaint should not be the sole reviewer of that complaint if another appropriate reviewer is available.
81. External advisers
cRUD may seek assistance from:
- legal counsel;
- security experts;
- auditors;
- other professional advisers
where required.
82. Complaint closure
A grievance may be considered closed where:
- appropriate action has been taken;
- no violation was identified;
- the complainant did not provide necessary information;
- the matter was referred elsewhere;
- no further action is reasonably available.
83. Reopening
A closed complaint may be reopened where new material evidence becomes available.
84. No waiver
Using this grievance process does not waive rights available under applicable law unless a valid settlement expressly provides otherwise.
85. Relationship to Terms
This Policy forms part of cRUD's broader contractual and governance framework.
Terms:
https://www.thecrudcompany.com/trust-center/terms-of-service
86. Relationship to AUP
Abuse and prohibited conduct are governed by:
https://www.thecrudcompany.com/trust-center/acceptable-use-policy
87. Relationship to Privacy
Privacy matters are governed by:
https://www.thecrudcompany.com/trust-center/privacy-policy
88. Relationship to Copyright Policy
IP complaints are governed by:
https://www.thecrudcompany.com/trust-center/copyright-ip-infringement-takedown-policy
89. Relationship to Billing Policy
Payment disputes are governed by:
https://www.thecrudcompany.com/trust-center/billing-cancellation-refund-policy
90. Policy changes
We may update this Policy due to:
- legal requirements;
- product changes;
- grievance-process improvements;
- organizational changes;
- regulatory requirements.
91. Versioning
Each material version will show:
- version;
- effective date;
- last updated date.
Canonical:
https://www.thecrudcompany.com/trust-center/grievance-complaint-redressal-policy
This Policy is published only at the canonical company website URL above. cRUD applications link to that canonical copy in a new browser tab and do not host duplicate legal-policy pages. A retired in-app legal route may redirect to the canonical URL, but must not render a separate copy.
92. Contact details
Grievances
General
Privacy
Security
Legal
Copyright
Support
Finance
Company
CRUD INFOSYSTEMS PRIVATE LIMITED Operating under the brand name The cRUD Company
Unit 101, OXFORD TOWERS 139, HAL Old Airport Road Kodihalli, Bengaluru, Karnataka 560008 India
This document is published by CRUD INFOSYSTEMS PRIVATE LIMITED, Unit 101, Oxford Towers, 139 HAL Old Airport Road, Kodihalli, Bengaluru, Karnataka 560008, India.
Return to Trust Center.