You may have made things prettier, but all of my criticisms still apply. You've also regressed in new and interesting ways. I'll start with the legal liability you've introduced.
Quote:
Q: Is it secure?
A: We are more than sure.
This is dangerous. I really, really doubt you know enough about security to even answer that question, much less implement the necessary security. You could actually get sued over these statements if you're claiming you're secure when in fact you aren't and don't even know how to become secure.
Have you hardened against XSS attacks? Man in the middle attacks? Verified non-repudiation of your login system (of course not, I checked myself and it is not compliant with non-repudiation principles)? Verified there are no SQL injection exploits that could dump your consumer database? Verified that your back-end install has been secured (they're rarely secure out of the box, a necessity for proper configuration).
Your site is running on PHP, which is nearly inherently insecure (something like 40% of all web vulnerabilities are PHP related). Have you familiarized yourself with PHP development best practices and security exploits? Have you brushed up on application security in
any way? Things aren't secure just because you want them to be or because you're using somebody else's code (that actually tends to make you much less secure, because you can't control the risk). Security is a hard problem, and you don't seem to be taking it seriously.
Next, usability.
1. Your captcha is a joke. I could write a piece of software to defeat your captcha in under 90 seconds. Seriously, 90 seconds. 20 lines of Java could pull the HTML from your reg form, parse it with a simple regex ("(\d+) \+ (\d+)" would do it) then I'm done. I can now automate registrations on your webpage, and I'm sorely tempted to do so to stress test your system.
Parsing text is easy, unless you're using an image, the only thing your captcha does is irritate your users. Whoever you got to program your site (I suspect you did it yourself) is just as untalented as I expected them to be.
2. Your registration form doesn't validate any data at all. It also looks like you didn't set your database tables up correctly (you should be getting unique key constraint violations on insert). My guess is you've got a ton of garbage data in there now from all the times I registered without a name, password, username
or filling in the captcha. That or your programmer was so bad he decided to show the success message without checking for failure, which doesn't bode well for the whole "security" thing we talked about before.
Also, if he's not even checking for success, there's no way in hell he's sanitizing inputs. This is serious amateur hour stuff. Nobody with any actual skill would assume success of a registration form, and nobody who had an inkling of an idea about security wouldn't use addition of two numbers displayed in plaintext as a captcha.
2. No password strength requirements, not even minimum length. Very insecure.
3. You claim to be much faster than major mail servers because you don't have any users yet. Hate to break it to you, but even without users you're still slower. This is because the big boys are running on major server hardware and have lower latency. You're not going to beat them here.
4. Your login failed notification is literally the worst I've seen. After several seconds a transparent pink box opens against a complex black and white background? My eyes, they hurt.
5. I can register accounts multiple times (though at least it doesn't successfully register new passwords for the account). You even get the welcome message multiple times. Serious security problem.
6. You block images in your own welcome email. That email backend you installed is pretty bad if it's flagging its own internal emails like that.
7. Your mail software is pretty barebones. I recommend you do a side by side comparison of your software and Gmail to understand what it is you're asking potential customers to give up.
8. The "Follow Us" links in the welcome email aren't links, but static pictures. Going to drop your conversion rate to effectively zero.
9. Why can I unsubscribe from a one-time email?
10. No ability to view email headers? Well, I hope your back end is good at checking for spoofed addresses, otherwise this is yet another security issue because your users won't be able to verify that an email was sent from who it claims to be from.
11. Terms and conditions aren't displayed, or even mentioned when signing up. That means anyone who signs up isn't bound by them. It's like walking into a bank and being informed upon entry that you've just taken a new boat loan. Even the EULA on games and other software must be mentioned on the box, and of course the user has to be shown the document (or at the very least, be told to look at it) when installing.
12. Your terms are incredibly overbroad, going so far as to claim anyone who registers has an obligation to police anyone else using your site on the same network. You also assert ownership of all intellectual property of everything on your site ("We are the owner or the licensee of all intellectual property rights in our service/site, and in the material published on it.") Might want to look up what happens when web services try to assert ownership of the IP users put on their site. That or amend your terms so you aren't asserting ownership of everything on the site.
13. "Any of the material on our site may be out of date at any given time, and we under no obligation to update such material." Translation: "I have no legal obligation to make good faith efforts to make sure legal documents are up to date." You do, actually. You can't change laws with contracts, especially contracts you never asked your users to agree to in the first place.
14. "We process information about you in accordance with our privacy policy." You don't even
have a privacy policy.
15. As a 12 year old kid, you shouldn't be trying to write legal documents. Really. Lawyers spend a lot of time at very expensive schools to become competent at these things. You haven't even started high school yet. You are laughably unqualified to be writing a TOS or EULA.
Really, it's nice that you were able to get through the installation of a some PHP code on a web server. That's not exactly easy, but it's not even in the same zip code as hard, either. It falls more into the category of "time consuming" rather than difficult.
You still haven't figured out how you get from A to B. How do you get from "barely functional prototype using off the shelf software" to "dethrone Google"? This is not rhetorical, I really want you to think about this. Because if you can't see it, then you can't do it, and if you can't do it, then your time would be better spent figuring out
what to do instead of just doing and asserting that what you're doing is right.
All the things you set out to do better than Google you seem to be doing worse (just like I said you would). The only thing you lead in is ads, but that's a problem I solved many years ago with a simple ad blocker.
If you want to learn to program, great. But this isn't the way to do it. You aren't really teaching yourself much, you're just making countless mistakes and refusing to acknowledge them. This in turn builds very bad programming practices, and is actually detrimental.
If you stopped and did things the right way, things would be different. Instead of learning about security, you merely state that you're secure. Instead of learning how to make good forms, you built a registration form that barely works at all. Instead of learning how email worked, you installed an off the shelf module.
In your mad dash to get to the finish, you've assured your failure and passed by every opportunity for learning and growth without so much as slowing down.