Acceptable Use Policy

Do not use LickityClick to promote, facilitate, or conceal illegal activity, fraud, scams, malware, credential theft, phishing, exploit delivery, botnets, evasion tools, or content that creates a real-world safety risk.

Do not use the Service for spam, unsolicited bulk messaging, misleading links, impersonation, link cloaking designed to deceive users or platforms, fake giveaways, fraudulent affiliate activity, or evasion of marketplace, email, search, social, advertising, or affiliate-program rules.

You may not use LickityClick for content involving sexual exploitation, non-consensual imagery, child sexual abuse material, extremist violence, targeted harassment, doxxing, hate activity, or instructions for serious harm. Regulated products or services must comply with applicable laws and platform rules.

Do not probe, scan, fuzz, scrape, overload, reverse engineer, or attack the Service or other customers. Do not bypass rate limits, abuse APIs, automate signup to create disposable accounts, interfere with redirects, or use the Service to hide traffic from security systems.

If you use LickityClick for affiliate, sponsorship, paid promotion, or advertising campaigns, you are responsible for required disclosures, truthful claims, brand and affiliate-program compliance, and destination-page accuracy. LickityClick does not review or certify your marketing claims.

LickityClick may apply rate limits, bot filtering, redirect protection, storage limits, API limits, domain limits, or other safeguards to protect the Service. Usage that threatens reliability or materially exceeds normal plan expectations may require an upgraded plan or custom agreement.

We may investigate suspected violations and may remove links, disable custom domains, throttle traffic, suspend accounts, preserve evidence, report activity to providers or authorities, or terminate service when needed to protect users, customers, infrastructure, or Client Amp LLC.

To report abuse, email abuse@lickity.click with the short link or domain, destination URL if known, screenshots or headers if relevant, and a short explanation of the issue. We review reports and take action based on risk, evidence, and applicable law.