Who we are
Our website address is cbdhash.co.uk.
Pornographic, sexually explicit, or erotic content.
Content that describes sexual acts or sex toys.
Escort services or other services that may be interpreted as providing sexual acts in exchange for compensation.
Content that describes or encourages bestiality.
zero-tolerance policy against child sexual abuse content. If we become aware of content facilitating or promoting the distribution of child sexual abuse content, we will report it to the appropriate authorities
Violence and dangerous activities
Graphic descriptions of realistic violence or violent threats to any person or animal.
Terrorist groups documenting their attacks.
Instructions for engaging in or facilitating violent activities, including bomb-making or weapon-making.
Self-harm, including instructions to carry out self-harm.
Bullying and harassment
Appearance or hygiene.
Ethics or morality.
Disability or medical condition.
Actions that lack reasonable sensitivity towards, or capitalize on, a natural disaster, atrocity, conflict, death, or other tragic event.
online gambling services, including but not limited to, online casinos, sports betting, lotteries, or games of skill if they offer prizes of cash or other value.
You are solely responsible for determining the legality of your Action in its targeted locale. Actions determined to be unlawful in locations where they are published will be removed.
Alcohol & Tobacco
Actions that facilitate or promote the sale of alcohol or tobacco.
We don’t allow Actions that promote excessive use of alcohol or tobacco, or use by minors
Actions that facilitate the sale or production of recreational drugs.
Actions that involve transmission of information that could be considered health information under the Health Insurance Portability and Accountability Act
We also don’t allow Actions that provide, collect, or store personal medical information, including data that could be considered data concerning health under the General Data Protection Regulation (GDPR).
Actions that provide services or store sensitive financial data in violation of applicable legal obligations.
Financial data or authentication data cannot be collected via the conversational interface.
Actions providing general financial information, including interest rates and stock prices, are permitted.
We don’t allow Actions that enable users to contact emergency responders. For example 911 or 999 services.
discusses mature themes, disturbing or distressing content, or frequently has profanity, it must include a disclaimer at the beginning of the user’s first conversation with the Action and in the Actions directory description.
it must include a warning indicating as such at the beginning of the user’s first conversation with the Action and in the Actions directory description.
Intellectual Property, Deception, and Spam
intellectual property rights of others, including trademark, copyright, patent, trade secret, and other proprietary rights. We also don’t allow Actions that encourage or induce infringement of intellectual property rights.
If you are a trademark owner and you believe an Action is infringing on your trademark rights, we encourage you to reach out to the developer directly to resolve your concern. If you can’t reach a resolution with the developer, please submit a trademark complaint
Actions that use another Action or entity’s brand, title, logo, or name in a manner that may result in misleading users. Impersonation can occur even if there isn’t an intent to deceive, so please be careful when referencing any brands that do not belong to you. This applies even if that brand doesn’t yet have a presence on the Directory.
ENCOURAGING INFRINGEMENT OF COPYRIGHT
Actions that induce or encourage copyright infringement. Before you publish your Action, look for ways it may be encouraging copyright infringement and get legal advice if necessary.
Actions that infringe on others’ trademarks. A trademark is a word, symbol, or combination that identifies the source of a good or service. Once acquired, a trademark gives the owner exclusive rights to the trademark usage with respect to certain goods or services.
Trademark infringement is the improper or unauthorized use of an identical or similar trademark in a way that is likely to cause confusion as to the source of that product. If your Action uses another party’s trademarks in a way that is likely to cause confusion, your Action may be removed.
Actions that attempt to deceive users. Actions must provide accurate disclosure of their functionality and perform as reasonably expected by the user. Actions must not attempt to mimic system functionality or warnings of any kind. Any changes to device settings must be made with the user’s knowledge and consent and be easily reversible by the user.
Actions that contain false or misleading information or claims, including in the trigger phrase, description, title, or icon. Don’t try to imply an endorsement or relationship with another entity where none exists.
Examples of misleading claims include:
- Misrepresenting or not accurately and clearly describing Action functionality, for example:
- An Action that claims to be a food delivery service in its description or invocation, but is actually a ride-sharing service.
- An Action that claims to be a restaurant reservation service, but only contains restaurant reviews.
- An Action that uses a trigger phrase related to coffee, but is actually a pizza delivery service.
- Misrepresenting the current status or performance on the Directory (e.g. “Editor’s Choice,” “Number 1 Action”).
- Featuring medical or health-related functionality that is misleading or potentially harmful.
- Claiming functionality that is impossible to implement.
- Actions that are improperly categorized.
- Misleading a user as to the content or destination of a link.
UNAUTHORIZED USE OR IMITATION OF SYSTEM FUNCTIONALITY
Actions that mimic or interfere with device or Assistant functionality. Examples of prohibited behaviour
Actions that spam users or the Directory in any way.
- Actions that push content to users’ mobile devices without their permission or send excessive or irrelevant content using the Update API.
- Actions whose primary purpose is to drive traffic to a website or app.
- Submitting multiple duplicative Actions to the Actions directory.
Privacy and Security
You must be transparent in how you handle user data (e.g., information provided by a user, collected about a user, and collected about a user’s use of the Action or device). This policy establishes the Directory’s minimum privacy requirements; you or your Action may need to comply with additional restrictions or procedures if required by an applicable law.
All Actions must:
Account linking and Identity
Don’t use any other method to associate a user with an account on your system, including using an association from another Action engaging in account linking. For example, if you offer multiple Actions requiring account linking, each Action must independently use the Account Linking API — using the configuration defined in the respective action package — to associate the user with the existing account.
If you initiate account linking mid conversation, then prior to triggering the account linking process you must explain why you are prompting the user to link their account.
Device and network abuse
We don’t allow Actions that interfere with, disrupt, damage, or access in an unauthorized manner the user’s device or other devices, computers, servers, networks, application programming interfaces (APIs), or services. This includes other Actions, any service, and the device’s network.
We don’t allow Actions that steal data, secretly monitor or harm users or that are otherwise malicious.
All Actions that collect user data must comply and fully disclose their functions.
The following are explicitly prohibited:
- Viruses, trojan horses, malware, spyware, and any other malicious software.
- Promoting or facilitating the distribution or installation of malicious software.
- Introducing or exploiting security vulnerabilities.
- Stealing a user’s authentication information (such as usernames or passwords).
- Tricking users into disclosing personal or authentication information.
- Running other Actions without the user’s prior consent.
- Secretly collecting device usage.
Actions and their listings on the Directory must not provide any means to activate or access functionality that violate these terms.
If your Action is associated with a security vulnerability that could be exploited to compromise another Action, application, device, or service, we may remove it to protect users.
Monetization and Ads
No in-conversation ads are permitted.
Naming, Directory Listing, and Promotion
Your Action’s invocation name and Actions directory listing is how users interact with and discover Actions. Your Action’s listing dramatically affects the directory’s quality, so avoid spammy listings, low quality promotion, and anything that artificially boosts your Action’s visibility. Fill out all of the details required for the directory listing, including providing visible, non-blank icons.
Your Action’s directory listing (including name, descriptions, etc.) must comply with the policies and not include words that are vulgar, sexually explicit, or offensive.
All Actions must have a unique invocation name that will allow users to trigger the Action’s functionality. Action names are unique within each so once a name is approved, no other Action can register the same name in the same language. Your directory listing must have at least one sample invocation, all of which must include your Action’s name, for example and consistently triggers your Action.
Names must meet the following requirements:
- One-word names are not allowed, unless the name is unique to your brand or trademark within the target country. Instructions to request an exception for individual countries are below. Compound words broken into multiple words will not circumvent this requirement, for example key board counts as one word.
- Two-word names are not allowed if one of the words is a definite article (the), indefinite article (a or an), pronoun (like my), or preposition (for, to, or of). For example, your name should not be a bicycle, an espresso, to amuse or for fun.
- A name uniquely identifies your Action, so it must distinguish itself from other Actions and from features of the Assistant. We don’t allow names that are:
- Common phrases (for example, thank you, how are you?, good morning)
- Confusingly similar with features of the Assistant (especially with home automation, device control, and media playback commands)
- Potentially confusing users into thinking they are interacting with is promoting, endorsing, or sponsoring content featured in the Action.
- Generic, including words or phrases that are categories of products, services, or content. We will consider exceptions to this prohibition on a case-by-case basis. Instructions to request an exception are below.
- Names of people or places are not allowed unless they also contain other words (for example, Bill’s horoscopeor New York tourism) or you are a government agency of that location (for example, the City of New York can register the name New York City).
- Some words and phrases are reserved and cannot be used in names, Test your name in the API dashboard to confirm it doesn’t use a reserved word or phrase. We may make exceptions for certain reserved words or phrases if used in a qualifying multi-word combination, if the name isn’t confusing, and if it doesn’t otherwise violate these policies. Instructions to request an exception are below.
- Depending on the language, some characters may be prohibited in the name pronunciation field; for example, languages using the Latin alphabet must contain only lower-case alphabetic characters, spaces between words, possessive apostrophes (for example, Sam’s science trivia), or periods used in abbreviations (for example, a. b. c.).
- Names must be easy to pronounce correctly and be phonetically distinct to avoid being misinterpreted as similar sounding words and other Action names (within the same language). Don’t use names that are phonetically similar to ones prohibited by these policies, such as vulgar, offensive, generic, or common names (even if spelt them differently).
In evaluating these policies, we consider the pronunciation of the word, how it’s spelled in the console, and the commonly accepted way to spell the pronounced word (if there is one).We will consider exceptions to certain naming policies on a case-by-case basis; you can request an exception filling out t
Allowed (for illustrative purposes only and subject to other policies)
Your Action’s invocation name must be a phonetic version of its display name. Permitted differences include: punctuation, spaces, and using numerals vs. spelling out numbers and ordinals (such as three vs. 3 or third vs. 3rd).
The description of your Action must accurately describe its functionality and the services or content it provides. Here are a few best practices for writing a description of your Action:
- Provide a clear, succinct description of how your Action can help users, for example, “You can use this Action to do X.” Excessive length, detail, or repetition in your Action description can result in a violation of this policy.
- Highlight what’s great about your Action. Share interesting and exciting facts about to help users understand what makes your Action special.
- Make sure that your Action’s title and description accurately describes its functionality.
- Avoid using excessive, repetitive, or unrelated keywords or references.
- Disclose whether your Action requires payment for any of its features.
User testimonials are not allowed in the Action’s description.
We don’t allow Actions that directly or indirectly engage in or benefit from promotional practices that are deceptive or harmful to users or the developer ecosystem. This includes Actions that engage in the following behavior:
- Using deceptive ads on websites, Actions, or other properties, including notifications that are similar to system notifications and alerts.
- Manipulating or inflating usage statistics, and product ratings, ranking or reviews.
- Engaging in unsolicited promotion via SMS services.
- Offering compensation for using Actions, including money, digital or physical goods.
It is your responsibility to ensure that any ad networks or affiliates associated with your Action comply with these policies and do not employ any prohibited promotion practices.
- Actions must be generally suitable for all ages including children under the age of 13 and not contain any inappropriate material, including adult themes, crude humor, and violent content.
- Actions must be designed for mixed audiences that include children under the age of 13. We cannot allow Actions into the Actions for Families program that are primarily designed for children under the age of 13.
- The primary purpose of the Action cannot be:
- To widely share unmoderated user-generated content, such as a social networking or user-forum Action, or
- To serve as a general utility, client, or communication Action, such as calculator, podcasting, home automation or reminder Actions.
- Actions may not collect or solicit any personally identifiable user data.
- Actions must not contain ads, including in streaming media. Self-promotional messages are acceptable.
- You represent that Actions submitted to the Actions for Families program are compliant with COPPA (Children’s Online Privacy Protection Rule) in the US, the EU General Data Protection Regulation, and other relevant statutes in your country including any APIs that your Action uses to provide the service.
Actions accepted to the Actions for Families program are required to continue to meet the program’s standards at all times, including in subsequent updates.
To ensure a great user experience, your Action must operate as described, provide a high-quality user experience, and take advantage of the platform’s features.
In addition, we reserve the right to reject Actions on the basis of content or functionality that are not explicitly prohibited by these policies, but that run contrary to these policies in spirit. In the event that your Action is rejected or removed under this section, we pledge to provide an explanation of our decision.
Special Requirements for Certain Use Cases
Certain APIs have special requirements, if your Action uses them, then it must also comply with those requirements.
All Actions must comply with these requirements:
- Don’t expressly direct users to a website, phone number, mobile app or alternative payment method to complete a transaction, whether within the Action via links or suggestion chips, or in the Action description. For example, don’t tell a user to visit a website, Action, or physical location (or provide a linkout chip) with a call to action to checkout or pay.
- If your Action enables users to complete a physical goods or services transaction, it must implement the Transactions API for Assistant. This does not include adding items to a basket.
- If your Actions enables users to complete a digital transaction or buy a subscription, it must implement the Digital Purchase API.
The following purchases and transactions (any agreement between a user and a business to fulfill a good or service) are supported on Actions
- Physical goods or services including:
- Purchase, rental or sale of physical goods (such as groceries, clothing, housewares)
- Purchase of physical services (such as car services, cleaning services, airfare, food delivery, tickets for live events)
- Reservations and bookings (such as hotel rooms), so long as the full price is paid at reservation/booking time or is clearly stated in advance in the check-out flow.
- Digital goods or services including:
- Purchase of digital goods (such as virtual currencies, extra lives, additional playtime, and special items)
- Subscription services (such as fitness, dating, education and content subscription services)
- Access to Action functionality and features (such as content or services)
Currently, Actions does not support money transfers from one user to another, either directly or via a licensed money transmitter, or donations to charitable or political entities.
Transactions API and Digital Purchase API Requirements
All Actions implementing the Transactions API, Digital Purchase API (a Billing service), or using Direct Actions (including the Food Order Direct Action API) must comply with these requirements:
- Abide by the Transaction Terms in the Terms of Service for Actions
- Implement all of the required methods and parameters, including proper order handling and acknowledgements, and don’t create duplicate orders.
- Provide accurate and timely information, including prices, and descriptions
- Provide your own customer service, and provide a customer service contact phone number and/or email address.
- Only use personal information obtained via the conversational interface to facilitate that transaction, including sending receipts, confirmations, and updates. You must independently obtain the user’s consent (via an opt-in) to use that information for any other purpose, including marketing.
- For Actions using the Digital Purchase API only:
- Only features or services bought within the Action, or on another platform under the same title as the Action, can be accessed by the user on the Actions platform
- Actions must not directly or indirectly lead users to a payment method other than via the Digital Purchase API, either within or outside of the action.
- For Actions using the Transactions API only
- Implement all required callback APIs related to providing transaction status updates within the specified time periods, and any follow-up actions.
- Provide an accurate and itemized receipt to all users by email and correctly set all related parameters for transactions where money is exchanged.
If you provide us with catalogs, menus, or other data via a data feed or other mechanism, the data must comply with these policies, including the sections on You must correctly implement all technical requirements and provide content for all required fields. The data provided must be relevant to the use case of feed and accurate. We may disable the feed (or a portion of it), disable use of the data, or takedown any related Actions for violations of these policies or if they create a poor user experience.
Actions controlling smart devices must ensure minimum security and safety precautions when the Action can:
- Unlock doors or disable physical security mechanisms.
- For example, unlocking car doors.
- Disarm or disable security or surveillance systems.
- For example, turning off a house alarm system.
- Operate devices that are capable of causing physical harm.
- For example, a cooking stove.
While the nature of the security and safety precautions may vary by the type of device, at minimum these devices must require account linking and a secondary user verification, such as confirmation on a secured mobile device or a password/PIN.
Security or surveillance Actions must not log PII of individuals outside the primary user without their consent. For example, doorbell Actions cannot log information about who may be at the door without the express consent of that individual. Actions that instruct passenger transport vehicles to move.
We also have additional restrictions related to Actions for passenger transport vehicles.
These policies do not limit or amend any terms of service or other agreements that apply to the user’s use of the applicable products or services unless the policies expressly state that they are amending specific terms of service or agreements.
When visitors leave comments on the site we collect the data shown in the comments form, and also the visitor’s IP address and browser user agent string to help spam detection.
If you upload images to the website, you should avoid uploading images with embedded location data (EXIF GPS) included. Visitors to the website can download and extract any location data from images on the website.
If you leave a comment on our site you may opt in to saving your name, email address and website in cookies. These are for your convenience so that you do not have to fill in your details again when you leave another comment. These cookies will last for one year.
If you visit our login page, we will set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser.
When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select “Remember Me”, your login will persist for two weeks. If you log out of your account, the login cookies will be removed.
If you edit or publish an article, an additional cookie will be saved in your browser. This cookie includes no personal data and simply indicates the post ID of the article you just edited. It expires after 1 day.
Embedded content from other websites
Articles on this site may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website.
Who we share your data with
How long we retain your data
If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognise and approve any follow-up comments automatically instead of holding them in a moderation queue.
For users that register on our website (if any), we also store the personal information they provide in their user profile. All users can see, edit, or delete their personal information at any time (except they cannot change their username). Website administrators can also see and edit that information.
What rights you have over your data
If you have an account on this site, or have left comments, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.
Where we send your data
Visitor comments may be checked through an automated spam detection service.
Your contact information
How we protect your data
What data breach procedures we have in place
What third parties we receive data from
What automated decision making and/or profiling we do with user data
Industry regulatory disclosure requirements