Automation means repeated actions without a person actively performing them
The page defines automation on X as accounts or apps that take repeated actions without a person actively performing them. It says the page explains what is allowed, what violates the rules, and how violations are detected and handled. It is labelled "Updated April 2026" and is primarily intended for developers, so much of it addresses people building apps or bots rather than people who only use X.
Supporting quotations
Automation on >x< refers to accounts or apps that take repeated actions without a person actively performing them.
Updated April 2026
This page is primarily intended for developers.
Qualifications & exceptions
The page says it is primarily intended for developers.
The page is labelled as updated April 2026; no effective date is stated.
Not stated here
The page does not say how many repeated actions, or how often, make an account or app count as automated.
Account & Service Control · Company practice
X users are responsible for automated activity on their accounts
A user is ultimately responsible for actions taken with their account and for actions by applications associated with their account. If automated activity on the account violates the X Rules or these automation rules, X may take action on the account. The page names two examples: filtering the account's posts from search results, or suspending the account. The wording is "may", so these are possible responses, and the page does not say when each applies.
Supporting quotations
You are ultimately responsible for the actions taken with your account, or by applications associated with your account.
Users should investigate a third-party application before authorizing it
Before a user authorizes a third-party application to access or use their account, the page tells the user to make sure they have thoroughly investigated the application and understand what it will do. The page also points to a separate article on connecting and revoking third-party applications; that article is not part of this document and its text was not supplied.
Supporting quotations
Before authorizing a third-party application to access or use your account, make sure you've thoroughly investigated the application and understand what it will do.
Developers are encouraged to build automated posts, auto-replies and automated Direct Messages
Under "Do!", the page encourages building solutions that automatically broadcast helpful information in posts, run auto-reply campaigns to users who engage with the account's content, and automatically respond to users in Direct Messages. It also says to try new things that help people, as long as they comply with the rules, and to make sure the application gives a good user experience and keeps performing well over time. These are encouragements, not permissions that override the later rules on replies and Direct Messages.
Supporting quotations
Build solutions that automatically broadcast helpful information in posts.
Run creative campaigns that auto-reply to users who engage with your content.
Build solutions that automatically respond to users in Direct Messages.
Try new things that help people (and comply with our rules).
Make sure your application provides a good user experience and performs well — and confirm that remains the case over time.
Qualifications & exceptions
The page says new things must comply with X's rules.
Later sections set opt-in and opt-out conditions for automated replies, mentions and Direct Messages.
Not stated here
The page does not say how X checks that an application keeps a good user experience over time.
Legal Rights & Agreement Rules · Restriction or exception
Automation must not violate X's policies, with extra care on abuse and user privacy
Under "Don't!", the first item tells developers not to violate "these or other policies" and to be extra mindful of the rules about abuse and user privacy. The page does not list which other policies it means here; later sections name the X Rules and the Developer Agreement and Policy.
Supporting quotations
Violate these or other policies. Be extra mindful of our rules about abuse and user privacy.
Qualifications & exceptions
Covers these automation rules and other policies; abuse and user privacy rules are singled out.
Not stated here
"Other policies" is not defined in this item, and the text of those policies is not supplied here.
Legal Rights & Agreement Rules · Restriction or exception
The X API must not be abused and rate limits must not be circumvented
Under "Don't!", the page tells developers not to abuse the X API or attempt to circumvent rate limits.
Supporting quotations
Abuse the >x< API or attempt to circumvent rate limits.
Not stated here
The page does not define what counts as abuse of the API or list the rate limits.
Account & Service Control · Restriction or exception
Non-API automation such as scripting the X website is prohibited and can lead to permanent suspension
The page tells developers not to use non-API-based forms of automation, with scripting the X website as the example. It says using these techniques may result in the permanent suspension of the account. The permitted route for automation is therefore the X API, subject to the other rules on this page.
Supporting quotations
Use non-API-based forms of automation, such as scripting the >x< website. The use of these techniques may result in the permanent suspension of your account.
Qualifications & exceptions
The suspension consequence is stated as "may", so it is possible, not automatic.
Scripting the X website is an example ("such as"); other non-API methods are also covered.
Not stated here
The page does not say which other techniques count as non-API-based automation.
Legal Rights & Agreement Rules · Restriction or exception
Users must not be spammed or sent unsolicited messages
Under "Don't!", the page tells developers not to spam or bother users, or otherwise send them unsolicited messages. Later sections add specific opt-in conditions for automated replies, mentions and Direct Messages.
Supporting quotations
Spam or bother users, or otherwise send them unsolicited messages.
Qualifications & exceptions
Later sections set the conditions under which automated replies, mentions and Direct Messages may be sent.
Not stated here
The page does not define what makes a message "unsolicited" in this item.
Legal Rights & Agreement Rules · Restriction or exception
Automated activity is subject to the X Rules, and for API developers the Developer Agreement and Policy
As with all activity on X, automated activity is subject to the X Rules. A developer using the X API is also subject to the Developer Agreement and Policy. The page says all aspects of both apply to automated activity, and developers should review them to make sure their activity is compliant. It then lists rules to keep top of mind, which are additions to emphasize, not a replacement for those documents.
Supporting quotations
As with all activity on >x<, automated activity is subject to the >x< Rules and, if you’re a developer using the >x< API, the Developer Agreement and Policy.
You should carefully review these policies to ensure that your automated activity is compliant.
Although all aspects of the >x< Rules and the Developer Agreement and Policy apply to automated activity, you should keep the following rules top of mind:
Qualifications & exceptions
The Developer Agreement and Policy applies if you are a developer using the X API.
Not stated here
The text of the X Rules and the Developer Agreement and Policy is not supplied here, so this card cannot say what they require.
Violating these policies, or helping others violate them, can lead to enforcement and loss of API access
Automated applications or activities that violate these policies, or that facilitate or induce users to violate them, may be subject to enforcement action, potentially including suspension of associated X accounts. X may also rate limit, suspend or terminate a developer's access to the X API based on violations of these policies. The wording is "may" and "potentially", so these are possible responses, and the page does not say which violation leads to which response.
Supporting quotations
Automated applications or activities that violate these policies, or that facilitate or induce users to violate them, may be subject to enforcement action, potentially including suspension of associated >x< accounts. We may also rate limit, suspend, or terminate developers’ access to the >x< API based on violations of these policies.
Qualifications & exceptions
Applies to violations of these policies, and to activity that facilitates or induces users to violate them.
Enforcement is stated as "may" and "potentially including".
Not stated here
The page does not describe a notice or appeal process for enforcement action.
Legal Rights & Agreement Rules · Restriction or exception
Automated posts and Direct Messages must not be spam
The page prohibits sending automated posts or Direct Messages that are spam, or otherwise engaging in spamming activity. It lists examples of spammy behavior to avoid with automation; the examples are illustrative, not a complete list.
Supporting quotations
Spamming: You may not send automated posts or Direct Messages that are spam, or otherwise engage in spamming activity. Some examples of spammy behavior to avoid with automation include:
Qualifications & exceptions
The listed examples are introduced as "some examples", so the list is not exhaustive.
Not stated here
The page does not define spam beyond the listed examples.
Legal Rights & Agreement Rules · Restriction or exception
Automation must not post about trending topics or try to manipulate them
As an example of spammy behavior, the page says a person may not automatically post about trending topics on X, or use automation to attempt to influence or manipulate trending topics.
Supporting quotations
Trending topics: You may not automatically post about trending topics on >x<, or use automation to attempt to influence or manipulate trending topics.
Account & Service Control · Restriction or exception
Duplicative or substantially similar posts, and duplicate automated accounts, are not allowed
The page says a person may not post duplicative or substantially similar posts on one account or across multiple accounts they operate. It also says a person may not create or automate multiple accounts for duplicative or substantially similar use cases. An exception follows: automating multiple accounts for related but non-duplicative use cases is permitted. The page's example is separate accounts that post when the Hubble Space Telescope passes over different cities.
Supporting quotations
You may not post duplicative or substantially similar posts on one account or over multiple accounts you operate.
You may not create and/or automate multiple accounts for duplicative or substantially similar use cases.
However, automating multiple accounts for related but non-duplicative use cases is permitted.
Qualifications & exceptions
Multiple accounts are permitted only for related but non-duplicative use cases.
The Hubble example is an illustration of a permitted use, not a limit.
Not stated here
The page does not say how different two use cases must be to count as non-duplicative.
Legal Rights & Agreement Rules · Restriction or exception
Automated posts and Direct Messages must not contain misleading links
The page prohibits automated posts or Direct Messages that contain misleading links. It gives as examples links that maliciously or deceptively redirect through landing pages or ad pages before showing the final content.
Supporting quotations
You may not send automated posts or Direct Messages containing links that are misleading, including links that maliciously or deceptively redirect through landing pages or ad pages before displaying the final content.
Qualifications & exceptions
Misleading links include, but are not limited to, malicious or deceptive redirects through landing or ad pages ("including").
Content & IP Rights · Restriction or exception
Automated posts and Direct Messages must follow the media policy, and sensitive-media accounts should be marked
Automated posts and Direct Messages must comply with X's media policy. The page also says a person should mark their account as potentially sensitive if they intend to post graphic, pornographic or potentially sensitive media. The first part is a "must"; the marking step is stated as "should".
Supporting quotations
Automated posts and Direct Messages must comply with the >x< media policy, and you should mark your account as potentially sensitive if you intend to post graphic, pornographic, or potentially sensitive media.
Qualifications & exceptions
Marking the account as potentially sensitive applies if the person intends to post graphic, pornographic or potentially sensitive media.
The marking step is "should", not "must".
Not stated here
The media policy is linked but its text is not supplied here, so this card cannot say what it allows or forbids.
Legal Rights & Agreement Rules · Restriction or exception
Automation must not encourage abuse, violence, hateful conduct or harassment, on or off X
The page prohibits any automated activity that encourages, promotes or incites abuse, violence, hateful conduct or harassment. The prohibition covers conduct both on and off X.
Supporting quotations
Abusive behavior: You may not engage in any automated activity that encourages, promotes, or incites abuse, violence, hateful conduct, or harassment, on or off >x<.
Qualifications & exceptions
Applies on or off X.
Data Access & Collection · Restriction or exception
Private or confidential information about a person must not be posted without their prior express authorization
Among the rules to keep top of mind for automated activity, the page says a person may not post private or confidential information about a person without that person's prior express authorization.
Supporting quotations
Private information: You may not post private or confidential information about a person without their prior express authorization.
Qualifications & exceptions
Authorization must be prior and express.
Not stated here
The page does not define private or confidential information.
Legal Rights & Agreement Rules · Restriction or exception
Automated activity should not surprise or mislead users, or send mature content they did not ask for
The page says these ground rules apply to all automated activity on X. Automated activity should honor users' expectations, and the page says to ask for the user's permission before taking an action if unsure. It also says not to Direct Message, mention or reply to users with potentially sensitive content, including profanity, unless they have clearly indicated in advance an intent to receive it.
Supporting quotations
In addition to the policies above, the following ground rules apply to all automated activity on >x<:
Don’t surprise or mislead users: Automated activity should honor users’ expectations. Ask for the user’s permission before taking an action if you aren’t sure.
Mature content or profanity: Don’t Direct Message, mention, or reply to users with potentially sensitive content (including profanity), unless they’ve clearly indicated an intent to receive it in advance.
Qualifications & exceptions
Applies to all automated activity on X.
Sensitive content may be sent only if the user clearly indicated an intent to receive it in advance.
Not stated here
The page does not say how a user's expectations are measured.
Data Access & Collection · Procedure
Do not ask users for personal information in public posts; ask for the minimum in Direct Messages
Under the heading about information requested or exchanged on X, the page says not to ask users to send personal or private information in a public post. If more is needed, for example for customer service, the page says to ask the user to share it by Direct Message or another private channel, and suggests considering a Direct Message deep link. For Direct Messages, it says to ask only for the minimum information needed to provide the service. For particularly sensitive information, such as credit card information, it says to consider directing users to a website or other appropriate channel. The "should" and "consider" wording makes the last parts recommendations.
Supporting quotations
Be thoughtful about the information you request or exchange on >x<
Don’t ask users to send you personal or private information via a public post.
you should ask the user to share such information by Direct Message or another private channel.
You should only ask users for the minimum amount of information you need to provide them with service.
Qualifications & exceptions
Asking by public post is the prohibited route; Direct Message or another private channel is the suggested route.
Directing users to a website for particularly sensitive information is something to "consider", not a requirement.
Not stated here
The page does not define which information counts as particularly sensitive beyond the credit card example.
The extracted list shows the lead-in and the two sub-items (posts, Direct Messages) as separate items; the card follows that structure.
Account & Service Control · Company practice
Violating the activity-specific rules, or helping others violate them, can lead to enforcement
The activity-specific rules apply to taking specific automated actions on X, and the page says to read them carefully because they describe both permitted and prohibited uses of automation. Automated applications or activities that violate these rules, or that facilitate or induce users to violate them, may be subject to enforcement action, including suspension of associated X accounts. X may also rate limit, suspend or terminate developers' access to the X API based on violations of these rules. The page reminds readers to review the spam guidelines in the X Rules so that activity by them, their app, or other users through their app or service is not flagged as spam.
Supporting quotations
The activity-specific rules in this section apply to taking specific automated actions on >x<.
Automated applications or activities that violate these rules, or that facilitate or induce users to violate them, may be subject to enforcement action, including suspension of associated >x< accounts. We may also rate limit, suspend, or terminate developers’ access the >x< API based on violations of these rules.
you should also carefully review the spam guidelines in the >x< Rules to avoid having activities performed by you, your app, or other users through your app or service flagged as spam.
Qualifications & exceptions
Applies to violations of the activity-specific rules and to activity that facilitates or induces users to violate them.
Enforcement is stated as "may".
Not stated here
The spam guidelines in the X Rules are linked but their text is not supplied here.
The page does not say which violation leads to which response.
Account & Service Control · Restriction or exception
Authorizing an app through OAuth is not by itself enough consent for automated actions
Users may authorize an app or service to access their X account through OAuth. The page says that this authorization does not by itself constitute sufficient consent to take automated actions through that user's account. The consent conditions in the next card apply as well.
Supporting quotations
A user authorizing your app or service to access their >x< account through OAuth does not by itself constitute sufficient consent to take automated actions through that user’s account.
Qualifications & exceptions
Applies to automated actions taken through a user's account by an app or service the user has authorized through OAuth.
Account & Service Control · Restriction or exception
Automated actions through another user's account need a clear description, express consent and honored opt-outs
A person may take automated actions through another X user's account only if they do all three things: clearly describe to the user the types of automated actions that will occur, receive the user's express consent to take them, and immediately honor a user's request to opt out of further automated actions. The three items are joined by "and", so all are required.
Supporting quotations
You may only take automated actions through another >x< user’s account if you:
clearly describe to the user the types of automated actions that will occur;
receive express consent from the user to take those automated actions; and
immediately honor a user’s request to opt-out of further automated actions.
Qualifications & exceptions
All three conditions are required (the list is joined by "and").
Applies to automated actions through another X user's account.
Not stated here
The page does not say how express consent must be collected or recorded.
Account & Service Control · Restriction or exception
Substantially changing an app's purpose or functionality requires new express consent
If a person substantially changes the purpose or functionality of their app or service, the page says they must re-obtain express consent from the user to take automated action through the user's account before doing so.
Supporting quotations
If you substantially change the purpose or functionality of your app or service, you must re-obtain express consent from the user to take automated action through their account before doing so.
Qualifications & exceptions
Applies if the purpose or functionality is substantially changed.
The new consent must be obtained before the automated action.
Not stated here
The page does not say what counts as a substantial change.
Account & Service Control · Restriction or exception
Consent rules cover every automated action through another account; bulk delete tools must warn posts are unrecoverable
The consent requirements apply to any automated action through another X user's account, with posting, sending Direct Messages, deleting posts or Direct Messages, and following or unfollowing named as examples. For applications that let users delete posts in a bulk or automated manner, the page also says the application must clearly state that posts are not recoverable once deleted.
Supporting quotations
These requirements apply to any automated action taken through another >x< user’s account, including posting posts, sending Direct Messages, deleting posts or Direct Messages, or following/unfollowing other accounts.
For applications that offer users the ability to delete posts in a bulk or automated manner, you must also clearly state that posts are not recoverable once deleted.
Qualifications & exceptions
The listed actions are examples ("including").
The warning duty applies to applications that offer deletion of posts in a bulk or automated manner.
Content & IP Rights · Permission or license
Automated posts may be based on outside information if the publisher is sufficiently authorized
The page says a person may post automated posts based on outside sources of information, such as an RSS feed or weather data, as long as they are sufficiently authorized to publish that information.
Supporting quotations
You may post automated posts based on sources of outside information — such as an RSS feed, weather data, etc. — as long as you are sufficiently authorized to publish such information.
Qualifications & exceptions
Permitted only if the person is sufficiently authorized to publish the information.
RSS feed and weather data are examples ("such as").
Not stated here
The page does not say what counts as being sufficiently authorized.
Account & Service Control · Permission or license
Other automated posts are allowed for entertainment, informational or novelty purposes if all other rules are followed
Excluding mentions and replies, the page says a person may post automated posts for entertainment, informational or novelty purposes, provided they comply with all other rules. It reminds readers that accounts posting duplicative, spammy or otherwise prohibited content may be suspended.
Supporting quotations
Provided you comply with all other rules, you may post automated posts for entertainment, informational, or novelty purposes.
accounts posting duplicative, spammy, or otherwise prohibited content may be subject to suspension.
Qualifications & exceptions
Does not cover automated mentions or replies, which have their own rules.
Allowed only for entertainment, informational or novelty purposes and only if all other rules are followed.
Suspension is stated as "may".
Legal Rights & Agreement Rules · Restriction or exception
Automated replies and mentions that reach many users unsolicited are not permitted
The page says the reply and mention functions are meant to make communication between X users easier. Automating them to reach many users on an unsolicited basis is called an abuse of the feature and is not permitted. For example, automated replies sent to posts based on keyword searches alone are not permitted. Spammy or duplicative use may result in enforcement action, such as removal of the person's posts from Search or suspension of their app or account. The next card sets the conditions under which automated replies or mentions are allowed.
Supporting quotations
Automating these actions to reach many users on an unsolicited basis is an abuse of the feature, and is not permitted. For example, sending automated replies to posts based on keyword searches alone is not permitted.
Spammy or duplicative use of mentions and replies may result in enforcement action, such as the removal of your posts from Search or the suspension of your app or account.
Qualifications & exceptions
Applies to automated replies and mentions sent on an unsolicited basis to many users.
Enforcement is stated as "may"; removal from Search and suspension are examples.
Not stated here
The page does not say how many users counts as "many".
Legal Rights & Agreement Rules · Restriction or exception
Automated replies and mentions need opt-in, an opt-out, one per interaction and a reply to the original post
A person may send automated replies or mentions to X users only so long as four conditions are met. First, before sending, the recipient or mentioned users have requested or clearly indicated on X an intent to be contacted by the sender (opted in), for example by replying to a post from the account or sending a Direct Message. Second, the sender provides a clear and easy way to opt out and promptly honors all opt-out requests. Third, the sender sends only one automated reply or mention per user interaction. Fourth, where the campaign is based on users replying to the sender's post, the automated reply is a reply to the user's original post.
Supporting quotations
However, you may send automated replies or mentions to >x< users so long as:
in advance of sending the automated reply, the recipient or mentioned user(s) have requested or have clearly indicated an intent on >x< to be contacted by you (i.e. opted in), for example by replying to a post from your account, or by sending you a Direct Message;
you provide a clear and easy way for such users to opt-out of receiving automated replies and mentions, and promptly honor all such opt-out requests;
you only send one automated reply or mention per user interaction; and
the automated reply or mention is a reply to the user’s original post (if your campaign is based on users posting a reply to your post).
Qualifications & exceptions
All four conditions are required (the list is joined by "and").
The fourth condition applies only if the campaign is based on users posting a reply to the sender's post.
Not stated here
The page does not define "user interaction" for the one-reply limit beyond the examples given.
Legal Rights & Agreement Rules · Restriction or exception
Opt-in can take many forms, but following an account alone is not enough
The page says opt-in techniques and indications of user intent take many forms depending on the use case. Examples are a post from the account that clearly says a specific action, such as Reposting it, will opt the user into an automated response, and a user's mention of the account suggesting they wish to receive a response. If a campaign uses a hashtag, users should also mention the account in their posts. The page states that a user following an account is not on its own a sufficient indication of intent to receive an automated response.
Supporting quotations
Opt-in techniques and indications of user intent take many different forms, depending on the specifics of your use case and implementation.
A post from your account that clearly indicates that a user taking a specific action on that post (such as Reposting it) will opt the user into receiving an automated response.
If you want to run an auto-reply campaign with a campaign- or use-case-specific hashtag, users should also mention you in their posts.
Note that a user following your account is not on its own a sufficient indication of user intent to receive an automated response.
Qualifications & exceptions
The examples are illustrative ("some examples").
For a campaign using a campaign- or use-case-specific hashtag, users should also mention the account in their posts.
Following is not sufficient on its own.
Not stated here
The page does not list every acceptable way to opt in.
Legal Rights & Agreement Rules · Procedure
X recommends filtering sensitive language and checking that the post still exists
The page recommends that accounts communicating with users through automated mentions or replies appropriately filter responses based on potentially sensitive language in user handles, display names and post text, and on potentially sensitive media. It also recommends checking that the post being mentioned or replied to still exists, for example using the statuses/lookup endpoint on the X API. These are recommendations, not stated requirements.
Supporting quotations
Additionally, we recommend that any accounts that will communicate with users via automated mentions or replies:
Appropriately filter responses based on potentially sensitive language in user handles, display names, and post text, as well as potentially sensitive media;
Check that the post you are mentioning or replying to still exists (for example, using the statuses/lookup endpoint on the >x< API).
Qualifications & exceptions
Stated as "we recommend", not as a requirement.
Applies to accounts that communicate with users via automated mentions or replies.
Account & Service Control · Restriction or exception
AI-powered reply bots are allowed only with X's prior written and explicit approval
Provided all other rules are followed, the page says a person may use artificial intelligence to create automated reply bots that generate dynamic, context-aware responses. The deployment or operation of any AI reply bot, however, requires prior written and explicit approval from X. The page says to contact a dedicated point of contact or submit a request through the developer portal for review.
Supporting quotations
Provided you comply with all other rules, you may leverage artificial intelligence (AI) technologies to create automated reply bots that generate dynamic, context-aware responses
the deployment or operation of any AI reply bot requires prior written and explicit approval from >x<. Contact your dedicated point of contact or submit a request through the developer portal for review.
Qualifications & exceptions
Applies to the deployment or operation of any AI reply bot.
The approval must be prior, written and explicit.
AI reply bots must also comply with all other rules.
Not stated here
The page does not say what X considers when reviewing an approval request, or how long review takes.
Legal Rights & Agreement Rules · Restriction or exception
Unsolicited Direct Messages must not be sent in a bulk or automated manner
The page says a person may not send unsolicited Direct Messages in a bulk or automated manner, and should be thoughtful about how often they contact users by Direct Message. The next card sets the conditions under which automated Direct Messages are allowed.
Supporting quotations
You may not send unsolicited Direct Messages in a bulk or automated manner, and should be thoughtful about the frequency with which you contact users via Direct Message.
Qualifications & exceptions
The prohibition applies to unsolicited Direct Messages sent in a bulk or automated manner.
Frequency is a "should be thoughtful" recommendation, not a stated limit.
Not stated here
The page does not give a number for acceptable Direct Message frequency.
Legal Rights & Agreement Rules · Restriction or exception
Automated Direct Messages are allowed only after the recipient opted in and with an easy opt-out
A person may send automated Direct Messages to users only so long as two conditions are met. First, before sending, the recipient has requested or clearly indicated on X an intent to be contacted by the sender via Direct Message, for example by sending the sender a Direct Message. Second, the sender provides a clear and easy way to opt out of automated Direct Messages and promptly honors all opt-out requests. Both conditions are required.
Supporting quotations
You may send automated Direct Messages to users so long as:
in advance of sending the Direct Message, the recipient(s) have requested or have clearly indicated an intent on >x< to be contacted by you via Direct Message, for example by sending you a Direct Message; and
you provide a clear and easy way for such users to opt-out of receiving automated Direct Messages, and promptly honor all such opt-out requests.
Qualifications & exceptions
Both conditions are required (the list is joined by "and").
The opt-in must come before the Direct Message is sent and must be for contact by Direct Message.
Not stated here
The page does not list every way a user can indicate intent beyond the example given.
Legal Rights & Agreement Rules · Restriction or exception
Being able to receive a Direct Message does not by itself mean the user asked for automated ones
The page says that a user being technically able to receive a Direct Message from the sender does not necessarily mean the user has requested or expects automated Direct Messages from the sender. It gives three examples of technical ability: the user follows the sender, the user has enabled receiving Direct Messages from any account, or the user is in an existing Direct Message conversation with the sender.
Supporting quotations
The fact that a user is technically able to receive a Direct Message from you (e.g. because the user follows you, has enabled the ability to receive Direct Messages from any account, or because the user is in a pre-existing Direct Message conversation with you) does not necessarily mean they have requested or expect to receive automated Direct Messages from you.
Qualifications & exceptions
The wording is "does not necessarily mean", so ability to receive does not settle the question either way.
The three situations are examples ("e.g.").
Data Access & Collection · Company commitment
Requesting personal information by automated Direct Message requires explaining how it will be used
Referring back to the ground rules, the page says to be thoughtful about the amount and type of information requested or exchanged with users in Direct Messages. If a person asks a user for personal or private information in an automated Direct Message, they must clearly explain how they will use the information. The page suggests, as something to consider, including a link to a privacy policy in the Direct Message and in the X profile bio.
Supporting quotations
If you will be asking a user to provide personal or private information via an automated Direct Message, you must clearly explain how you will use the information you’re collecting.
Consider including a link to your privacy policy in your Direct Message to the user, as well as in your >x< profile bio.
Qualifications & exceptions
The explanation duty applies when asking for personal or private information in an automated Direct Message.
Including a privacy policy link is "consider", not a requirement.
Not stated here
The page does not say what the explanation must contain beyond how the information will be used.
Sharing & Disclosure · Restriction or exception
Information received in a Direct Message must not be shared publicly without explicit consent
The page says a person may not publicly share information received in a Direct Message conversation with a user without first obtaining the user's explicit consent. Its example is a user asking by Direct Message about a purchase: the person may not mention that user in a public post including information about the purchase unless they have the user's explicit consent.
Supporting quotations
Don’t publicly share information received in a Direct Message conversation with a user without first obtaining explicit consent from the user.
you may not mention the user in a public post that includes information about their purchase unless you have the user’s explicit consent to do so.
Qualifications & exceptions
Applies to information received in a Direct Message conversation.
The consent must be explicit and obtained first.
Legal Rights & Agreement Rules · Restriction or exception
After a user-initiated interaction ends, no follow-up Direct Messages or mentions without permission
The page says that after a user-initiated interaction ends, a person may not send additional follow-up Direct Messages or mention users in a post unless they get permission from the user.
Supporting quotations
After a user-initiated interaction ends, don’t send additional follow-up Direct Messages or mention users in a post unless you get permission from the user.
Qualifications & exceptions
Applies after a user-initiated interaction ends.
Permission from the user is the exception.
Not stated here
The page does not say when an interaction is considered to have ended.
Legal Rights & Agreement Rules · Restriction or exception
Automated likes and hiding replies are not allowed
The page says a person may not like posts or hide replies in an automated manner.
Supporting quotations
Automated likes or hide replies: You may not like posts or hide replies in an automated manner.
Legal Rights & Agreement Rules · Permission or license
Automated Reposts are allowed for stated purposes only; bulk or spammy Reposting violates the rules
Provided all other rules are followed, the page says a person may Repost or Quote post in an automated manner for entertainment, informational or novelty purposes. It says automated Reposts often lead to negative user experiences, and that bulk, aggressive or spammy Reposting is a violation of the X Rules.
Supporting quotations
Provided you comply with all other rules, you may Repost or Quote post in an automated manner for entertainment, informational, or novelty purposes.
bulk, aggressive, or spammy Reposting is a violation of the >x< Rules.
Qualifications & exceptions
Allowed only for entertainment, informational or novelty purposes and only if all other rules are followed.
Bulk, aggressive or spammy Reposting is a violation.
Not stated here
The page does not define bulk or aggressive Reposting.
The linked X Rules text is not supplied here, so this card cannot say what they require.
Legal Rights & Agreement Rules · Restriction or exception
Following or unfollowing accounts in a bulk, aggressive or indiscriminate manner is not allowed
The page says a person may not follow or unfollow X accounts in a bulk, aggressive or indiscriminate manner, and that aggressive following violates the X Rules. It points readers to following rules and best practices, which are linked but not supplied here. It also says applications that claim to get users more followers are prohibited under the X Rules.
Supporting quotations
You may not follow or unfollow >x< accounts in a bulk, aggressive, or indiscriminate manner.
applications that claim to get users more followers are also prohibited under the >x< Rules.
Qualifications & exceptions
The prohibition applies to bulk, aggressive or indiscriminate following or unfollowing.
Applications that claim to get users more followers are separately prohibited.
Not stated here
The linked following rules and best practices are not supplied here, so this card cannot say what they require.
Legal Rights & Agreement Rules · Restriction or exception
Adding users to lists or posts to collections in a bulk or indiscriminate manner is not allowed
The page says a person may not add X users to lists or add posts to collections in a bulk or indiscriminate manner, and that adding a large number of unrelated users to lists violates the X Rules.
Supporting quotations
You may not add >x< users to lists or add posts to collections in a bulk or indiscriminate manner. Adding a large number of unrelated users to lists is a violation of the >x< Rules.
Qualifications & exceptions
The prohibition applies to bulk or indiscriminate additions.
Not stated here
The page does not say how many additions count as a large number.
The linked X Rules text is not supplied here, so this card cannot say what they require.