Who we are
Orabby is operated by Clickdee LLC ("we", "us"), 1021 E Lincolnway, Suite #5803, Cheyenne, WY 82001. Questions about this policy go to privacy@orabby.com.
This website
This public website sets no cookies and runs no analytics or advertising scripts. Its fonts are served from the site itself. Standard server logs, such as IP address and requested page, may be kept by our hosting providers in the United States for security and reliability.
Information we hold when you use Orabby
- Account details: your name, work email address, organisation name and sign-in credentials.
- The campaigns you plan and launch in Orabby, and your settings.
- Data we read from your Google Ads account after you connect it. This is described in the next section.
We use this information to run the service you asked for, to keep it secure, and to support you.
Google user data
What you authorise
You connect a Google Ads account by approving access on a Google consent screen. For that connection Orabby requests one permission, the Google Ads scope (https://www.googleapis.com/auth/adwords), and asks for offline access so that we can read results and keep your connection working without asking you to approve it each time. The Ads connection does not request your name, email address or other Google profile information. Signing in to Orabby with Google is a separate step, described next.
Signing in with Google
You can sign in to Orabby, and confirm your identity before sensitive actions, with your Google Account. For this we request the openid, email and profile scopes. From Google we receive your Google account identifier, your email address, whether Google has verified it (sign-in is refused if it is not), and your name. We keep the identifier and link it to your Orabby account. We do not read or store your profile picture. We use these only to find or create your Orabby account, to sign you in, and to check that you recently signed in at Google when you confirm a sensitive action. This sign-in does not give Orabby access to Google Ads or any other Google service.
What we read
- The Google Ads manager and client accounts you can access, with their IDs, names and currency, so you can choose which ones Orabby uses.
- Performance data for the campaigns and ad groups in those accounts, such as cost, clicks and impressions, to show results per ad group.
- Search terms that triggered your ads, so you can see what people searched for.
- The status and policy review of the ads we created, to show whether they are running.
What we write
- Campaigns you launch from Orabby, created in one request so that Google applies all of it or none: the campaign and its daily budget, ad groups, keywords, negative keywords and responsive search ads. The campaign is created paused unless you choose to go live, runs on the Google Search network only, and uses manual cost per click bidding.
- Targeting you choose: the country of the product, whether to reach people in that location or people in or interested in it, and, where Google offers them, age ranges, genders and household income bands that you exclude. Each exclusion is added to the campaign as its own targeting criterion. Orabby does not use these to build audiences or to learn anything about people.
- Ad assets in the plan you approved: sitelinks and promotions on each ad group, and callouts, a structured snippet and your business name on the campaign.
- Images and your business logo, if you add them. We upload each one to the asset library of the Google Ads account you chose and link it to the campaign.
- Removal of what a launch left behind. If Google creates a campaign but Orabby cannot save its record, we remove the campaign and budget that this launch created. Uploaded assets stay unlinked in your account library, because Google does not allow an asset to be removed.
- A pause of a campaign, but only if you have allowed automatic pausing in your organisation settings. You can switch it off at any time. Every pause is recorded in your activity log.
We do not otherwise change campaigns, bids or budgets in your Google Ads account, and we never edit or remove a campaign you did not launch from Orabby.
How we use it
We use Google user data only to provide and improve the user-facing features described above: building and launching your campaigns and showing you their results. We do not sell it, we do not use it for advertising of our own or for anyone else's, and we do not use it to develop, improve or train generalised artificial intelligence or machine learning models.
Limited Use
Orabby's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
- We use Google user data only to provide and improve the user-facing features that are visible in the Orabby interface.
- We do not transfer Google user data to others except as needed to provide those features, to comply with the law, or as part of a merger or sale of assets with notice to you.
- We do not use or transfer Google user data for serving advertisements, including retargeting, personalised or interest-based advertising.
- We do not allow people to read Google user data unless you give consent for specific data, it is needed for security or to investigate abuse, it is needed to comply with the law, or the data is aggregated and used for internal operations in line with applicable law.
How we protect it
- Your Google refresh token is encrypted at rest with AES-256-GCM, bound to your organisation's record, so it cannot be used for another organisation. It is decrypted only by our server when we call Google on your behalf.
- The token is never sent to your browser and is never written to logs.
- Connections use HTTPS. Each organisation's data is separated, and one organisation cannot see another's.
- Only organisation administrators can connect or disconnect Google Ads.
Where Google data goes
Google user data is stored in our database and processed on servers run by our hosting providers in the United States. We do not share it with other third parties, except as required to run the service (our hosting and database providers, acting on our instructions) or by law.
Revoking access
You can stop Orabby reaching your Google Ads account in either of two ways:
- In Orabby, an organisation administrator opens the Google Ads connection and chooses Disconnect. We revoke the token with Google, delete the stored token and stop using the connected accounts.
- In your Google Account, open myaccount.google.com/permissions, choose Orabby and select Remove access.
Deleting your data
Disconnecting removes our access to Google. To have your data deleted, an organisation administrator can request that the organisation be closed in Orabby, or you can email privacy@orabby.com. After an organisation is closed we keep its data for 90 days and then delete it. Records that the law requires us to keep are the exception. Data already deleted from the service may remain in our backups until they expire.
Sharing
We do not sell personal data. We share it only with service providers that help us run Orabby (for example hosting, email delivery and product usage analytics inside the Orabby application, which never receive Google user data) under written terms, and when the law requires it.
Retention
We keep account and campaign data while your organisation is active, and for 90 days after it is closed, unless the law requires longer.
Your rights
Depending on where you live, you may have the right to access, correct, delete or export your personal data, and to object to or restrict how we use it. Email privacy@orabby.com and we will respond within the time the law allows.
Children
Orabby is for businesses and is not directed to anyone under 18.
Changes to this policy
We will post changes on this page and update the effective date. If a change affects how we use Google user data, we will tell you in the product before it takes effect.
Contact
Clickdee LLC, 1021 E Lincolnway, Suite #5803, Cheyenne, WY 82001, privacy@orabby.com.