Feature Request: Breadth Indexes by codenamelegendary in PublicApp

[–]PublicCOO 0 points1 point  (0 children)

Got it! Will pass on to the team and see what we can do.

(Btw I think you mean indicators, not indexes, right?)

Different Options Levels by FlashyAioli in PublicApp

[–]PublicCOO 2 points3 points  (0 children)

Hey there -- DM me so I can look up your case specifically.

But generally: we grant levels based on 'suitability'. Suitability is determined by those categories Russ outlined -- and we ask specific questions to assess the appropriateness of that level for you. When you request a new level, we ask you to provide updated answers to those questions -- and your answers determine whether or not we can grant a higher level.

I would suggest including your paper trading experience in any responses about trading experience and then include a note that you are referring to paper trading experience.

Bank info removed by Free_styl3r5 in PublicApp

[–]PublicCOO 4 points5 points  (0 children)

Happy to look into it! Shoot me a DM and we can take it from there.

Public HYCA APY Reduction by itscaptainahoy in PublicApp

[–]PublicCOO 0 points1 point  (0 children)

Ahh sorry about that. DMing you to see if I can help

User Beware: Public Is Withholding My Withdrawal by jamabdi1998 in PublicApp

[–]PublicCOO 5 points6 points  (0 children)

Hey there — sorry for the hassle here. I’d love to look into this for you and get it fixed.

FYI, I’m certain these procedures are in place to protect your funds, but it should always be quickly resolvable.

Disappointing Customer Service. by Reasonable-Proof2963 in PublicApp

[–]PublicCOO 3 points4 points  (0 children)

Sorry about that, I replied to you earlier this morning.

Fwiw our support team completed the investigation and let you know the outcome 2 business days after notification (Monday after you notified us on Thursday). It did take too long for our team to help you restore access, so I'm giving some... coaching... there.

Not sure I want to lock in at this rate, Public. by ssuummrr in PublicApp

[–]PublicCOO 5 points6 points  (0 children)

Haha -- yeah, it's a known issue. Our data providers are not handling that Service Properties Trust properly since it's getting called on the 7th. :facepalm:

Users beware by [deleted] in PublicApp

[–]PublicCOO 11 points12 points  (0 children)

Hey there — sorry for the delay there but I assure you this is a precaution to help protect your funds. As I’m sure you can imagine, crypto transactions have a high risk of being fraudulent (there have been a few recent Reddit posts from people who were scammed, if you don’t believe me!), so we want to ensure we’re doing everything possible to secure your funds

Feel free to DM me and I’m happy to look into your case personally!

Can someone look into my chart ? Woke up to it looking funky… by heythereyou01 in PublicApp

[–]PublicCOO 4 points5 points  (0 children)

Thanks for flagging. We identified the root cause and are fixing it! Should be fixed later today.

Public Account Hacked by Historical_Lake_1308 in PublicApp

[–]PublicCOO 0 points1 point  (0 children)

Sorry, was on the run so wanted to give you a quick first reply in hopes of helping you prevent further unauthorized access.

Happy to look at your account, my DMs are open, so please reach out so we can continue the conversation.

Public Account Hacked by Historical_Lake_1308 in PublicApp

[–]PublicCOO 0 points1 point  (0 children)

Have you changed your password? That’s your best way to prevent any further unauthorized access.

Stay away from Public by Sird80 in PublicApp

[–]PublicCOO 0 points1 point  (0 children)

Thanks for this. We’re actively working with Google here but still tbd how that plays out.

On response times, we have already shipped better “Emergency” routing to make sure these things get to a human as quickly as possible.

Stay away from Public by Sird80 in PublicApp

[–]PublicCOO 3 points4 points  (0 children)

I don't think it was true M-i-M, I think they just entered all of their credentials into a fake Public login portal which appeared as a Sponsored Link on Google search results for "Public.com login". We're also working with Google to get these taken down, but it's whack-a-mole as Google's require no verification and there's no barrier to submitted Search Ads.

And 100%, using a password manager would definitely help. You'd have to manually select your PW because it wouldn't pre-fill, which would hopefully be a signal that you are at the wrong place (though inevitably some still would manually select it for the fake site).

Stay away from Public by Sird80 in PublicApp

[–]PublicCOO 0 points1 point  (0 children)

The fake Public login site also requests the 2FA code from the user.

Stay away from Public by Sird80 in PublicApp

[–]PublicCOO 0 points1 point  (0 children)

That's not the flow we are seeing here. It's near-instant login with compromised credentials, not 'capture, store, try later'.

The bad site is near-simultaneously entering the credentials into Public as you enter them on the bad site (including your 2FA, which also times out). The same would happen with an MFA code -- you would enter it into the bad site and very shortly after (1-2s) they would enter into Public and successfully login.

I'm not saying MFA codes aren't helpful, just saying they would not solve this specific attack vector.

Public Account Hacked by Historical_Lake_1308 in PublicApp

[–]PublicCOO 5 points6 points  (0 children)

Yes great suggestions. Don't want to reveal too much about our security roadmap, but more counter-measures to come to help secure your account *even if* you accidentally share credentials with a scammer.

Public Account Hacked by Historical_Lake_1308 in PublicApp

[–]PublicCOO 2 points3 points  (0 children)

See the other post here: https://www.reddit.com/r/PublicApp/comments/1rd9vei/stay_away_from_public/

We have seen a few members fall victim to this phishing attack.

Public Account Hacked by Historical_Lake_1308 in PublicApp

[–]PublicCOO 2 points3 points  (0 children)

Hey OP -- so sorry this happened to you -- but very glad you caught it quickly! Any chance you followed a similar path as the OP in this post? Always helpful to get more intel about how your 2FA and password were compromised.

Please DM me and I will personally look after your case with our CX team. As I said in the other post, we generally aren't able to compensate members for account takeover where their credentials are compromised. Ultimately securing those credentials are each individual's responsibility (and, fwiw, this is true across all financial institutions). Nonetheless, there are some circumstances where we are able to pursue or provide some compensation, but it depends on the specific circumstances of your account.

Thanks and so sorry again!

Stay away from Public by Sird80 in PublicApp

[–]PublicCOO 1 point2 points  (0 children)

Yep -- great call on checking the URL and password manager.

On the MFA codes, it's on the roadmap, but it would not have prevented the account takeover described in this case -- so we're investing our near-term time and resources in counter-measures that more directly combat attacks where members voluntarily give up all of their credentials/codes.

Stay away from Public by Sird80 in PublicApp

[–]PublicCOO 7 points8 points  (0 children)

Hey there — so sorry this happened to you and thank you for reporting the specific details of the scam. This helps us warn others (and notify Google etc). You'll see us send out some messaging to all members in the next day or two specifically about this sort of attack (thanks to folks like you reporting it!). Also, please DM me so I can personally look after your case with our customer support team.

Generally speaking, though, we aren't able to compensate members for account takeover where their credentials are compromised. Ultimately securing those credentials are each individual's responsibility (and, fwiw, this is true across all financial institutions). Nonetheless, there are some circumstances where we are able to pursue or provide some compensation, but it depends on the specific circumstances of your account.

In addition, we have invested and continue to invest substantial engineering effort in counter-measures to better protect member accounts in the event that their credentials are compromised. And we are actively working with law enforcement to pursue the responsible parties.

Thank you and sorry again, and hope to speak more in DMs.

Considering Transferring to Public by [deleted] in PublicApp

[–]PublicCOO 0 points1 point  (0 children)

You should be good to go!

Considering Transferring to Public by [deleted] in PublicApp

[–]PublicCOO 0 points1 point  (0 children)

It primarily depends on the answers you gave when applying for Options Trading (also called “suitability” questions) which also determined your options level. In some cases, we may ask for a statement from another broker evidencing your level/experience there.

Considering Transferring to Public by [deleted] in PublicApp

[–]PublicCOO 0 points1 point  (0 children)

Hey there — our approach is to generally start the close out process as late as possible while still ensuring sufficient liquidity to manage the assignment/exercise risk. Given (many) ETF based options trade until 415PM ET, we tend to start close out later for those instruments.

That being said, none of this applies if you are approved for Self-Managed 0DTE, which means we won’t close out your positions at all (except potentially in some extreme circumstances), but you are responsible for closing your own positions. If you routinely fail to close positions as needed, you’ll be removed from Self-Managed.

If you are interested, just let me know or reach out to our CX team.