When my users record their voice using the Google's Cloud Speech API, how can I give them the option to delete them later? I tried to search everywhere but haven't found it yet. Google seems to allow this within their Assistant App, but what about developers building something similar?
Similarly, what is the retention policy for these recordings? I need to be able to tell my users something, too.
Why not read their terms?
Regarding customer deletion of data (section 6.1)
Google will enable Customer to delete Customer Data during the Term in a manner consistent with the functionality of the Services. If Customer uses the Services to delete any Customer Data during the Term and that Customer Data cannot be recovered by Customer, this use will constitute an instruction to Google to delete the relevant Customer Data from Google’s systems in accordance with applicable law. Google will comply with this instruction as soon as reasonably practicable and within a maximum period of 180 days, unless EU or EU Member State law requires storage.
It does not state a retention policy, though you should be able to contact them and get a definitive answer.
Related
I would like to know if there is an API that gives freely the flight paths of all aircraft currently flying or that had flight some days ago over the world. It could be in any projection and any format. I imagine that it would be most likely a table with each row being an aircraft/flight and the correspondent geopath in one column.
Thanks.
I was looking around for the same topic.
The terms and conditions for getting data from Flightradar24 are shown there
https://www.flightradar24.com/terms-and-conditions
... they talk only about getting data after a business contract on the kind of data (e.g. flights with a specific filtering) and on the format (JSON, CSV, ?). With the contract one may download the data, maybe via an API.
My conclusion: Flightradar24 does not share its full set of data, only a limited set with payment.
Searching for "Flightradar24 API" you will find some sites offering Flightradar24 data via their own API primarily requiring payment, a few for free at a very low level.
You will also find some software projects for accessing and processing data from the Flightradar24 sites with a focus on Python. But these software packages build on tracking the access of the Flightradar24 site from a mobile app or the desktop browser. Result: a few accesses of an endpoint may work then comes the stop sign: Flightradar requires an authenticated access.
Hello to all the community. Within the Metatrader platform, there is a way to create accounts once the desired broker has been selected. My problem arises when I want to automate this process from code. From my search on the internet I understand that the solution could be using the .crv / .dat files, from within the config folder where said platform is installed, which contain the necessary information. But unfortunately it hasn't worked for me because I don't even know how to read them.
Specifically, I would like to know if there is any API that allows me to carry out the explained process (account management), as well as consult information (account balance, trades ...) which is also shown on the platform. Currently I am only interested in demo type accounts.
The closest solution I've found is using this API, but it's not free and also doesn't work for all brokers.
There is basically no solution to register demo accounts for any broker this way as not all brokers support registering demo accounts via MT terminal.
If a broker allows creating demo accounts via MT terminal, then it is also possible to register a demo account via MetaApi MT account management api.
For most applications the revenue application owner will earn per demo MT account is much higher than a fee MetaApi charges for API use, thus the fee just makes sense. It allows the MetaApi team to continue working on the project while not reducing application owner earnings significantly.
However if your application is low margin then you might want to automate it yourself. In this case you will also need to spend either time or money or both to implement your own solution.
Long time ago, I took and passed the Google Analytics IQ certification test. At the time, I don't believe there were such things as Core Reporting API, Management API, and Metadata API (and probably some other Google Analytics related API's that I don't know about). Now that I am going through the Google Analytics IQ certification training course again (provided by Google, presented by Justin Curtoni?? I believe that's his name), I found that they now have Core Reporting API, Management API, and Metadata API.
I am a computer programmer by trade; so, I have no problem with programming using these API's. However, what I don't understand is, what do these API's buy me that the Google Analytics UI cannot offer? There is no reason to write a program that utilizes these API's simply because I can do it. To me, the existing Google Analytics UI has a lot of tools, reports, and other features that quite extensive. I am hoping that some of you can help me see something that I am probably missing.
The APIs are primarily for programmatic access. For example, if you need to create 1000 accounts all with the same property/view structure and then maybe add a few view filters to each of those accounts, you'll probably want to use the Management API. Doing that by hand would be a nightmare.
The same thing is true for the reporting API. Maybe you want to set up task that runs every monday morning and reports on the previous weeks data. And maybe you want to display that data on an internal dashboard for your company using some fancy charting library. You'd have to use the API to get the data.
Dashboards (executive summaries; managers often want nice visualizations instead of boring drill-downs)
Custom reports for user groups that do not have a Google Account or are not supposed to have access to full reports (e.g. Affiliates)
advanced filtering and aggregation (GA report cannot do everything)
You can combine analytics data with external data (e.g. you are not allowed to store personally identifiable information within GA; but you might store a custom key that allows you to link analytics data to customer data from you CRM or fulfillment system)
Machine-to-machine communication; I once did tracking for an airline that needed trend data on what people where searching for and what they where actually booking; that data was used to allocate/withdraw resources from busy/lame flights, and part of this was done by hooking up GA to their backend system
Take a look at the GA Partner Page. I would say the primary reason is to "liberate" GA Data from outside of GA itself. As Eike mentions, you can create dashboards and combine this data with other sources for a complete "View" of your online presence.
HI I guess there is no definite answer. Here are some things you can do with the APIs:
Automating AdWords CRO based on keyword ad and campaign performance.
Scoring leads based on Analytics data (Engagement with different items) and external data from a CRM.
Collecting unsampled data using multiple daily queries
Filtering using several dimension.
Tracking conversions for periods longer than supported by AdWords.
Looking at a funnel via segments
Analyzing funnels with non-linear structures
Create more robust alerts
Export data to BigQuery and analyse it together with data from other systems.
Create Machine learning apps for behavioural customizing your site.
Create a dashboard with data from multiple views
Use product recommendation to implements "better together" in an online store.
Automate creation of accounts and properties + their integration in a Hosting provider's console.
Cheers!!
I have developed one app in which i have used the Google Place API. This is what places doc says about limitation.
The Google Places API has the following query limits:
Users with an API key are allowed 1 000 requests per 24 hour period.
Users who have also verified their identity through the APIs console are allowed 100 000 requests per 24 hour period. A credit card is required for verification, by enabling billing in the console. Your card will not be charged for use of the Places API.
So my question is that if i enable billing for Place API then its free? Is it really true?
Yes, you will have what they are saying. I have done that, so I can confirm... If you put your credit card info, you are letting them know that you are a verified user, and that therefore you won't misuse their services.
And for the second question, we are talking about Google here. It is really true, you won't be charged, they can make money from other sources :)
EDIT:
Actually, if you need more than the "verified" option, it seems you can contact them as stated by Thor Mitchell (Product Manager #Google) in this topic at Quora: Pros and Cons of Places API
"The limits on use (after identity verification) is 100,000 requests
per day, and we're happy to talk to developers who need more about
their requirements."
As of today, the limit is 150,000 free requests per day, but the documentation is hard to make sense of in terms of how they bill overage.
Latest update March 2019:
"For an overview of pricing for the Google Maps Platform products, please see the Pricing Sheet.
To learn more about how Google Maps Platform APIs are billed, please see Understanding billing for Maps, Routes, and Places."
This question is for anyone that used Google Analytic API on a commercial website.
For instance you have a website where members can upload music and pay for a membership to track via Analytics how many people visited their uploads.
Does Google allow to use the Analytics API for commercial use?
The Analytics API may be used for both commercial and noncommercial purposes in ways consistent with these API Terms.
http://code.google.com/apis/analytics/docs/gdata/gdataTermsOfService.html
Please refer to the lengthy Terms of Service :)
EDIT: As #yc pointed out, this is a question toward the the API (thanks btw).
While I don't think my original answer is totally correct, I think it is worth mentioning the "Privacy" paragraph in the "Regular" Analytics TOS:
PRIVACY . You will not (and will not allow any third party to) use the
Service to track or collect personally
identifiable information of Internet
users, nor will You (or will You allow
any third party to) associate any data
gathered from Your website(s) (or such
third parties' website(s)) with any
personally identifying information
from any source as part of Your use
(or such third parties' use) of the
Service. You will have and abide by an
appropriate privacy policy and will
comply with all applicable laws
relating to the collection of
information from visitors to Your
websites. You must post a privacy
policy and that policy must provide
notice of your use of a cookie that
collects anonymous traffic data.
I am by no means a lawyer, but just want to point out that you need to be careful about what data you collect. Especially when using Event Tracking and Custom Variables.
From the API page:
What does the Google Analytics Data
Export API cost?
The Google Analytics
Data Export API is free. We intend to
always provide a basic level of
service for free. As we continue to
build out more advanced features and
functionality, we may revisit this
later.