Skip to main content
Mon to Sun, 9 AM to 9 PM ET
Legal

Nine Documents.
Written To Be Read.

Each one does a job none of the others does. Each has a one-line summary, so you can find the right one without reading all nine.

No clause numbers you have to cross-reference. No paragraph that exists to make a bad term survive a skim. If a sentence in here only makes sense to a lawyer, it is written wrong and we want to hear about it.

Which one do I need?
The short version

Which one do you need?

Start from the question you actually have. Nine questions, nine documents, no cross-referencing.

None of those is your question?

Ask it directly and you get an answer in plain English, not a pointer to a clause number. That includes the parts of these documents that are not in your favor, and there are some. Ask a question.

The short version

Five things are true across all nine documents. If you read nothing else on this page, read these, then go straight to the one you need.

  • You own everything

    Your site, your domain, your ad accounts, your data, your content, in your name from day one. No proprietary platform you cannot leave, no exit fee, and nothing held back if you go. On full payment it transfers, and we hand over the access rather than waiting to be asked.

    Deliverables and IP

  • Month to month, no minimum term

    Care is cancellable on 30 days notice. Nothing auto-renews into a term, nothing rolls over into a second year because you missed a window, and canceling does not cost you the site. If we have to lock you in to keep you, we have already lost.

    Terms and Conditions

  • Every charge is agreed in writing first

    Prices are published on the site. Work beyond your care allowance is quoted and approved before it starts. Ad spend goes to the platforms directly from your own payment method and is never marked up. There is no charge on your statement you have not already said yes to.

    How billing works

  • We do not sell or share your data

    Not yours, and not your customers. Mobile opt-in data is never shared for marketing by anyone, us included. The tools we pass data through are named in the privacy policy rather than described as trusted partners.

    Privacy and Data Protection

  • We publish where our responsibility ends

    We configure the technical safeguards. You own the legal compliance. That line is written out framework by framework instead of left vague, because a correctly configured system is not the same thing as a compliant business, and finding that out afterwards is expensive.

    Compliance responsibilities

True of all nine, without exception

  • Written in plain English and laid out to be read on a phone, because that is where most people open them.
  • No clause numbers to cross-reference. Every section says what it means where you are standing.
  • The date each one last changed is published on this page, not buried at the bottom of the document.
  • A change that materially affects an existing client goes out with notice in advance. Nothing is quietly reposted.
  • The version in force when your estimate was signed governs your project, whatever we publish later.

If a term only makes sense once it is explained to you, it is written badly. Tell us and we will rewrite it.

The agreement

What we are doing for you, what it costs, what we commit to afterwards, and who owns the result. Three documents, and between them they are the whole commercial relationship.

Terms and Conditions

The governing document19 sections

Scope of work, fees and the payment schedule, refunds, late payment, timelines and delays, termination, confidentiality, liability and governing law. Where any two documents appear to disagree, this one wins.

Read it if you want to know what you are signing up for, when payments fall due, what happens if an invoice runs late, or how to end the arrangement.

Read it

Service Level Agreement

After launch10 sections

What we commit to once the site is live. 99.5% uptime with service credits applied automatically when we miss it, response windows by priority, scheduled maintenance, and what support covers on each care level.

Read it if you want to know how fast we respond, what happens during an outage, or exactly what your monthly buys.

Read it

Client Deliverables and IP

OwnershipTransfers on full payment

Who owns what, and when it changes hands. Your content and everything built specifically for you is yours on full payment. Our reusable frameworks stay ours and you get a perpetual license to them.

Read it if you want to know exactly what you take with you when you leave, or how third-party fonts, images and plugins are licensed on your site.

Read it

What is true across all three

  • The estimate is part of the agreement. Scope, price and the launch date are on the estimate you signed. These documents set the rules around it, they do not quietly change what you bought.
  • Nothing applies retroactively. The version in force when your estimate was signed governs that project, however many times we revise these pages afterwards.
  • The build fee and the monthly are separate. Canceling care does not undo the build, and it does not cost you the site, the domain or the accounts.
  • Every number in them is published. Build fees, care levels, the hourly rate beyond your allowance and the ad-spend percentage are all on the site, not quoted per client behind a login.

Order of precedence. Your signed estimate first, then the Terms and Conditions, then the Service Level Agreement, then everything else. We publish the order rather than leaving you to guess which document wins, because the moment it matters is the moment nobody wants to be arguing about it.

Your data

What we collect, where it came from, which tools it passes through by name, how long we keep it, and what we will never do with it.

Privacy and Data Protection

The main one13 sections

Everything we hold and why, split by who you are: a visitor, an inquiry, a client, or somebody we contacted first. Covers verification and enrichment, the full named tool list, retention periods, security, and the rights you can exercise in each region.

Read it if you want to know what we know about you, where we got it, or how to make us delete it.

Read it

Cookie and Tracking Policy

Named inventoryPer cookie

Every cookie on this site listed by its actual name, with what it does, how long it lasts, and which third party sets it. Google, Meta, LinkedIn, Mautic and HubSpot are named, with a link to each one policy, and there are instructions for switching the whole category off.

Read it if you want the detail rather than the four-category summary most sites publish.

Read it

SMS Terms

Text messagingReply STOP

Our text message program. How you opt in, what the opt-in language says word for word, how often we message, what it costs you, how to get help, and how to stop in one word.

Read it if you receive texts from us, or you are about to agree to. The commitment that matters: mobile opt-in data is never shared for marketing by anyone.

Read it

What we never do with it

  • Sell it. Not your data, not your customer data, not a list, not once. There is no line item in our revenue that comes from anyone data.
  • Share mobile numbers for marketing. Consent given to us stays with us. No affiliate, no partner, no third party gets a phone number collected on one of our forms.
  • Hold onto it because it might be useful. Every category has a stated retention period and is deleted at the end of it rather than archived indefinitely.
  • Describe our vendors as trusted partners. The tools that touch your data are named, individually, with a link to each privacy policy. You can go and read them.
  • Make you fight for a deletion. Ask and it happens, with confirmation in writing. No retention offer, no exit survey, no form that loops.

We play two roles, and they have different rules. On our own site we decide what is collected and why. On yours we process data on your instructions, and you are the one answerable for it. The privacy policy separates the two, and Compliance Responsibilities draws the same line framework by framework. If you are in healthcare, legal or finance, read that one before you read anything else.

Responsibility and standards

Three documents about conduct rather than commerce. What we are answerable for, what you are answerable for, and the standards we hold our own work to when nobody is checking.

Compliance Responsibilities

9 exclusions6 frameworks

Opens with what we refuse. We do not sign business associate agreements, so protected health information and eight other regulated categories never reach anything we build. What remains is split framework by framework: TCPA and messaging, CAN-SPAM, CASL, GDPR, US state privacy, PCI and state consumer health data laws.

Read it if you are in healthcare, legal or finance, if you send texts or email, or if you want to know why a correctly configured system is not the same thing as a compliant business. It also sets out what we can still build a regulated practice, which is most of it.

Read it

How We Email

For people who did not opt in8 sections

We send cold email, so this page exists for the people who receive it. Where we got your address, what we do and do not do with it, how much of it a machine wrote, what changes once you become a client, and how to end it in one word.

Read it if an email from us arrived that you never asked for. It is written for you rather than for us, and the unsubscribe is one click with no confirmation page.

Read it

Accessibility Statement

WCAG 2.2 AAIncluding what we missed

What we build to, which browsers and assistive technologies we test against, what we have not solved yet, and how to tell us when something here does not work for you. The unsolved list is published rather than quietly omitted.

Read it if you use assistive technology, or you want to know what WCAG 2.2 AA actually means for a site we build you rather than as a phrase in a proposal.

Read it

The division of labor, in one line each

  1. We configure the safeguards

    Ours to get right. Encryption in transit, consent banners wired to the tags they gate, form data going where it is supposed to, access controls, backups, and a stack that passes an audit on the technical points.

  2. You own the legal compliance

    Yours to get right. Whether you may lawfully hold the data at all, whether your consent language is adequate for your industry, and whether your claims are substantiated. Where a regulated system needs a business associate agreement, that sits between you and the vendor who signs one. It is never us.

  3. We tell you when we think you have a problem

    Ours to raise. If something you have asked for looks like it puts you on the wrong side of a rule, we say so before we build it. We are not your lawyer and we will tell you to get one.

A configured system is not a compliant business. We would rather say that here than after something goes wrong.

Things that moved

We used to publish twelve documents. Three of them were saying things the others already said, or were guides filed in the wrong place. Here is where each one went and why.

Retired legal pages and where their content now lives
Was Now Why
Payment Policies Terms and Conditions Four of its five sections already existed inside the Terms saying the same things. Two documents stating one policy is how they end up disagreeing.
SMS Compliance Guide Twilio campaign registration It was a how-to guide filed as a legal policy. The help center version covers the same ground and adds the actual steps, screen by screen.
Email Marketing and Anti-Spam Policy How we email It described how we operate rather than setting a legal obligation, so it reads better where people can find it. The compliance obligations it carried now live in Compliance Responsibilities.
Every old URL still resolves Each retired page carries a permanent 301 to its replacement. An old bookmark, an old email footer or an old PDF still lands somewhere useful rather than on a 404.
Nothing was quietly deleted Consolidating meant moving text, not dropping commitments. If a term applied to you before, it still applies, and it is in the document named above.

Twelve documents is not more protection than nine. It is three more chances for two pages to contradict each other on the same point, and the contradiction only ever gets found at the worst possible moment. If we can say something once, we say it once.

When each was last updated

Published in one place, because a legal page with no date on it tells you nothing about whether anyone has looked at it since 2019.

Each legal document, the date it last changed, and the version currently in force
Document Last updated Version
Terms and Conditions 1.0
Service Level Agreement 1.0
Client Deliverables and IP 1.0
Privacy and Data Protection 1.0
Cookie and Tracking Policy 1.0
SMS Terms 1.0
How We Email 1.0
Compliance Responsibilities 1.0
Accessibility Statement 1.0

Every document here is at its first version. None of them has been revised since it was published, and the day that stops being true this table is where you will see it, on the same page rather than in a changelog nobody links to. Six of the nine take their effective date the day counsel signs them off, and until that happens this page says so rather than showing a date nobody stands behind.

What happens when one of them changes

  • You hear about it first

    Where a change materially affects an existing client, notice goes out in advance. It is not reposted quietly with a new date at the top and left for you to notice.

  • Your version is frozen

    The version in force when your estimate was signed governs that project. Nothing we publish afterwards reaches back and changes what you already agreed to.

  • Old versions are kept

    Ask for the version that applied on a given date and we will send it. That is the entire point of publishing a version number instead of just a date.

Ask us anything in them

These documents are written to be read, not to be impressive. If a section is unclear, that is a fault in the writing and we would like to know about it.

  • What does this clause mean?

    You get the answer in plain English, including the parts that are not in your favor. There are some, and pointing you at clause 14.3 is not an answer.

  • What do you hold about me?

    Ask and we will tell you, whether you are a client, an inquiry or somebody we emailed first. Ask us to delete it and we do, with confirmation in writing.

  • This paragraph is badly written

    Genuinely the most useful message we can get about this page. Tell us which sentence lost you and we will rewrite it rather than defend it.

Call and ask +1-248-205-6977
Put it in writing [email protected]
Ask a Question
Help Center

Black Tiger Digital · Waterford, Michigan · Mon to Sun, 9am to 9pm ET

  • You own everything
  • Month to month, no minimum term
  • Every charge agreed in writing first
CallBook a Free Call