Policies for a better community.

1. Adults-only access and age assurance

GreenGlass is intended only for people aged 18 or older. A person under 18 may not create an account, access adult areas, participate in communities, or use another person's account. Users must provide truthful age information and must not evade restrictions through alternate accounts, VPNs, false documents, or another person's identity.

• Self-declared birth dates are not sufficient verification for a high-risk adult-content service. Before production, use a reputable age-assurance provider that is lawful in each target jurisdiction, proportionate to risk, accessible, and privacy-preserving.
• Prefer an age-over-18 token/result over collecting or retaining identity documents or exact birth dates. Do not store raw identity documents unless a reviewed legal and security basis requires it.
• Keep adult-only content behind server-enforced access checks. A hidden button, client-side checkbox, or URL obscurity is not access control.
• Provide a documented appeal process for mistaken age decisions. Minimize retained evidence and limit staff access.
• Do not permit any sexualization of minors, grooming, sexual solicitation of minors, or sexual content involving anyone under 18, including fictional or AI-generated depictions where prohibited by applicable law or this policy.

2. Terms of Service — draft

By creating an account or using GreenGlass, you agree to these Terms, the Community Guidelines, the Privacy Notice, and any additional rules shown for specific features. If you do not agree, do not use the service. GreenGlass may update these documents and will provide notice when required by law.

Accounts

• Provide accurate registration information, protect your credentials, and promptly report suspected account compromise.
• You are responsible for activity performed through your account except where applicable law says otherwise.
• Do not sell, rent, transfer, impersonate, or use accounts to evade enforcement.
• We may require age assurance, account verification, rate limits, or security checks to protect users and the service.

Permitted use

Use the service lawfully and respectfully. You retain rights you hold in your own content, while granting GreenGlass only the limited permissions needed to host, process, display, transmit, moderate, and back up that content to operate the service. The final production terms must specify the exact licence, termination effects, and retention practices.

Service availability

Features may change, be interrupted, or be removed. We will not promise uninterrupted availability, end-to-end encryption, secure deletion, or global legal compliance unless those capabilities are actually implemented and verified.

Liability and consumer rights

Any disclaimers, limitations of liability, indemnities, dispute-resolution clauses, governing-law provisions, and arbitration clauses must be drafted for the actual operating entity and jurisdictions. Nothing in these draft Terms removes rights that cannot legally be waived.

3. Community Guidelines

These rules apply to profiles, avatars, banners, messages, servers, channels, voice/video, files, invites, reactions, bots, and other content or behavior on GreenGlass.

• Zero tolerance for child exploitation: no child sexual abuse material (CSAM), grooming, sextortion, sexual solicitation of minors, sexualized depictions of minors, or attempts to recruit, identify, or contact minors for sexual purposes. Do not upload, request, save, or redistribute suspected CSAM. Report it immediately; do not circulate it as evidence.
• No non-consensual intimate content: no revenge porn, hidden-camera sexual content, sexual deepfakes, or intimate imagery shared without explicit consent. Consent to creation does not automatically mean consent to distribution.
• No exploitation or coercion: no trafficking, forced sexual activity, blackmail, threats, doxxing, stalking, or blackmail involving intimate media.
• No credible threats or targeted abuse: no threats of violence, targeted harassment, hateful attacks against protected groups, or coordinated abuse campaigns.
• No illegal activity: no content or instructions facilitating serious crimes, exploitation, trafficking, terrorism, or the sale of illegal goods. Applicable laws vary by location.
• No malware or scams: no phishing, credential theft, malicious files, fraud, deceptive impersonation, or spam campaigns.
• No privacy violations: do not publish private addresses, phone numbers, identity documents, account credentials, private communications, or other personal data without a lawful basis and appropriate consent.
• No dangerous encouragement: no encouragement or instruction to commit suicide, self-harm, or violence against others.
• No evasion: do not use alternate accounts, edited media, coded language, or bots to evade moderation, age restrictions, blocks, or suspensions.
• Respect intellectual property: do not upload infringing material or impersonate creators, brands, or public figures in a deceptive way.

4. Mature and adult content policy

GreenGlass may permit lawful adult-only mature content only after robust age assurance, reporting, moderation, and access controls are implemented. Being an 18+ platform does not make every type of content lawful or permitted.

• Sexually explicit content may only appear in clearly labeled, access-controlled adult areas and may not appear in general profile surfaces, public previews, default avatars, banners, server icons, notifications, or other areas visible before age checks.
• All depicted people must be adults and have consented to the creation and distribution of the material. Uploaders must have the rights and consent required by law.
• Prohibit any sexual content involving minors, apparent minors, age-ambiguous youthful depictions, incest involving minors, grooming, coercion, trafficking, or exploitation.
• Prohibit non-consensual intimate imagery, sexual deepfakes of identifiable people without explicit consent, voyeurism, blackmail, and content created through coercion.
• Prohibit unlawful extreme violence, terrorist propaganda, illegal sexual material, and content whose distribution is prohibited in the relevant jurisdiction.
• Offer user controls to hide, blur, or opt out of sensitive content where feasible. Do not show explicit media by default in previews or push notifications.
• Use age-restricted server/channel flags enforced by backend rules, not client-only UI. Moderators who can access adult content must meet applicable age and training requirements.

Before enabling this category, obtain specialist advice on local laws covering pornography, obscenity, consent, age assurance, record-keeping, image-based abuse, and platform liability in every target market.

5. Safety, reporting, and urgent escalation

Users should be able to report a message, profile, server, channel, file, or account without confronting the reported person. Production reporting must create a server-side case with a unique ID, timestamp, target reference, reason, and status, and it must be visible only to authorized trust-and-safety staff.

• For immediate danger, contact local emergency services. GreenGlass is not an emergency response service.
• Report suspected child sexual exploitation, grooming, sextortion, credible threats, non-consensual intimate media, trafficking, doxxing, and account compromise using the in-product reporting flow once deployed.
• Do not download, repost, or forward suspected CSAM. Preserve only lawful, minimal case metadata and follow applicable mandatory reporting and evidence-handling rules.
• Restrict access to reports and sensitive media; log staff access; establish response-time targets, escalation owners, retention schedules, and lawful disclosure procedures.
• Provide blocking, muting, server/channel restrictions, invite revocation, message deletion, account suspension, and appeals where appropriate.
• Publish a verified safety contact and legal-notice address before launch. Do not invent contact information or claim a report has been filed when no system exists.

6. Privacy Notice — draft

The final notice must accurately describe the deployed system, controller/operator identity, contact details, data categories, purposes, legal bases where applicable, processors, transfers, retention, security, and user rights. Do not publish this draft as a complete privacy notice until those facts are filled in.

Data minimization

• Collect only data needed for accounts, safety, abuse prevention, service operation, legal obligations, and user-requested features.
• Prefer age-over-18 results over raw identity documents or exact birth dates where lawful and sufficient.
• Do not claim messages are end-to-end encrypted unless end-to-end encryption is implemented and independently assessed.
• Set clear retention periods for messages, reports, logs, backups, and account deletion. Legal holds and safety investigations may require limited exceptions disclosed in the final notice.

User rights and security

• Provide workable access, correction, export, deletion, objection, and consent-withdrawal processes where applicable law grants those rights.
• Use least-privilege access, strong authentication for staff, encryption in transit, appropriate encryption at rest, secure backups, incident response, and vulnerability management.
• Assess processors and international data transfers, publish subprocessors where required, and provide a breach notification process that meets applicable deadlines.
• Do not sell personal data or expose private messages to advertisers. Be precise about analytics, cookies, telemetry, and third-party SDKs.

7. Copyright and intellectual property

Do not upload content that infringes copyright, trademarks, publicity rights, or other rights. GreenGlass must implement a jurisdiction-appropriate notice-and-action process, a counter-notice or appeal mechanism where required, repeat-infringer rules where applicable, and a designated legal contact. A valid notice should identify the work, the allegedly infringing material, its location, the claimant's contact details, and the required good-faith statements under applicable law.

Do not use a notice process to silence lawful criticism, parody, fair use/fair dealing, or other legally protected speech. The final process and forms need counsel review for each relevant jurisdiction.

8. Legal compliance and jurisdictional limits

No single web page can guarantee compliance with every law worldwide. Obligations depend on the operating entity, where users live, the service's scale, content categories, data processing, and whether the service is legally classified as an intermediary, hosting provider, online platform, or another category.

• India: assess the Information Technology Act and applicable rules, intermediary due-diligence and grievance requirements where applicable, the Digital Personal Data Protection Act 2023 and DPDP Rules 2025 commencement timetable, consumer-protection and advertising rules, criminal laws, copyright, and applicable child-protection obligations.
• European Union/EEA: assess GDPR, the Digital Services Act, e-Commerce rules where applicable, national age-assurance and audiovisual rules, consumer law, and country-specific criminal and image-abuse laws.
• United Kingdom: assess UK GDPR and Data Protection Act, Online Safety Act duties and Ofcom codes/guidance, age-assurance requirements for regulated content, and applicable criminal law.
• United States: assess federal and state privacy laws, Section 230 and its limits, DMCA notice-and-takedown and designated-agent requirements where applicable, child-protection and reporting duties, intimate-image laws, consumer protection, and state age-verification laws.
• Other countries: assess local privacy, intermediary, content, age-assurance, consumer, copyright, law-enforcement request, and data-localization requirements before making the service available there.

Use a jurisdiction matrix and a launch decision for each country: permitted, restricted, or unavailable. Establish a legal-request process, government-request review, preservation procedures, and transparency reporting where appropriate. This draft is not an exhaustive inventory of laws and must not be represented as legal advice.

9. Enforcement, appeals, and transparency

Enforcement may include content removal, warning labels, adult-content restrictions, temporary feature limits, server restrictions, suspension, or permanent termination. Consider severity, context, history, and immediate risk while applying consistent rules.

• Provide a reason for significant enforcement actions where lawful and safe.
• Offer a secure appeal route and human review for consequential cases, except where disclosure would create a safety risk or violate law.
• Use audit logs and restrict moderator access. Staff must not use privileged access for personal reasons.
• Publish periodic transparency data about reports, actions, appeals, government requests, and child-safety escalation where legally appropriate and operationally feasible.
• Do not promise automated detection is perfect. Provide human escalation for serious cases and test systems for bias, false positives, and evasion.

10. Required before production launch

• Verified age-assurance vendor and documented fallback/appeal process.
• Server-side Firebase/Firestore rules and automated tests; no client-only permission enforcement.
• Shared real-time data model for users, servers, memberships, roles, channels, messages, attachments, and invites.
• Server-side reporting queue, trained moderators, escalation playbooks, and verified safety/legal contacts.
• Privacy impact assessment, retention schedule, data-subject request workflow, incident response plan, processor agreements, and breach process.
• Adult-content access restrictions, sensitive-media preview controls, consent rules, and removal process.
• Abuse protections: rate limits, spam detection, account recovery safeguards, block/mute, invite revocation, audit logs, and ban evasion handling.
• Accessibility, mobile/desktop testing, load testing, backup/restore drills, security review, and penetration testing.
• Country-by-country legal review and finalized operating entity, contact details, terms, and policies.