Acceptable Use Policy

In short

• Use Tillyard yourself, through an ordinary browser, at the speed of a person.
• No bots, scripts or AI agents acting for you. Assistive technology is always welcome.
• One account each. Do not share, lend, sell, buy or borrow an account.
• Do not scrape, crawl or copy in bulk. Signed-in areas are closed to every crawler. On public pages, only search engines may crawl, and they must follow our robots file and the tags on each page.
• Do not harvest members' information, and do not use public pages to build profiles or lists of people.
• Do not use members' work or words to train or test AI models.
• Do not probe, bypass or pick apart our safeguards. If you find a security problem, tell us.
• Everything has a limit. Do not try to get round limits or weigh the service down.
• When daily capacity runs short, features pause in a set order. A pause is not a penalty and says nothing about you.
• If this policy is broken we may slow, block or end access, and withdraw anything gained by the abuse.

If this summary and the full text below ever differ, the full text governs.

1 About this policy

1.1 What it covers

This policy covers every technical way of reaching or using the service, which means the website at tillyard.org and everything behind it: its pages and forms, its live connections, the interfaces its own pages use, its public pages, the emails it sends, and the calendar files, feeds and site maps it publishes.

1.2 Who it applies to

It applies to everyone:

• members;
• visitors who are not signed in;
• people who use a public form or a confirmation link, such as an outside confirmer, a person asking for a removal or a correction, or a person sending an inquiry;
• companies, colleges, researchers and other organizations;
• any software or service acting for any of them, including crawlers, bots and AI agents.

If you use the service on behalf of an organization, this policy applies to the organization too.

1.3 How this policy fits with our other documents

• The Terms of Use are the contract. This policy is part of it.
• The Community Guidelines govern conduct toward people: harassment, honesty, spam, gaming of records. Where a matter is about how you treat people, they govern. Where it is about how you use the machinery, this policy governs.
• The Messaging and Monitoring Notice and the Privacy Notice say what we log and why.
• The Security and Vulnerability Disclosure Policy sets out how to report a vulnerability and what good-faith research is permitted. On that subject it governs.
• The Copyright Policy and each paper's license govern reuse of published work.

Where two documents cover the same point, the more specific one governs. Section 37.5 of the Terms of Use sets the order among all our documents, including the sections of those terms that prevail over every other document.

1.4 Words we use

Words that have one meaning in every one of our documents, such as member, visitor, staff, the editor, record item, hold, case and tip, are defined in Definitions. The words below are added for this document's own subject, or repeated from Definitions for convenience. If a repeated meaning ever differs, Definitions governs the meaning of the word.

• We, us and our mean Tillyard, which operates the service.
• A member is a person who holds an account.
• Member content means anything a member wrote, made or set on the service: papers, readings, entries, profile text, Record items, messages, answers, order lines and so on.
• Member information means anything that identifies or describes a member: name, school, email address, profile details, Record, connections, and when or where they were present on the service.
• Public pages means pages that can be opened without signing in: published papers, a Record page opened by its link or code, a public profile its owner has switched on, the directory search where it is open to visitors, the policy pages and the signed-out front pages.
• Signed-in areas means everything else.
• Automated means means any software that acts on the service without a person choosing each action at the time: bots, scripts, macros, crawlers, scrapers, headless browsers, browser extensions that click or type, and AI agents.
• Crawler means automated means that fetch pages in order to index, copy or analyze them.
• Safeguards means the technical measures that protect the service and its members: sign-in and session controls, human-check challenges, rate limits and budgets, signed tickets and tokens, the word list and classifiers, blocks, the blind-reading draw, anonymization, and the page headers and tags that tell software what it may do.
• Limits means the ceilings on size, count and speed described in section 9.
• Capacity pause means a feature being slowed or switched off for a time because a daily ceiling on what the service can do has been reached or is near.

2 What you are welcome to do

So that nothing below is misread, all of this is fine:

• using the service through an ordinary, up-to-date web browser, on any device;
• using assistive technology of any kind: screen readers, magnifiers, voice control, switch devices, dictation, reading modes, your own style sheets, browser zoom and translation;
• using a password manager, your device's passkey features, and your browser's own autofill, spell-check and print-to-PDF;
• subscribing to the calendar files we publish, such as the shop's hours, in your own calendar;
• linking to any public page;
• reading published papers, and quoting them with attribution within the license shown on the paper;
• checking a Record item that someone gave you, by its link, its QR code or its code;
• exporting your own data;
• viewing the source of pages in your browser to see how they work;
• telling us about a security problem you found (section 8.6).

3 Your account

3.1 One person, one account

Each member is one real person with one account. Do not:

• open more than one account;
• open an account for someone else, for a club, a company or a team, or for a character;
• open accounts in bulk, or by automated means.

3.2 No sharing, lending, selling or borrowing

Do not:

• let anyone else use your account, or use anyone else's;
• sell, rent, give away, buy or trade an account, a founding number, a title, a Record item or a place in a line;
• join with a college email address that is not yours;
• keep an account alive through an address you were never entitled to.

3.3 Help with access

A person who helps you use your device because of a disability, such as a personal assistant, a reader or a support worker, is not "someone else using your account" when they act at your direction and in your presence. You remain responsible for what is done on your account.

3.4 Eligibility checks

Sign-up asks for an eligible college email address, a date of birth, a status and a statement that you are 18 or older. Do not get round any of these: no false answers, no repeated attempts with different answers, no second address after a refusal, and no route around a school that is not yet open.

3.5 Keeping your account secure

• Keep your devices and passkeys under your own control.
• A sign-in code or setup code is for you alone. Nobody from Tillyard will ever ask for it.
• Sign out on shared computers.
• Tell us at security@tillyard.org if you think someone else has got into your account.

You are responsible for what is done through your account, except where someone got in through no fault of yours and you told us promptly once you knew.

3.6 After a restriction, suspension or removal

Do not get round a decision about your account by opening another one, borrowing one, or having someone else act for you. The Community Guidelines (section 7.11) say what can follow.

3.7 The staff console

The staff console is for staff. Do not try to reach it, guess its address, or obtain or use staff credentials.

4 Automation

4.1 Use the service yourself

Use the service yourself. A person must choose each action at the time it is taken. Do not use automated means to sign up, sign in, read, click, type, send, tick, nod, score, confirm, report, reserve, refresh or stay connected.

4.2 What this rules out

• bots and scripts of any kind, including "user scripts" and bookmarklets that act on the page;
• macros, auto-clickers and key repeaters;
• browser extensions that click, type, tick, refresh or send for you;
• headless or remotely driven browsers;
• tools that keep a tab or a connection alive, or that reconnect you automatically beyond what our own pages do;
• tools that watch the shop's sign, a line or a pool and act the moment something opens;
• anything that sends requests to the service other than through its own pages (section 4.5).

4.3 What it does not rule out

• Assistive technology, including technology that operates the page for you by voice, switch or eye movement.
• Ordinary browser features and extensions that change how a page looks to you, read it aloud, translate it or block trackers.
• Password and passkey managers.
• Dictation, spell-check and grammar help while you write. If an extension does this by sending what is on your screen to another company, remember that the screen may show other members' words (section 7.2).

4.4 AI assistants and agents

• Do not let an AI agent or a "browsing" assistant operate your account: no signing in for you, reading pages for you, or acting in the shop, in Notes, in threads or in any form on your behalf.
• Do not have an AI tool hold a conversation for you. People here expect to be talking to a person, and the Community Guidelines say the same.
• Using an AI tool to help with your own writing is a separate question, governed by the Community Guidelines and the rules of Tillyard Research. It must be declared where a form asks.

4.5 Other clients and our internal interfaces

• The service is offered through its own web pages. We publish no programming interface for members. The only one is a payments interface for sponsor accounts, which stays closed until we can accept gifts.
• The addresses our pages call in the background, and the live connections they open, are for those pages alone. Do not call them directly, build your own client, app, bot or integration on them, or publish instructions for doing so.
• Do not replay, alter or forge the requests our pages make.

4.6 Automation and things that are counted

Visits, pots, attendance, readings and similar counts are meant to record what a person did. A count produced by an idle tab, a script or any other automated means is false, and the Community Guidelines (section 3.12) treat it as gaming. Such counts may be withdrawn.

5 Scraping, crawling and bulk copying

5.1 Signed-in areas

Signed-in areas are closed to all automated collection. Do not scrape, crawl, index, mirror, record or export anything from them, by any means, whether or not you are a member. Your own data export is the proper way to take your own information away.

5.2 Public pages

Public pages exist so that a person can read a paper or check a record. Do not collect them in bulk, by automated means or by hand.

Automated fetching of public pages is allowed in two cases only:

• a general web search engine indexing the pages that our robots file and page tags allow (section 5.4);
• a service fetching a single page in order to show a preview of it, because a person shared that page's link there.

Every other kind of crawling, including by archives, research crawlers, data collectors and AI crawlers, needs our written permission first (section 5.7).

5.3 Rules for every crawler

A crawler that falls within one of those two cases may fetch public pages only if it does all of the following:

• Obeys our robots file at tillyard.org/robots.txt, including any rules that name it or its kind and any delay the file sets. A page or path the file disallows must not be fetched. Fetching beyond what the robots file allows is a breach of this policy.
• Obeys page-level signals: the "noindex" and similar tags and headers on a page, and the difference between a page that answers normally, one that says it is no longer listed and one that says it has been withdrawn.
• Uses the site map we publish as the list of pages offered for indexing, and does not go looking for others.
• Identifies itself honestly in its user-agent string, with a way to contact its operator, and does not pretend to be a browser or a different crawler.
• Goes slowly, stays well within what an ordinary reader would request, and stops when asked or when it meets a refusal.
• Does not evade. No rotating addresses, proxies, spoofed headers, stealth browsers, solved or farmed human checks, or signed-in sessions.

5.4 Search engines

A general web search engine may index public pages that the robots file and page tags allow, and may show a link and a short extract in its results. It must drop a page and any stored copy when the page stops being offered, for example when a member turns off search visibility, when an item is withdrawn or when a page reads as no longer listed.

Being findable in search is each member's own choice, off until they turn it on. Do not index, list or link in bulk any page whose owner has not made that choice.

5.5 The directory and record lookups

• The directory is for finding a person you have a reason to find. Do not run systematic searches through it, such as working through the alphabet, through schools or through interests, and do not record the results.
• A Record page is opened by a link or a code that its owner gave to someone. Do not guess, generate or cycle through links or codes.
• Do not use the human check or the short-lived search pass more often than a person searching for someone would.

5.6 Copies, archives and mirrors

• Do not republish, mirror or frame the service or any substantial part of it.
• Do not keep or publish copies of members' pages in a way that would outlast their removal. A member can withdraw, unlist or delete, and a copy made by you should not defeat that.
• A published paper may be shared and quoted as its license allows. That license comes from the author, and this policy does not widen it.

5.7 Permission

We do not grant permission to scrape or crawl beyond sections 5.2 to 5.4 through this policy, through the robots file or by silence. If you believe you have a good reason, write to legal@tillyard.org first. Any permission is given in writing, for a stated purpose, and can be withdrawn.

6 Member information

6.1 No harvesting

Do not collect members' names, schools, email addresses, profile details, Record items, connections, messages or anything else about them, by automated means or by hand, beyond what you need for the ordinary use you are making of the service at that moment.

6.2 No profiles, lists or dossiers

Do not use the service, including its public pages, to:

• build or add to a database, a list or a profile of members or of students;
• supply a people-search site, a lead list, a recruiting database, a marketing list or a data broker;
• combine what is here with information from elsewhere in order to identify, locate, monitor or contact a person;
• produce a report on a person's character, reputation or suitability for anything;
• sell, rent, share or publish any such collection.

6.3 Checking a record is fine

Opening the Record page a candidate, applicant or acquaintance gave you, and reading what it says, is exactly what those pages are for. What section 6.2 rules out is going beyond that: collecting many people's pages, keeping files on people, or treating our pages as a background check. Record pages say what a member did and who confirmed it. They are not consumer reports, and Tillyard is not a background-screening company.

6.4 No watching when people are here

Who is in the shop, where they are sitting, the rings they left and their usual evenings are shown to members only, and only where the member chose to show them. Do not record, log or compile any of it, and do not use it to work out a person's routine.

6.5 No unsolicited contact

Do not use information found here to contact members by email, on other platforms, by phone, by post or in person when they have not invited that. This applies to messages sent one at a time as much as to bulk mail.

6.6 No unmasking

Do not use technical means, such as comparing writing style, timing or metadata, to work out:

• who wrote a paper or an entry you were given blind;
• who read or scored your work;
• whose résumé you were sent in a swap;
• who reported you, or who blocked you.

6.7 People who are not members

The same rules protect outside confirmers and anyone else named on the service.

7 Machine learning and AI

7.1 No training or testing on member content

Do not use member content or member information from the service, whether from public pages or signed-in areas, to:

• train, fine-tune, test or evaluate any machine-learning or AI model;
• build a dataset, a search index, an embedding store or a knowledge base for such a model;
• supply a product that generates text, answers questions or scores people.

Members own what they write here. We have no right to give this permission on their behalf, and we do not give it. Our robots file tells AI crawlers the same.

7.2 Other members' content and AI tools

Do not put another member's unpublished or non-public content into an AI tool or any other outside service. That includes a paper or entry you were given to read, a résumé from a swap, and messages from Notes, threads or tables. Many such tools keep what they are given, and it was not yours to hand over.

7.3 Your own content

What you made is yours. This section does not limit what you do with your own work. Where you used AI help on something you submit here, the Community Guidelines say how to declare it.

7.4 What Tillyard does

We do not use member content to train AI models, and we do not provide it to anyone else for that purpose. Automated safety screening, described in the Messaging and Monitoring Notice, scores a piece of text and is not training.

8 Security

8.1 Do not attack or probe

Do not:

• test, scan or probe the service or its hosting for weaknesses, except as section 8.6 allows;
• get round, switch off or interfere with sign-in, sessions, human checks, rate limits, blocks, page security headers or any other safeguard;
• reach, or try to reach, data, pages or functions that were not meant for you, including by changing an identifier in an address or a request to one that belongs to someone else;
• take over or use another person's session or account;
• try codes, links, ticket numbers or addresses in bulk to find ones that work;
• intercept or tamper with anyone else's connection to the service;
• flood, overload or otherwise try to make the service unavailable.

8.2 Tickets, tokens and codes

The service uses short-lived signed tickets, tokens, one-time codes and a short-lived search pass. Do not forge, alter, replay, share or stockpile any of them, and do not use one outside the purpose and the person it was issued for.

8.3 Evading screening

• Do not disguise text to get it through the word list or the classifiers: no spacing tricks, look-alike letters, invisible characters or encoding.
• Do not probe the screening to map what it stops.
• Do not split or encode content to get round a size cap or a restriction on links and contact details.

8.4 Harmful code and content

• Do not submit or link to malware, exploits, or pages that try to capture sign-in details.
• Do not try to inject scripts, markup or styling into any field. The service treats what members write as text only; do not try to make it do otherwise.
• Do not craft a file to attack the in-browser résumé reader.

8.5 Deception

• Do not try to trick staff or members into giving up a code, approving a passkey request or granting access.
• Do not send email or build pages that pretend to come from us.

8.6 Good-faith security research

We want to hear about security problems. Research carried out within the Security and Vulnerability Disclosure Policy is not a breach of this policy. In outline, that means:

• testing only against your own account and your own data;
• stopping as soon as you have confirmed a problem, and not using it to read, change or remove anyone else's information;
• no flooding, no social engineering, and nothing that degrades the service for others;
• telling us promptly and privately at security@tillyard.org, and giving us reasonable time before telling anyone else.

The Security and Vulnerability Disclosure Policy has the full terms and governs. Our security contact file is at tillyard.org/.well-known/security.txt.

8.7 If you come across something by accident

If you see data or a function that clearly was not meant for you, stop, do not copy or share it, and tell us at security@tillyard.org. Reporting an accident honestly is not held against you.

9 Limits, load and capacity

9.1 Everything has a ceiling

To keep the service safe and affordable, every input and every action has a limit:

• how long a piece of text can be, and how large a request;
• how many items a list can hold, and how many rows a page shows;
• how many messages, saves, searches, nods, reports, invitations, favors, submissions and tables you can make in a minute or a day;
• how many live connections you can hold: one in a shop room and one for notices, so a second tab replaces the first;
• how often a page may reconnect;
• how many times a sign-in code or a confirmation code can be sent to one address.

Each member also has an overall daily allowance of writes. Limits are shown where they apply ("three nods a day"). The exact thresholds behind some anti-abuse measures are not published, and any limit may change.

9.2 New accounts

For its first days, a new account has lower limits and cannot send links or contact details. This is the same for everyone and is not a judgment about you.

9.3 Do not get round limits

Do not use extra accounts, sessions, devices, networks or timing tricks to exceed a limit, and do not split one action into many to stay under one.

9.4 Do not weigh the service down

Do not:

• send requests faster or more often than a person using the pages would;
• reload, reconnect or re-search in a loop, by hand or otherwise;
• submit deliberately huge, malformed or costly input;
• hold connections open that you are not using;
• do anything whose purpose is to use up the service's daily capacity.

If you see a message saying you are going too fast, wait and try again later. Trying again at once makes it last longer.

9.5 Email and forms

• Do not cause the service to send email to an address that is not yours, or to send repeated email to any address.
• Do not use confirmation links to make the service email people who have nothing to do with your record.
• Do not send junk, tests or repeated submissions through the report, removal, dispute or inquiry forms, and do not file reports in bulk. Those forms have to stay clear for people who need them, including people with a legal deadline attached to their request.

9.6 Tip links

Tips are paid on pages run by Stripe. Do not use them to test card numbers, to make payments with a card that is not yours, or to move money for any purpose other than leaving a tip. The Tips and Larger Payments Terms govern tips.

9.7 Capacity pauses

The service runs within fixed daily ceilings: on requests, on database writes, on live connections, on email and on safety screening. The ceilings exist so that a spike, an attack or a mistake cannot run up a bill the company cannot pay or take the service down without warning.

When a ceiling comes near, the service sheds load in a set order:

1. drafts save to Tillyard less often;
2. optional background work stops;
3. new sign-ups are placed on a waiting list;
4. chat is switched off;
5. publishing is paused.

Throughout, we aim to keep enough in reserve for signing in, for reporting, for the removal form and for moderation. We cannot promise that those will always be available.

Email has a daily ceiling of its own, and it is the one most easily reached. When it is reached, emails may be delayed or not sent, including sign-in codes.

What this means for you:

• You may see a notice that a feature is resting, or that your text is being kept on your device until saving resumes.
• Most pauses lift when the daily count resets at midnight UTC.
• A capacity pause is not a penalty. It applies to everyone and says nothing about your account.
• Do not try to work round a pause.

9.8 Switches and maintenance

Staff can switch any feature off, or put the whole service into a read-only or maintenance state, at any time and without notice, for safety, for security, for cost or for repair.

9.9 What we do not promise

The service is provided as the Terms of Use describe. We do not promise that it, or any feature, will be available at any particular time, that a limit will stay where it is, or that a pause will end by a particular hour.

10 Text, links and files

10.1 Text, figures and receipts

The service accepts text. The only pictures it accepts are figures in a paper for Tillyard Research and receipts for a research grant, and it accepts no other files, audio or video anywhere. Do not try to bring them in another way, for example as encoded data in a text field.

10.2 Links

Links in member text are shown as text and are not clickable. Do not:

• disguise where a link leads, or use shorteners, redirects or tracking links;
• post links to malware, to pages that capture sign-in details, or to content the Community Guidelines would not allow in words;
• use spelling or spacing tricks to post a link or contact details when your account is not yet able to.

10.3 Tracking other people

Do not use links, addresses or any other device to learn whether, when or where another member opened something you sent.

10.4 Résumé import

The résumé import reads your file inside your own browser, and the file is never sent to us. Only the text you then choose to save reaches the service, where it is treated like any other text.

10.5 Evidence links

When you give a link as evidence for a Record item, do not arrange for it to show one thing to the reader and another later, or to show different things to different visitors. The Community Guidelines (section 3.8) cover honest evidence.

10.6 Call links

Where the outside-call feature is switched on, a call link must point to a call on one of the services the feature accepts, in the form it accepts. Do not try to pass any other address through it.

10.7 Our emails, calendar files and feeds

• Do not forge, alter or re-send our emails as if they came from us.
• The unsubscribe link in an email is for the person it was sent to.
• Calendar files and feeds are for personal use in a calendar or a reader. Section 5 applies to anything beyond that.

11 Our safeguards and our name

11.1 Do not pick the safeguards apart

Do not reverse engineer or decompile the service. In particular, do not work out the inner workings of any safeguard in order to defeat it, weaken it or help anyone else do so. That includes the human check, signed tickets and tokens, rate limiting, the word list and classifier settings, the blind-reading draw, anonymization in the résumé swap, and the codes on Record pages.

This section does not take away any right the law gives you that cannot be waived by agreement, and section 11.2 says what is clearly fine.

11.2 What is fine

• Reading the page source your browser receives, to learn how pages are built.
• Using the open-source components the service is built from, under their own licenses.
• Research within the Security and Vulnerability Disclosure Policy (section 8.6).

11.3 Do not interfere with how pages appear or what they say

• Do not frame or embed the service in another site, or overlay it, so as to mislead anyone about what they are looking at.
• Do not remove or hide the notices on a Record page or a paper, such as the "what this page does and does not say" section, when showing it to someone.
• Do not present an altered copy of a page, an export or a QR code as the real thing.

11.4 Lookalikes

Do not register or use a web address, an account on another platform, an app or a page that imitates the service or its record pages, or that uses our name or wordmark in a way likely to confuse people about who is behind it. The Trademark and Brand Use Policy says what use of our name is allowed.

12 Commercial and organizational use

12.1 Personal use

A member's account is for that member's own study, work and record. Visitors may read public pages and check records for their own purposes, including an employer's ordinary reading of a candidate's record.

12.2 No resale or brokering

Do not:

• sell or resell access to the service or to anything on it;
• offer, for payment or otherwise, to operate accounts, to raise counts, to obtain confirmations or to "improve" a Record;
• run the service for other people as a service of your own;
• place advertising on, around or through the service.

12.3 No copying to compete

Do not copy the service's content, structure or member data, or measure the service by automated means, in order to build or improve a competing product or dataset.

12.4 Research about the service

If you want to study the service or its members, for a class, a thesis or a publication, write to legal@tillyard.org before you begin. Approval from an ethics board at your institution does not by itself give you permission to collect anything here, and sections 5 to 7 apply to researchers as to everyone else. Research that uses only your own data, or published papers within their licenses, needs no permission from us.

12.5 Permissions are in writing

Any exception to this policy for an organization, such as a data arrangement, an integration or a study, is given in writing by the company, for a stated purpose, and nothing is implied by a conversation, a sponsorship or a tip.

13 How this policy is enforced

13.1 How we notice

Mostly through counters and patterns: how fast requests arrive, how many fail, what is repeated, and what trips a limit. The Messaging and Monitoring Notice and the Privacy Notice describe what is logged. We also act on reports.

13.2 What happens automatically

Software applies the limits in section 9 without a person being involved. It may:

• refuse a request, or ask you to wait;
• show a human check;
• close a live connection, and keep it closed for the rest of an evening after repeated violations;
• block requests from an address, a network or a kind of software;
• hold an item for a person to look at;
• pause an account while something is checked;
• pause a feature for everyone (section 9.7).

These are technical measures and not findings against you.

13.3 What a person decides

A person, not software, decides every notice, 24-hour mute, suspension and removal for conduct. Software may hold an item, stop your table chat for one visit, or pause an account while a person looks, including a pause of up to 24 hours when activity looks like abuse; that pause ends by itself unless a person extends it, and it is not a finding. One closure happens by rule: an age re-check answered "under 18" or "high-school student", or left unanswered. The Community Guidelines (section 7) describe how those decisions are made.

13.4 What we may do

Depending on what happened, we may:

• slow, limit or block access for an account, a session, a device, an address, a network or a crawler;
• end sessions and require you to sign in again;
• withdraw counts, perks, Record items or titles obtained through abuse;
• restrict features, or suspend or remove an account, and refuse a new one;
• remove or hide content;
• ask the operator of a crawler or a service to stop, and ask others who received improperly collected data to delete it;
• tell members whose information was affected;
• preserve evidence;
• take legal action, and refer a matter to law enforcement where appropriate and lawful.

13.5 Who is responsible

You are responsible for what is done through your account and by any software or person acting for you. An organization is responsible for what its staff, contractors and tools do. "A tool did it" is not an answer.

13.6 Our other rights

This policy does not limit any other right or remedy we have under the Terms of Use or the law. If we do not act on one occasion, we have not approved the conduct or given up the right to act later.

13.7 Asking us to look again

If an automatic measure seems wrong, for example because you share a network with many other people, write to support@tillyard.org and we may adjust it. For a decision about your account, the appeal in the Reporting, Enforcement and Appeals Policy applies.

13.8 What we do not promise

We do not promise to detect or stop every misuse of the service, to act on every report, or to act within any set time. We do what a very small company reasonably can.

14 Telling us about misuse

• A security problem: security@tillyard.org, under the Security and Vulnerability Disclosure Policy.
• Scraping, a copied page or a lookalike site: legal@tillyard.org, with the address and what you saw.
• A member using automation or more than one account: the report control on that member, or the public report form.
• If you operate a crawler and want to know what is allowed, read the robots file first, then write to legal@tillyard.org.

15 Changes to this document

• We may change this policy as the service, the threats to it and the law change.
• Each version carries a number and an effective date at the top, and earlier versions are kept available.
• For a change that matters, such as a new prohibition or a new consequence, we aim to tell members on the site before it takes effect. Changes needed urgently for security or to stop abuse, and small clarifications, may take effect when posted.
• Limits and capacity ceilings are operating settings, not terms of this policy, and may change at any time without notice.
• A change applies to conduct after it takes effect.

16 Contact

• Questions about this policy: support@tillyard.org.
• Permissions, legal notices and crawler operators: legal@tillyard.org, or by post to Tillyard, 10602 York Rd SW, Etna, Ohio 43062.
• Security: security@tillyard.org.
• Accessibility, including any difficulty with a human check or a limit: accessibility@tillyard.org.

Questions about this document

support@tillyard.org

Legal notices

legal@tillyard.org

By post

10602 York Rd SW, Etna, Ohio 43062

For anything else, see where to send what.

Fingerprint of this text (SHA-256): 664f689b2b91db7c6cde73a6f3bf26e1165d193a19fced2cf0dcfd4dc96d3d4b