LinkedIn
Twitter
I recently created a new project (website) using Firebase auth and Firestore.
My project had 5 pages in total... (visual screenshots at bottom of post)
Signup: This page included the following text forms to register a user with additional data that is required for my project (see below).
- First Name (stored in a new database entry for the user)
- Last Name (stored in a new database entry for the user)
- uDisc ID (stored in a new database entry for the user)
- Email (sent to Firebase Auth & stored in a new database entry for the user)
- Password (sent to Firebase Auth, not stored inside the database for obvious reasons)
Note: uDisc is a separate website/app not owned by myself. They display their leaderboard data via an html link for users to see their scores after a round. Since uDisc does not have any public API's I scrape the data using cheerio and save it to my database. The uDisc ID is required to match a users score from uDisc to make sure I save the correct scores to the same user in my database
Signin: This page only included 2 text forms that used Firebase auth to authenticate their login session.
- Email
- Password
Home (index.html): This page currently has a top navigation bar listing our socials, pages, and website logo and nothing in the body of the page (empty).
Events (events.html): This page had our clubs recurring event information displayed (ie: where, when, etc).
Leaderboards (leaderboards.html): This page like the home page, only had the top navigation bar and an empty body.
Somehow, google decided I was "phishing". After doing some digging it seems that firebase could have been the reason (due to some of their public API's not being secure?). After creating a ticket of appeal I get the same copy and pasted automated BS response saying they found phishing content and too remove it but will not define what on my site was considered phishing. Does anyone have an idea what they could be referring to?
