Contents — 14 sections
- Scope and definitions
- 1. Designated contact for copyright notices
- 2. What Ingy is, and what it does with third-party material
- 3. Users are responsible for their sources and their publishing
- 4. What a valid notice must contain
- 5. What we do when we receive a notice
- 6. Counter-notice: if you are a user and we acted against you
- 7. Repeat infringers
- 8. Machine-readable rights reservations, and publishers who do not want us fetching
- 9. False and abusive notices
- 10. Other kinds of complaint
- 11. Changes to this policy
- 12. Governing law
- Contact
Scope and definitions
In this policy, "we", "us" and "our" mean IX Labs. "You" and "your" mean the person using our product. "Rights holder" means a person or organisation claiming rights in a work.
Our product is Ingy, a Telegram bot that drafts social media posts from a link, a video, or plain instructions. Our website is ingy.app and the bot is @IngyAppBot.
This policy stands on its own. You do not need to read any other document to send us a notice or to understand how we handle one.
1. Designated contact for copyright notices
1.1 Send all copyright complaints, takedown notices and counter-notices to:
Email: [email protected] (fastest, and preferred)
Post:
Legal — Copyright Notices
IX Labs
27 Old Gloucester Street
London
WC1N 3AX
United Kingdom
1.2 Please put "Copyright Notice" or "Counter-Notice" in the subject line.
1.3 We are a UK company and this policy sets out a UK and EU notice-and-takedown procedure. We are not established in the United States and we do not maintain a designated agent under the US Digital Millennium Copyright Act. We nevertheless accept notices concerning claims under US law at the same address above, and will deal with them under the procedure in this policy.
2. What Ingy is, and what it does with third-party material
This section matters, because it determines what we are actually able to take down.
2.1 Ingy is a Telegram bot. Everything happens inside a private Telegram conversation between the user and the bot. A user's account is their Telegram account.
2.2 A user can give Ingy an article URL, a video link (for example YouTube, TikTok, Instagram or X), an uploaded video file, or plain written instructions with no source at all.
2.3 Ingy fetches articles and transcribes video and voice at the user's direction, for the purpose of producing a draft for that individual user. Fetching happens because a user asked for it, at the moment they asked, and for that request.
2.4 We do not host a public library of third-party content. There is no public archive, no searchable index of fetched articles, and no public page displaying fetched material.
2.5 The output is one plain-text draft message, delivered privately to the user who requested it. It is not published by us, it is not listed anywhere, and it is not visible to other users.
2.6 Publishing is manual. Ingy never posts to any channel. If anything reaches the public, it is because the user copied the text and pasted it somewhere themselves.
2.7 As a result, if content you are complaining about is live on a Telegram channel, a website or a social platform, we cannot remove it from there. We do not control those places. We can act on what is inside our own service — see section 5 — and you will usually also need to contact the platform where the content is published.
3. Users are responsible for their sources and their publishing
3.1 Every Ingy user is responsible for having the right to submit the sources they give us.
3.2 Users are told, in our acceptable use rules, that they must not submit paywalled or access-restricted content, content behind a login, content whose site terms forbid automated access, content covered by a machine-readable reservation of rights against text and data mining, or anything that infringes another person's rights.
3.3 Users are responsible for reviewing any draft and for anything they choose to publish, including whether their use of a source is lawful in their jurisdiction.
3.4 Nothing in this policy makes us the author, editor or publisher of what a user posts.
4. What a valid notice must contain
4.1 To let us act quickly, your notice must include all of the following:
4.1.1 The work. Clear identification of the copyright work or works you say have been infringed — title, author or rights holder, date, and where the original can be seen (a URL is ideal). If you are complaining about many works, a representative list is acceptable.
4.1.2 Your rights. A statement of your relationship to the work: are you the rights holder, an exclusive licensee, or an authorised agent? If you are an agent, say who you act for.
4.1.3 What you are complaining about, and where. Identify the specific material at issue and where you encountered it precisely enough for us to find it — for example the Telegram username or channel involved, the URL of a published post, the date and time you saw it, the source URL you believe was fetched, and, if you have it, the text in question. A notice we cannot locate the material from is a notice we cannot act on.
4.1.4 Your contact details. Full name, organisation if any, postal address, email address and telephone number.
4.1.5 Good faith statement. A statement that you believe in good faith that the use complained of is not authorised by you, your agent, or the law (including any applicable exception such as quotation, news reporting, criticism or review, or fair dealing).
4.1.6 Accuracy statement. A statement that the information in the notice is accurate, and that you are the rights holder or are authorised to act on their behalf.
4.1.7 Signature. Your signature. A typed full name in an email from your own address is sufficient as an electronic signature.
4.2 Please send the notice in English.
4.3 If your notice is incomplete, we will tell you what is missing. Our time limits in section 5 start when we receive a complete notice.
5. What we do when we receive a notice
5.1 Acknowledge. We aim to acknowledge a complete notice within 5 working days of receipt.
5.2 Review. We assess whether the notice is valid and complete, whether the material is within our control, and whether the complaint appears well-founded on its face. We are not a court and we do not decide who owns what; we take a reasonable view on the information in front of us.
5.3 Act, where appropriate. Where we consider it appropriate, we may:
- remove or disable the material within our service;
- delete the stored draft, versions and any cached or transcribed source material relating to the complaint;
- block future fetching from a specified domain or URL;
- restrict, suspend or terminate the account of the user involved; and
- decline to act, if we consider the notice invalid, mistaken, abusive, or aimed at material we do not control.
5.4 Notify the user. Where we act on a notice, we will normally tell the affected user what we have done and why, and pass on the substance of the notice, so that they can respond. We may pass on your notice, including your identity and contact details, to that user, unless we are prevented from doing so by law or believe it would create a real risk of harm. If you do not want your details shared, say so in your notice and we will consider it — but we may then be unable to act, because a user cannot answer a complaint they cannot see.
5.5 Records. We keep a record of notices, our decisions and the action taken.
5.6 Deadlines. The timescales in this policy are targets, not contractual commitments. We act expeditiously where the complaint is clear and serious.
6. Counter-notice: if you are a user and we acted against you
6.1 If we removed or disabled material of yours, or restricted your account, and you believe that was a mistake or that your use was lawful, you can send a counter-notice to [email protected].
6.2 A counter-notice must contain all of the following:
6.2.1 Identification of the material that was removed or disabled, and where it was before removal.
6.2.2 Your full name, postal address, email address and telephone number.
6.2.3 A statement explaining why you believe the material was removed or disabled as a result of a mistake, a misidentification, or a use that is permitted — for example because you own the rights, you are licensed, the source was openly available and permitted for your use, or an exception such as quotation, criticism, review or news reporting applies.
6.2.4 A statement that the information in your counter-notice is accurate.
6.2.5 A statement that you consent to us passing your counter-notice, including your contact details, to the person who complained.
6.2.6 Your signature. A typed full name in an email from the address on your account is sufficient.
6.3 On receiving a valid counter-notice we will:
- acknowledge it;
- pass it, including your contact details, to the complainant; and
- decide whether to restore the material or the account access.
6.4 We are not obliged to restore anything. We may keep material disabled where we consider the complaint well-founded, where the dispute is unresolved, where restoring it would expose us to legal risk, or where the material also breaches our acceptable use rules for a separate reason.
6.5 A copyright dispute between a rights holder and a user is between them. We are not the referee. If the two of you resolve it, tell us in writing and we will act on that.
6.6 Do not send a counter-notice you know to be false. See section 9.
7. Repeat infringers
7.1 We terminate the accounts of repeat infringers.
7.2 We treat a user as a repeat infringer where, in our reasonable judgement, they have been the subject of more than one well-founded copyright complaint, or have persisted after being warned.
7.3 In deciding, we consider the number and seriousness of complaints, whether the user was warned, whether any counter-notice was credible, and whether the conduct looks deliberate.
7.4 No refund is available on termination for repeat infringement.
7.5 We may also terminate on a single notice where the infringement is serious, deliberate, or part of a commercial operation.
7.6 Creating a new account to get around a termination is itself a breach and that account will also be closed.
8. Machine-readable rights reservations, and publishers who do not want us fetching
8.1 We respect machine-readable reservations of rights against text and data mining. This includes reservations of the kind contemplated by Article 4 of EU Directive 2019/790 (the Copyright in the Digital Single Market Directive), and equivalent declarations however expressed.
8.2 We respect robots.txt directives and comparable machine-readable signals, including Content Signals and similar declarations placed by publishers to state how their content may be used.
8.3 We instruct our users not to submit sources that are paywalled, behind a login, restricted by site terms against automated access, or covered by such a reservation.
8.4 Fetching by Ingy happens at the direction of an individual user, for that user's single draft. We do not run a general crawl of the web, we do not build a public index, and we do not use fetched third-party content to train models.
8.5 If you are a publisher and you have a concern about our fetching, email [email protected]. Tell us your domain or domains and what you want. We will look at it, and where appropriate we can block Ingy from fetching your domain so that user requests pointing at it fail. You do not need to send a formal copyright notice to raise this — an email is enough.
8.6 If you would like to license your content for use with Ingy instead of blocking it, we are open to that conversation at the same address.
9. False and abusive notices
9.1 Knowingly making a false or misleading notice or counter-notice can carry legal liability, including liability for damages and costs to the person wrongly affected, and in some circumstances liability for a false statement made to us.
9.2 Do not use this procedure to suppress criticism, reporting, review, competition or lawful commentary. We take a dim view of it.
9.3 We may decline to act on, and may refuse to process further notices from, a sender we reasonably consider is abusing this procedure.
9.4 If you are not sure whether your rights have been infringed, take legal advice before sending a notice.
10. Other kinds of complaint
10.1 This policy is about copyright. If your complaint concerns something else — trade marks, defamation, privacy or data protection, impersonation, harassment, or unlawful content — email [email protected] with a clear description and we will direct it to the right process.
10.2 Nothing in this policy is a waiver of any right, remedy or defence available to us, or an admission that any particular legal regime applies to our service.
11. Changes to this policy
11.1 We may update this policy. The version number and effective date at the top will change.
11.2 The version in force when we receive a notice is the version we apply to it.
12. Governing law
12.1 This policy and any dispute arising from it are governed by the law of England and Wales, and the courts of England and Wales have jurisdiction.
12.2 If you are a consumer, this does not remove any statutory right you have to bring proceedings in your own country of residence.
Contact
IX Labs
27 Old Gloucester Street, London, WC1N 3AX, United Kingdom
General enquiries: [email protected]
Legal notices: [email protected]