Privacy policy problem?
13

I'm experiencing a privacy policy violation. The URL works fine, but even if I resubmit, the submission is rejected as invalid URL. https://www.happypointcard.com/page/customer/term.spc?no=2 If you try to submit a support ticket for this phenomenon, you will receive a submission error. How do I fix this?

박진수
Gefragt vor etwa 9 Monaten
Jeremy

Getting the same thing here. There is no issue on my end when trying to curl the URL, but everytime I try to resubmit it, it gives an error. I've tried invalidating the URL with the sharing debugger, but that didn't help.

29. Januar um 17:37
Darvin

Getting same issue here. Unable to resubmit the url or even after change the url.

29. Januar um 19:15
Timothy

I have the same problem as well.

29. Januar um 23:09
Vibin

+1. Same issue here since today

29. Januar um 23:21
黃梓榆

+1. I also have same issue

29. Januar um 23:27
Knorish

faced same issue, resolve with a workaround, check my answer below.

29. Januar um 23:28
Timothy

OP, were you able to fix the issue?

31. Januar um 21:27
Erik

Same issue here. URL has worked fine for years. No changes. Static HTML on S3 + CloudFront. Suddely is rejected

31. Januar um 22:35
Ausgewählte Antwort
1

In our case, this alert got fixed after we updated our robots.txt file to Allow: the privacy policy URL path

2. Februar um 05:45
Vibin
1

I noticed that Facebook has resolved the issue. Therefore, I replaced the Google Docs link with the original one we had before.

5. Februar um 02:14
Knorish
1

So I use angular for my webpages, FB and google seem to be using crawlers and do not like any pages that have things like modules and components. I had to create a plain HTML page with no js etc. For angular I had to include the file in my assets file and in my assets block of the angular.json file. I was then able to access my webpage URL/assets/privacypolicy.html

17. Juni um 11:26
Ryan
2

We have the same issue, it randomly popped up a couple of days ago.

31. Januar um 01:10
Mihai
2

Platform Term 4.f will be processed using a CDN server rather than a web server.

31. Januar um 18:23
조재현
Knorish

What do you mean by it? Are you suggesting that we need to serve policies from CDN? How did you come to know about this?

31. Januar um 20:49
조재현

We also had the same issue, so we tried many things, but when we used the Amazon cdn server, it was fixed and it is now normal.

31. Januar um 21:44
2

After the weekend it was resolved. This is probably a Facebook bug.

5. Februar um 00:58
박진수
Timothy

Same for me

5. Februar um 01:26
4

Has anyone found it to be working or not?

30. Januar um 20:37
Knorish
5

+1, We're having the same issue here, we opened a post about it too: https://developers.facebook.com/community/threads/3635861516682827/

30. Januar um 07:19
Gaudium
6

Getting the same too, curl the URl is ok (200) but when submitted I get "URL not valid".

29. Januar um 21:01
Jh
Gerard

+1. Same issue here since today

30. Januar um 01:40
Gaudium

+1, We're having the same issue here, we opened a post about it too: https://developers.facebook.com/community/threads/3635861516682827/

30. Januar um 07:14
6

Same issue maybe someone must open a bug report

30. Januar um 04:19
George
Gaudium

Unfortunately, we are unable to open new bug reports because Facebook has apparently disabled all the options available for opening new support reports. Currently, the only way we can talk about the problem is here in the Community Forum.

30. Januar um 07:17
黃梓榆

https://developers.facebook.com/support/bugs/create/

31. Januar um 00:26
Erik

Link exists but you cannot open any support request there. They simply say "sorry no support available"

31. Januar um 22:34
7

Same issue. I attempted to address it by testing various random URLs, but none of them appear to be working.

29. Januar um 23:03
Knorish
Knorish

As a workaround, I created a Google Drive with the exact same privacy policy content, made it publicly accessible, and used that link. It is currently working.

I checked on YouTube video id 5IORElzRLDQ, he mentioned its allowed, can't validate his suggestion.

Please suggest if you have any permanent solution.

29. Januar um 23:27
박진수

Even if it works, it still violates 4.f terms.

30. Januar um 01:35
Knorish

i just referred again 4.f. terms, that's not an issue if we use google doc as a temporary solution. https://developers.facebook.com/terms/dfc_platform_terms/#privacypolicy

30. Januar um 01:48
Timothy

Out of desperation (as the violation due date was in 2 days), I copied my privacy policy content into a Google doc, and used the published link to submit as my privacy policy to Facebook. The app dashboard reported an error, but when I refreshed the page the violation was gone.

So this does work, but probably not for the right reasons. Sharing my experience so you can decide ultimately what you wish to do.

30. Januar um 21:09
Knorish

I noticed that Facebook has resolved the issue. Therefore, I replaced the Google Docs link with the original one we had before.

5. Februar um 02:14