• Sethayy@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    13
    arrow-down
    2
    ·
    10 months ago

    Pretty much any webhosted service out there essentially needs to track ip’s (unless they want to be ddos’d), so even the server thats serving the pdf can and will track you

    They could even go the easy route and use something like bit.my to do it for them too

    • frezik@midwest.social
      link
      fedilink
      English
      arrow-up
      6
      ·
      10 months ago

      If you’re on their WiFi, then they’re just getting the restaurant’s IP. If you’re on mobile data, then they’re getting your carrier IP, which is often inside layers of carrier-grade NAT. Either way, they don’t get much besides knowing you’re attached to a specific carrier.

      • Sethayy@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        3
        ·
        edit-2
        10 months ago

        Even then it usually goes through the device’s browser and fingerprints as hard as some JavaScript virtually can, but I figured that was a bit long for the original post

        (I mean shit your device probably tells google itself where its going, much less the connections on the other end)

        edit: and of course this isn’t just the restaurant collecting it cause why would they care, usually its a shady 3rd party that already has a massive profile on you they can cross-reference

    • DrM@feddit.de
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      1
      ·
      10 months ago

      Yeah, but want I want to say with this: the restaurant gets nothing out of providing the menu only as a PDF. It’s stupid, just give me the OPTION to use a paper card, even though I prefer the PDF