Acceptable Use Policy

1. Purpose and scope

This policy protects ASCA users, organizations, connected services, and platform integrity. It applies to every ASCA account, organization workspace, website, API, integration, module, upload, and automated action.

Organization rules may be more restrictive, but they cannot authorize conduct prohibited here.

2. Authorization and security

You must not:

• Access or attempt to access an account, organization, system, record, API, integration, or device beyond your authorization.
• Share credentials improperly, bypass authentication, evade rate or usage limits, or defeat tenant and permission controls.
• Probe, scan, exploit, reverse engineer, or disrupt ASCA except within a separately authorized security-testing program.
• Introduce malware, malicious documents, destructive code, denial-of-service traffic, credential theft, or unsafe automated requests.
• Use ASCA to compromise or interfere with a connected service.

3. Harmful and abusive conduct

Do not use ASCA to harass, threaten, stalk, exploit, deceive, impersonate, or endanger another person. Prohibited conduct includes sexual exploitation, non-consensual intimate content, credible threats, targeted abuse, doxxing, human trafficking, and attempts to exploit or groom minors.

ASCA is not an emergency service. Contact the appropriate local emergency service when someone faces imminent harm.

4. Fraud, spam, and manipulation

Do not use ASCA for fraud, scams, phishing, spam, fake engagement, deceptive fundraising, payment abuse, chargeback abuse, account farming, artificial eligibility, reward manipulation, false organization affiliation, or misleading commercial activity.

Do not manipulate voting, attendance, identity, membership, moderation, storage, rental, event, reward, or transaction records.

5. Content and intellectual property

Do not provide content that you lack the right or authority to use. Do not use ASCA to distribute illegal content, malicious files, counterfeit goods, or content that violates another person’s privacy, intellectual property, or publicity rights.

Lawful criticism, accessibility activity, interoperability, and protected security research are not prohibited merely because they are inconvenient or critical.

6. Moderation and automation

Do not attempt to evade or poison moderation, submit adversarial content to cause unauthorized action, impersonate a moderation notice, or use an automated assessment as a substitute for required human, legal, medical, or safety judgment.

Organizations must use A.M.A.R. and M.A.C.R.O. only for authorized communities and must configure actions, permissions, review paths, and notices responsibly. Automated output is not guaranteed to be accurate.

7. High-risk workflows

ASCA must not be used to:

• Administer a government election or represent Aaravos as government-certified.
• Provide emergency dispatch, medical diagnosis, legal advice, insurance, or regulated professional services.
• Hide, destroy, or fabricate evidence required for a safety, payment, voting, employment, legal, or organizational process.
• Sell prohibited or dangerous goods or evade sanctions, export, licensing, tax, consumer-protection, or payment restrictions.
• Condition a protected report, complaint, accommodation, vote, or moderation appeal on a reward or waiver of rights.

8. Data collection, scraping, and surveillance

Do not systematically collect, scrape, index, aggregate, enrich, sell, or redistribute non-public ASCA information without documented authorization. Public availability of a profile, listing, event, or page does not authorize bulk harvesting, identity correlation, facial recognition, stalking, surveillance, targeted harassment, or creation of a competing database.

Do not use pixels, web beacons, fingerprinting, hidden fields, deceptive links, or other passive collection mechanisms through ASCA content unless the applicable organization, user notice, consent, platform permission, and law allow that collection.

Authorized search engines, accessibility tools, archives, integrations, security systems, and research activities must respect technical controls, purpose restrictions, privacy, rate limits, and revocation.

9. Communications and community features

Do not use ASCA messaging, forms, comments, reviews, notifications, webhooks, voice, or connected channels to distribute unsolicited bulk communications, malicious links, deceptive promotions, unauthorized advertising, pyramid schemes, manipulated reviews, or content intended to overwhelm a person or service.

Do not falsely present a message as an ASCA notice, organization decision, moderation action, payment request, official emergency communication, or communication from another person. A sender must honor the audience, consent, unsubscribe, quiet-hour, organization, and connected-platform controls that apply to the communication.

10. Commerce, rewards, events, and physical services

Do not use ASCA to offer counterfeit, stolen, recalled, unsafe, illegal, or prohibited goods or services. Sellers, organizers, venues, suppliers, partners, and organizations must accurately describe material price, eligibility, inventory, fulfillment, refund, safety, sponsorship, contribution, reward, and role information.

Prohibited conduct includes:

• creating fake orders, attendance, referrals, reward activity, disputes, or fulfillment records;
• manipulating a queue, capacity, ballot, contest, benefit, or eligibility decision;
• concealing material event, product, venue, accessibility, safety, or cancellation information;
• using a payment, donation, sponsorship, credit, or reward label to disguise a different transaction;
• offering a prize, stored-value-like instrument, regulated item, or restricted service without the required approval; and
• using ASCA records to claim insurance, licensure, certification, tax status, institutional approval, or legal authority that has not been verified.

11. Misuse of support, reports, and enforcement

Do not submit a knowingly false abuse, copyright, security, payment, safety, privacy, accessibility, or legal report. Do not retaliate against a good-faith reporter, witness, reviewer, voter, complainant, or person exercising an applicable right.

Support and review channels must not be used to obtain another person's data, evade organization authority, pressure staff to disclose protected evidence, or repeatedly relitigate a resolved matter without new information. A mistaken or unsubstantiated good-faith report is not prohibited merely because it does not result in action.

12. Enforcement

ASCA may investigate reported or detected misuse and may limit content, credentials, integrations, actions, or account access. ASCA will scope enforcement to the documented risk and its authority.

An automated signal, organization rule, human review, platform decision, and executed action are separate. Review and appeal options are described in the Content Moderation and Enforcement Policy.

Enforcement may include warning, content restriction, quarantine, credential rotation, integration limitation, transaction hold, feature suspension, organization-access restriction, account suspension, preservation, referral to a responsible organization, or legally required reporting. The action depends on severity, confidence, authority, recurrence, risk, available alternatives, and mandatory obligations.

ASCA may preserve relevant records and coordinate with an organization, connected service, payment provider, rights holder, safety contact, or authority where permitted and necessary. Enforcement does not guarantee that harmful material will be detected or that ASCA can reverse an independent party's action.

13. Reporting

Report suspected misuse through [email protected]. Do not include passwords, payment credentials, illegal content, or unnecessary sensitive evidence in ordinary email. ASCA may provide a protected intake method when needed.