Content Protection and AI Policies
SievePage actively protects your pages, portfolio, and uploaded work from scraping, AI training, and bulk harvesting.
Your content is never used for training
Anything you upload to SievePage belongs to you. Artwork, reference sheets, WIP files, commission previews, gallery video and audio, 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.
We don't run your work through AI either
Blocking outside AI is only half of it. On our side, your uploaded work is never fed to an AI model, never analyzed by one, and never turned into a dataset. No AI reads, processes, or learns from your art, files, or media anywhere in SievePage. ♡
AI crawlers are blocked
We block AI training and harvesting bots at multiple layers before they can reach your work. That keeps the known AI companies out, and stops AI tools from bulk-reading your pages.
We block a broad and growing set of AI training and harvesting crawlers, including:
- OpenAI (GPTBot)
- Anthropic (ClaudeBot, anthropic-ai)
- Google AI (Google-Extended)
- Common Crawl (CCBot), ByteDance (Bytespider), Meta (Meta-ExternalAgent), Amazon (AmazonBot), Apple (Applebot-Extended)
- Commercial harvesters such as Diffbot and Omgilibot, among others
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. ♡
You control how AI sees your pages
AI tools that bulk-read your pages to build training datasets are turned away by default. Your artist profile and portfolio aren't pulled into AI training data without your permission.
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.
A different kind of AI protection
There are two broad ways to keep your art away from AI. One alters the image pixels on your own computer before you post online. AI models trip over it during training, but it's a never-ending cat-and-mouse game with the models, and the protection remains on that one exported file.
SievePage's approach mirrors the one used by Cloudflare, The New York Times, and major publishers like Condé Nast, The Atlantic, and the groups behind Rolling Stone, Variety, and IGN: instead of touching your art, we keep the AI crawlers from reaching it in the first place.
- It's automatic. Your whole page is protected the moment you post, not with a tool you run on each image and nothing is done to your pixels.
- It's where the web is heading. As of July 2025, Cloudflare blocks AI crawlers by default for new sites, and over a million sites have switched on one-click AI blocking. We build the same thing in.
- Your art stays untouched. Full quality and exactly how you made it.
An honest note on what's possible
We will always be straight with you: no platform can make public art truly uncopyable, whatever they promise. If a page can be opened in a browser, the picture on it can be saved. That holds here, and everywhere your work is public, from social media to other portfolio sites.
What we are doing is making it harder to do so. We turn away the known AI companies and the obvious scraping tools, and slow down anything trying to grab your work in bulk. It stops the easy, automated harvesting that is almost all scraping, while keeping your page public so clients and community can still find you.
We could hide your files so only you could open them, but that would pull your work out of Google image search and break the previews that show your art when you share your page. Being findable is part of the point. We would rather give you strong, honest protection than promise a secrecy no one can deliver.
We hope you continue making the world better with your beautiful art ♡
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 community 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.
Working on something you're not ready to show? Hide the card, or on Pro, keep the whole page private until it's ready to share.
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 encrypted at rest and in transit, stored on hardened cloud infrastructure in the United States with redundant, continuously backed-up copies, so your work is never at risk from a single point of failure.
Files are delivered through a global CDN so they load quickly for visitors anywhere, while the primary copy 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.
These protections are enforced in more than one place, so the same rules always apply no matter how your page is reached.