Content Protection and AI Policies
SievePage actively protects your pages, portfolio, and uploaded work from scraping, AI training, and bulk harvesting. Here's what we do and why.
Your content is never used for training
Anything you upload to SievePage belongs to you. Artwork, reference sheets, WIP files, commission previews, and documents are yours. We don't use your content to train AI models, sell your data, or share your uploaded files with anyone outside what's needed to display them to you.
AI crawlers are blocked
We block AI training and harvesting bots at the server level, enforced in our API. Your work won't end up in a training dataset, and AI tools can't bulk-read your pages.
Blocked crawlers include:
- GPTBot and ChatGPT-User (OpenAI)
- ClaudeBot and anthropic-ai (Anthropic)
- Google-Extended (Google AI training)
- PerplexityBot (Perplexity)
- CCBot (Common Crawl)
- Bytespider (ByteDance / TikTok)
- Meta-ExternalAgent (Meta)
- AmazonBot (Amazon)
- Applebot-Extended (Apple AI training)
- Diffbot and Omgilibot (commercial harvesters)
This list isn't static. We're hard at work on adaptive protection that spots and blocks new AI scrapers the moment they appear, plus more controls that let you decide exactly how your work can be used. Your art stays yours, full stop. no bots allowed ♡
AI agents can't browse your pages
AI search assistants and agentic frameworks that browse and summarize creator content are blocked from indexing your work. Your artist profile and portfolio won't show up in AI-generated search results or summaries without your permission.
Your work belongs to you, not to an AI intermediary.
Scraping protection
Every request to your public profile goes through bot detection and rate limiting. Automated scrapers are identified and throttled before they can bulk-harvest your portfolio or commission queue. Legitimate visitors and search engines are not affected.
Public pages vs. private pages
Public pages (your sieve.page/username profile) are visible to anyone, including search engines. We protect them from scraping and AI training, but they are intentionally public. That's how clients and fans find you.
Private pages are only visible to you and anyone you explicitly invite. They aren't indexed by search engines and aren't accessible to bots.
For sensitive work-in-progress content, we recommend keeping cards or pages set to private until you're ready to share publicly.
File upload security
Files can only be uploaded to your account through SievePage. Our storage is locked to the SievePage platform. Upload requests from external scripts, terminal tools, or third-party sites are rejected automatically.
This means no one can inject files into your account from outside the platform, and your storage quota can only be consumed by you through normal use.
Where your files are stored
All uploaded files are stored on AWS S3 infrastructure in the United States (US East, Virginia). Files are encrypted at rest using AES-256 and transmitted over TLS. Storage uses multi-availability-zone redundancy with continuous versioned backups so your work is never at risk from a single point of failure.
Files are delivered through a global CDN spanning 90 cities across 47 countries, so your work loads quickly for visitors anywhere in the world. Edge caching is temporary. The primary copy of your files always stays on US-based infrastructure.
Our storage infrastructure is SOC 2 and GDPR compliant.
How we block unauthorized content
SievePage enforces a strict Content Security Policy on every page. Your browser is only allowed to load images, files, scripts, and connections from a pre-approved list of trusted sources. Everything else is blocked at the browser level before it can execute.
This protects you in a few concrete ways:
- Malicious scripts can't run. Even if an attacker found a way to inject code into a page, the browser would refuse to execute it.
- Your files only load from our CDN. Images and media on SievePage can only be served from our storage infrastructure, never swapped out for content from unknown domains.
- Your data stays on secure connections. The browser is only permitted to send data to trusted endpoints over HTTPS, blocking man-in-the-middle attacks.
- SievePage can't be embedded in malicious iframes. This prevents clickjacking, where an attacker tricks you into clicking something hidden inside a fake page.
This policy runs on both the SievePage app and our API, two independent layers enforcing the same rules.