Skip to content
  • Daniel Gultsch's avatar
    2cb21bcb
    use static (not translated) text for Privacy policy and TOS · 2cb21bcb
    Daniel Gultsch authored
    For a long time Quicksy had a privacy policy written by myself that explains
    in plain English what data we store and how we use it.
    https://quicksy.im/#privacy
    
    Google doesn’t like that and prefers that we use some bullshit template that
    is extremely vague, doesn’t explain anything and gives us permission to do
    basically everything. (At least I think so. I don’t understand the text I
    copy pasted)
    
    Apparantly the text in the app is important as well (BARD didn’t explain
    that very well when it reviewed our app) therfor we need a static text (not
    allow translations)
    
    Furthermore the data safety section on Google Play now claims we store the
    users address book even though we don’t actually. But who cares; nobody reads
    this and we just do this to make the machine happy. Cool!
    2cb21bcb
    use static (not translated) text for Privacy policy and TOS
    Daniel Gultsch authored
    For a long time Quicksy had a privacy policy written by myself that explains
    in plain English what data we store and how we use it.
    https://quicksy.im/#privacy
    
    Google doesn’t like that and prefers that we use some bullshit template that
    is extremely vague, doesn’t explain anything and gives us permission to do
    basically everything. (At least I think so. I don’t understand the text I
    copy pasted)
    
    Apparantly the text in the app is important as well (BARD didn’t explain
    that very well when it reviewed our app) therfor we need a static text (not
    allow translations)
    
    Furthermore the data safety section on Google Play now claims we store the
    users address book even though we don’t actually. But who cares; nobody reads
    this and we just do this to make the machine happy. Cool!
Loading