Skip to main content

Stage plot is erased after account creation

Thanks for providing a free version of the Ridermaker service. I created a stage plot, then created an account and was surprised to see that my stage plot was erased. You may want to handle this case, or at least tell the user that his work will be erased after creating the account.

3 comments

Log in to comment and vote

Comments3

  • mcidesarrollo

    Team•

    Sep 7, 2025

    Hello Boris, just to clarify:

    Ridermaker already uses the modern Web Storage API (localStorage) for temporarily saving a stage plot before you create an account. If you have technical knowledge you can check it in your browser's inspector (in our previous answer we named it as browser cookies so that it was more understandable if your profile was not technical).

    However, according to privacy regulations, we can only enable local storage if the user accepts the cookie banner — the law treats both cookies and localStorage as “local storage” that requires consent when used for functionality beyond what is strictly necessary.

    That’s why in your case the stage plot may have been lost: if cookies/local storage were not allowed, we weren’t able to keep it.

  • mcidesarrollo

    Team•

    Sep 7, 2025

    Hello Boris, thanks for reporting the issue.

    When the user doesn't have an account yet, the current stage plot is temporarily saved in the browser's cookies.

    When the user registers, this data continues to be stored in the browser until the user clicks "SAVE" to save the rider, at which point the data is also saved to their account.

    We've tested this behavior and it works correctly, so the stage plot and channel list items shouldn't disappear.

    There is only one case in which the items could disappear: if the user didn't accept saving cookies in the browser when prompted in the cookie banner. We recommend always enabling cookies in Ridermaker to get all the benefits the tool offers.

    If you've already rejected cookies in the banner, you can accept them by visiting https://ridermaker.com/privacy and activating the "Cookies enabled" checkbox at the bottom of the page, as you can see in the screenshot.

    • Boris Burtin

      •

      Sep 7, 2025

      Thanks for looking into this. I’m skeptical that an end user will read the text in the screenshot and will understand that it’s related to saving the temporary rider. You may consider using the Web Storage API for storing local data in the browser. We used cookies to manage local state in the 20th century, but they’re a bit clunky and more likely to be affected by edge cases like this one.