A del­i­cate bal­ance is required for mar­keters who wish to pro­vide per­son­al­ized and engag­ing mobile app expe­ri­ences while at the same time pro­tect­ing user privacy.

Build­ing a great cus­tomer expe­ri­ence is crit­i­cal to your busi­ness. But nav­i­gat­ing COPPA com­pli­ance, appro­pri­ately han­dling sen­si­tive loca­tion data, main­tain­ing a cus­tomer friendly approach to in-app, and push mes­sag­ing, while at the same time prop­erly com­ply­ing with OS devel­oper guide­lines (in your own code as well as in Ven­dor SDKs included in your app) also requires atten­tion and peri­odic review.  App teams that fail to appro­pri­ately address these issues may face last-minute code changes to remove non­com­pli­ant SDKs, app store rejec­tion, and legal action.

To help nav­i­gate these issues, Adobe recently pub­lished a whitepa­per pro­vid­ing guide­lines around pri­vacy for mobile apps. The guide, spon­sored by Vinay Goel, pri­vacy prod­uct man­ager at Adobe, may be found here: Mobile App Pri­vacy Cus­tomer Imple­men­ta­tion Guide. The primer includes clear guide­lines for han­dling pri­vacy in mobile apps. If you haven’t assessed your app against these or sim­i­lar guide­lines recently, I rec­om­mend you take time now to per­form a review of your app code includ­ing ven­dor SDKs.

Ques­tions? Com­ment on this post or ask your account man­ager to coor­di­nate a deeper dis­cus­sion around pri­vacy with our app team.