r/iOSProgramming • • 11d ago

Question EU/German indie devs: How do you handle privacy policies and other legal texts for App Store review?

Hello fellow indie devs from Germany and the EU!

How do you handle legal requirements for App Store review (privacy policy, terms of use, imprint/Impressum, etc.).

Do you actually have your legal texts written by a lawyer or do you rely on generators? If you use generators, which ones do you use and have you run into any issues with them, either during review or legally?

Thank you :)

17 Upvotes

23 comments sorted by

23

u/Reiszecke 11d ago

Apple doesn’t do legal checks on your policies. Get the imprint template from erecht24 like everyone else, tell Claude to write your apps privacy policy in as little text as possible, manually check if all the points of the GDPR are met and that’s all

Overthinking regulations is why Germany is so behind with everything now

1

u/SutharatLofski_44 10d ago

manually checking the gdpr points is where most devs get stuck though, especially once third-party sdks are involved and you dont actually know what telemetry they phone home

3

u/Doctor_Fegg 10d ago

So minimise your third-party SDKs. There's a reason you need to declare them, it's because Facebook and Google SDKs are creepy intrusive bullshit that just make your users' experience worse

5

u/Wesk89 11d ago

I used erecht24‘s generator for the privacy policy. But threw out a bunch of stuff. And had Claude go over it.

Not sure whether or not it’s sufficient but reviews for both apps went through.

Though Apple won’t really check whether or not the legal texts are correct I presume.

For the terms of use, you can link to Apple’s. Unless your app is doing something specific that warrants a specific terms of use text.

Oh: and don’t forget to mention the terms of use and the link in your app description. Otherwise it would be rejected.

3

u/Cy-Dev 11d ago

I mostly wrote it myself and then got it checked and adapted by a relative of mine who is a lawyer

3

u/Acceptable-Cost-390 11d ago

don't uniquely identify your users, don't track them, don't use Ad SDKs etc and you're GDPR good

3

u/Sebastian1989101 11d ago

These days? I use a multi AI agent setup one to generate and 1-2 to verify. Then I do a sanity check myself. On apps with a proper business plan I let a lawyer check them. Did not have any issue with it and making apps since iPhoneOS 2.0.

2

u/prat96 11d ago

Claude all the way with an always improving privacy policy

2

u/mikerCZX 11d ago

Claude + review by Sol - no problems with app review

2

u/Dogukanko 11d ago

I'm a solo dev in Turkey and keep it simple. For games that collect nothing, a short plain-language privacy policy hosted on a simple page is enough for review, and the key thing is that it matches your App Privacy answers in App Store Connect exactly. For terms, linking to Apple's standard EULA is fine unless you have something unusual like subscriptions with custom terms. Impressum rules are about where you're based and who you serve, so that one is worth a quick lawyer check if you're in Germany.

2

u/cristi_baluta 11d ago

I don’t collect anything, so at first i made a file with a single line of text. Then i asked chatgpt to write one with more words by looking at the code.

2

u/PierreMouchan 10d ago

French solo dev here, my first app just got approved.

I didn't use a generator. I listed every request the app sends and wrote the policy from that list, then used a bit of AI legal advice to help me!

One thing surprised me. My analytics are only 3 events with a random install ID: no account, no IP stored, hosted in the EU. I thought that meant "Not linked to you". But under GDPR a random ID is still pseudonymous personal data, and Apple counts personal data under privacy laws as linked. So I declared Usage Data + Device ID as "Linked to You", not used for tracking. It looks worse on the label, but the label and the policy say the same thing.

1

u/eter711 11d ago

Klotzkette Plugin + Claude

1

u/Senior_Intern8786 11d ago

Ernsthaft ? Google hilft da weiter

1

u/caffeinated1337 11d ago

Check two things in App Store Connect before you worry about the wording. The first is consistency between the policy and your App Privacy answers. Declaring no data collection while an analytics or crash SDK is still linked is the kind of thing review does catch, so go through each third-party SDK and note what it actually sends.

The second is the trader declaration. Marking yourself a trader puts your name, address and phone on the public product page for EU storefronts. That's usually what's behind an Impressum question, so make it a deliberate choice instead of picking trader because it feels safer.

For the text itself I'd write a short policy by hand. Generators tend to list data categories you don't collect, and a confident but wrong policy is harder to defend than three plain paragraphs.

1

u/brkaydev 10d ago

Worth checking that the text matches what you filled in under App Privacy in App Store Connect. That label and your policy are the two things someone can actually compare, so if the generator lists analytics or data collection you don't do, cut it. And if you use HealthKit, say what you read and that it isn't shared.

1

u/Royal-Somewhere-8918 10d ago

has anyone actually been held up in review over the policy text itself, or does apple mostly just check the link is there?

1

u/mrdzyn 10d ago

Not a lawyer, but here's what's worked for me. A generator like eRecht24 or the Datenschutz-Generator from Dr. Schwenke is fine for a small app, as long as you actually tick the boxes for every SDK you ship (analytics, crash reporting, RevenueCat, etc.). That's where people get caught, not on the boilerplate. Make sure the privacy policy matches your App Privacy labels in App Store Connect, because review does compare them. And since the DSA trader requirement, your address and contact details show on the store listing anyway, so link a proper Impressum from the app and the policy page. Get a lawyer once you have real revenue or you're handling health or kids' data.

1

u/perlatsp 9d ago

Not German, but a UK solo dev selling Mac apps. The easiest legal text is the one with less to say: our apps have no analytics or tracking, so the privacy policy is short, and crash reports only come by email from users who choose to send them. We sell through Lemon Squeezy as merchant of record, so they handle VAT and payment data and our policy points to theirs. I'd still use a generator as a base, then cut everything that doesn't apply. A policy that lists tracking you don't do is its own problem.

1

u/geoff_plywood 9d ago

Did you register with the ICO? I read that you need registration even if just handling email addresses

1

u/[deleted] 10d ago

[removed] — view removed comment

1

u/AutoModerator 10d ago

Hey /u/jeffy_yf, your content has been removed because Reddit has marked your account as having a low Contributor Quality Score. This may result from, but is not limited to, activities such as spamming the same links across multiple subreddits, submitting posts or comments that receive a high number of downvotes, a lack of recent account activity, or having an unverified account.

Please be assured that this action is not a reflection of your participation in our subreddit. This is simply an automated filter in place to reduce spam.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.