security

security

How ogbase keeps accounts, pages and payments safe. Last updated November 4, 2026.

the short version

ogbase is built so that each person can change only their own page, payments can’t be faked, and as little as possible is kept about anyone. What is kept, and why, is on the privacy page.

your account

  • Passwords are stored scrambled, so nobody at ogbase can read yours.
  • Sign-up and log-in allow 10 tries per connection every 15 minutes, and each person gets one account.
  • ogbase will never ask for your password by email or message. Anyone who does isn’t ogbase.
  • Use a long password you don’t use anywhere else, and log out on shared computers.

your data

  • The server decides who can see and change what, so the checks can’t be skipped by changing the website in a browser.
  • Private things, like your email, orders and support tickets, are only shown to you and ogbase’s admin.
  • The site’s code holds no secret keys, and every page sends strict security rules to your browser.
  • Everything travels over HTTPS. IP addresses are only stored scrambled, to stop spam.

payments

  • Card numbers, wallet keys and Cash App logins never reach ogbase.
  • Checkout happens on Backout’s own page. When a payment comes in, ogbase asks Backout directly whether it was paid before anything turns on.
  • Only that check can turn on a purchase. A repeated update changes nothing, and an underpaid one doesn’t turn anything on.

safe pages

  • A word filter keeps slurs and hate out of usernames, display names, bios, tags and guestbooks, in the site and in the database.
  • Every page has a report button, and the admin can remove pages and accounts. The terms say what pages can’t have.
  • Old and new names are recorded, to stop people pretending to be someone else.
  • ogbase is for people 18 and older.

how updates ship

Updates go out one file at a time. Each file is compared with the live copy before it’s uploaded, the code that handles usernames and payments has to pass its automatic checks, and every update is logged, so a change that causes a problem can be found and undone.

if something goes wrong

  1. Stop it: switch off the part that’s affected, remove a page, or roll the site back.
  2. Find out what happened, since when, and who it touched.
  3. Tell the people affected what happened and what’s being done, within 72 hours of knowing.
  4. Fix it, test the fix, and write down what changes so it doesn’t happen again.

report a problem

Found a security problem? Open a ticket on the support page or email [email protected]. A real bug report earns the Bug Hunter badge.

Please only test with your own account and page, and give ogbase a chance to fix a problem before telling others about it.