I'm planning on publishing an app on Google Play that uses AdMob and location data to draw pins on an in-app Google Map and need a privacy policy. I'm not sure how to make one so I thought I would use a policy generator for now until I can see if I can afford to have a lawyer write one up.
So the question is what privacy policy generator should I use?
I use this generator it is very good. if you have Facebook login in your app you may need to add a paragraph to enable user to retrieve and/or delete their data from your app, usually I add an email for people who wants to remove their data and that's it.
Related
I want to publish a simple app that doesn't collect any personal data. It is an offline game (noughts and crosses), that doesn't require any account, and stores only field state on the user's device. I don't have any server and don't transfer the data anywhere, so it's fully offline. But Google Play asks for a Privacy Policy. How can I get it? Is there any standard Privacy Policy for such type of application? Can I just write something like "We don't store and transfer any personal data"?
Disclaimer: I Am Not A Lawyer
I recently ran into this myself. I have a very simple app that does not collect any personal information.
I looked all over and tried a few of the privacy policy generators, but they all seemed like overkill. So I started with a simple statement:
This application does not collect or store personal data.
Then based on this comment, I added another note:
If you installed this application from Google Play, then Google Play does collect some personal data. Please see the privacy policy for Google Play Services here: https://policies.google.com/privacy
Here's the whole thing: https://github.com/bmaupin/android-pitchpipe/blob/main/metadata/en-US/privacy_policy.txt
Easiest way is just to use a privacy policy generator such as this one: https://app-privacy-policy-generator.firebaseapp.com/
It's simple to use and only takes a few minutes to get you a privacy policy
What I want to build:
I want to build a website where users can connect their google calendars (this will use Google Calendar API's)
and view their calendar events, as well as edit them, and create new ones.
My problem:
In order to do so, google says my app needs to be verified, which can take weeks, and I also need to set up terms of services pages, privacy policy pages
I also need to supply authorised javascript origins which MUST start with https, which of course is a problem during development, since my origin is http://localhost
I also need to set up support emails and homepage link
Question
I just want to start building my application without having to set up a whole production-ready website eco system.
Is there anyway I can use these Google Calendar APIs for editing/creating calendar events locally, without having to set up everything mentioned above first?
Unverified apps can still be used by the developer who created the project on google developer console.
Unverified app screen
The app or script might display an "unverified app" screen before it displays the consent screen. This is based on the specific scopes that your app includes in the request.
You can still work on your app while you are going though the verification process. However that being said i would start that process asap it can take a long time to get verified.
Yes, you can. As far as I am able to tell, all the verification step does is remove the "unverified app" screen. As long as you click Advanced > Go To ... (unsafe), you should be able to create and edit calendar events for that user in your application.
In order to be able to create and edit calendar events, you need to use the most sensitive scope, which is https://www.googleapis.com/auth/calendar. I couldn't figure out how to edit and create calendar events in my web app until I changed my scope from calendar.events to calendar.
Creating Events: https://developers.google.com/calendar/create-events
Just wondering if someone can clear this up for me as its kind of a grey area and not sure what to do.
I have a website that is split into frontend and api and has a subscription service provided by stripe on the api. I am now making apps in ionic for both apple and google stores but Im unsure of how the payments will work on the platforms, ideally i would like to just stick to using stripe but Ive been reading about both stores and this is where I need guidance.
From what I have read it seems to be that I have to use google play billing and apples alternative. Do I have to use these for the apps going into their respective stores or can I continue to use stripe within the apps? As i see it its a multi platform saas. So why cant I just send the card info to my api for charging?(I know theres alot of security involved and its not as trivial as I make it out to be)
Ive been reading conflicting statements from multiple sites and Im just not sure which is correct and the docs on google play billing make no reference to this. Its a multiplatform service so can I just send on the card details to my api
But what I have found is that apple have this
3.1.3(b) Multiplatform Services: Apps that operate across multiple platforms may allow users to access content, subscriptions, or features they have acquired elsewhere, including consumable items in multi-platform games, provided those items are also available as in-app purchases within the app. You must not directly or indirectly target iOS users to use a purchasing method other than in-app purchase, and your general communications about other purchasing methods must not discourage use of in-app purchase.
Which to me states that I have to use Apple Pay and make no reference to my other payment methods for fear of being refused from the store.
I can't comment for Apple. For Google Play the best place to answer this sort of question is the Developer policy center. In the Monetization and Ads section it says
Developers offering products within another category of app downloaded on Google Play must use Google Play In-app Billing as the method of payment, except for the following cases:
Payment is solely for physical products
Payment is for digital content that may be consumed outside of the app itself (e.g. songs that can be played on other music players).
You should read all of the linked page and decide what category the stuff you are selling falls into.
I was reading about creating a custom tinywebdb and wondered will it offer me more entries than the the normal tinywebdb.
I am creating an app using app inventor where users can comment and review about a specific product.
So I was wondering if I create my google cloud, will I be able to upload it into app inventor? If you guys have better advises please tell me!
The limit of 1000 entries is only valid for the default TinyWebDB component on the test service provided by App Inventor. For a custom TinyWebDB there is no such limit, see also Creating a Custom TinyWebDB Service.
You can read here more about quotas and pricing.
See also this guide for the setup and don't sign up for the free trial.
Generally, as already suggested in the forum, I would use a fusiontable instead, which offers better filter and query possibilities. Remember, in TinyWebDB you can only store tag/value pairs.
I want to build something similar to a poll service for mobile but it doesn't need Facebook.
After Facebook's acqusition, is Parse.com still a viable option if your web app does not need Facebook integration? Could app developers (customers) log in to my backend without a Facebook account?
Is it possible to build premium features with Parse and then charge for them?
Do you own your data when using Parse.com? I.e., can you export it in case you decide to move to another service in the future?
I am hoping someone with experience can shed some light on this. Thank you!
After Facebook's acqusition, is Parse.com still a viable option if
your web app does not need Facebook integration? Could app developers
(customers) log in to my backend without a Facebook account?
yes,for now.
Is it possible to build premium features with Parse and then charge
for them?
yes
Do you own your data when using Parse.com? I.e., can you export it in
case you decide to move to another service in the future?
yes
I'd suggest you always have a backup plan,when using a BAAS.I pity Stackmob users that didnt.You dont know if parse will still be there in 3 years or their features and pricing will change.Never rely on a BAAS on the long run.
Yes parse has standalone login features with username, and password, in addition to twitter, and facebook. They even handle lost password reset's via email as long as the user has the email field entered. You can check if the user's email has been verified via the emailVerified field.
I'm using stripe.com's payment system via parse's cloud code. I will admit this is not a complete drop in feature for parse yet, but maybe in the future. stripe is made for developers, and I find it to be a very powerful payment system. I can answer some basic stripe/parse questions as I have written myself basically a semi-complete API for handling customers, card, and charges.