01 Overview & scope
CrownInternet.ai (“we,” “us”) serves other businesses—we write software, operate hosting you ask for, and help with design. We are not building a consumer lifestyle app. This policy covers colleagues who visit crowninternet.ai or collaborate with us using a signed estimate, work order, umbrella agreement, or anything similar.
If a separate attachment spells out who owns which privacy duties for a system we run on your behalf (sometimes called “controller” vs “processor” language in Europe), that paperwork governs that system. Everything here is the general picture.
If an NDA or services contract says something different from this page, the signed document wins.
02 What we collect
- Colleagues we work with: names, titles, work email and phone, mailing or billing addresses, buying references, signatures, workshop notes, ticket threads, chat in shared channels—everything you’d expect when onboarding a partner.
- Logs inside environments we manage for you: typical cloud diagnostics—timestamps, request paths we store, IP addresses, service identities—used to fix issues, stay secure, and right-size capacity. Only where our agreement covers that environment.
- People browsing this marketing site: basic device and browser signals plus rough location from IP to block abuse and understand traffic as a whole.
- Cookies: described in the next major section.
Some regions (including parts of Europe, the UK, and several U.S. states) add extra duties. Tell us where your teams sit and where data lives so any add-on privacy paperwork lines up with reality.
03 How we use data
We use what we collect for ordinary business reasons:
- Win and deliver work—discovery calls, prototypes, go-lives, fixes, and the tight window of support right after launch;
- Run hosting you already bought from us;
- Invoice, handle taxes, and keep books regulators expect;
- Guard our own systems from fraud or misuse;
- Respond to regulators or courts when the law requires it.
Where stricter privacy laws apply, we usually point to fulfilling the contract with your company or to balanced business needs that still respect individual rights. For truly optional activities—like a newsletter you didn’t have to join—we ask permission first.
06 Protecting your information
We protect data the way a services firm should: encrypted browsing for normal work, least-privilege access for staff and contractors, separation between client projects, backups when we’ve promised them, and vendor checks that match the risk.
No internet service is bulletproof. If something looks wrong involving CrownInternet.ai—or systems we run for you—reach us through the contact form and loop in your project lead. Heavy security questionnaires and on-site style reviews stay under NDA during sales, not on this public page.
07 Retention
Stale sales leads get removed from our CRM after a sensible quiet period. Live and finished project files—contracts, invoices, code, backups—usually stick around longer for accounting, warranties, disagreements, and tax rules, unless your deal sets an earlier cleanup we can actually execute.
Day-to-day logs normally expire on the schedule we publish for each environment (think weeks, not eternity). Backups rotate the way we wrote down for your setup.
08 Your choices
Depending on geography, your teammates may have rights to see, correct, download, limit, object to, or erase certain details. Most companies route those asks through purchasing or HR—we verify identity so one person’s curiosity doesn’t expose another’s inbox.
Deleting live data can trail a few days while overnight backups age out, unless rotating credentials already solves the risk.
Start with Contact below. You can still talk to a regulator on your own.
09 Data across borders
We work from different locations and lean on cloud vendors who may move or store data in several countries.
When regulators demand extra paperwork for those moves, the executed contract and privacy assessments carry the technical wording, not this overview. Your legal team can attach the right exhibit for the regions you pick.
10 Children
We deal with employers and their vendors. If you ship something aimed at kids, parental permission and youth safeguards are mainly your product responsibility—tell us early so contracts describe who does what.
11 Changes
If we materially change how we treat business visitors’ personal details, we refresh this page and its date, and email active customers when that’s practical.
12 Contact
Use the contact form with Privacy request in the subject. We usually answer standard questions within a couple of U.S. business days.