Privacy

— version 2026-10-31

  1. Who we are. rideskout, hello@rideskoutapp.com. Email us
  2. What we collect, and why.
    • Requests: the place, your pick-up location, your times and days, seats, price band, and how you travel now. Also the phone or email you give to manage the request (at least one). If you tick the box, we may message you on WhatsApp about it; we send no WhatsApp messages yet. For a school, you may add students' names. Only that school's verified organisation sees them, and it may ask for one name per seat. We use all this to count demand and to let you change or withdraw your request. We also email you when the school is verified.
    • "Tell me when it's live": if you add a place or an area and leave your email, we use it once: to tell you it is live. We delete it when it goes live or is turned down, and after 90 days at the latest.
    • Accounts (transporters, organisations, rideskout staff): your name and email, through Google sign-in, an email code or WhatsApp; when you ask for verification, your email reaches our team.
    • Signing in. We keep the email or WhatsApp number you sign in with, and the date. We use it only to sign you in. A sign-in code works for 10 minutes and is deleted a day later. We never send you WhatsApp messages. If you recover a request link by WhatsApp, we use the number you type for that day only.
    • Cookies: One cookie on pages you don't sign in to (rk_v), plus rk_theme if you switch between light and dark. Signing in adds the three cookies it needs — sessionid, csrftoken, rk_in. Recovering a link by WhatsApp adds the first two. Nothing that tracks you, ever.
    • Share codes: Links and QR codes we hand out carry a short code, so we can count which one brought a visit. It holds no personal data and sets no cookie.
    • Searches that find nothing: the words searched, the city and how often — never who searched.
    • "Ask for your city": the city, who you are and why (from short lists), the phone and/or email you give, your WhatsApp tick, and an optional note only our team reads. We use it to decide where to open next. We also email you when your city opens. It is deleted 12 months after your last change.
    • WhatsApp check. If you verify a number with WhatsApp, Meta passes us the message you send. We use it only to match the code, and to sign you in. We keep only the date the number was verified, and we never reply.
  3. Who sees it. Public pages show seat counts only, from the first seat ("61 seats needed"; once everyone is served, "30 seats served"), the price band most people chose (and the average, once 5 people ask), and area names with their own seat counts. Your contact details are never shown publicly or given to transporters. A school sees only its own families' requests, as the notice on its page says.
  4. Service providers. A hosting provider, an email delivery service, Google (place search and sign-in), and Meta (WhatsApp). They handle data only to run rideskout.
  5. How long we keep it. Requests are kept only as long as the rule shown where you make them. A withdrawn request is kept for 90 days and can be brought back, then deleted. Requests are deleted after a year without activity; a month before, we write to the email we sent your link to, so you can keep yours. Anonymous travel counts are kept after your details are deleted.
  6. School pickup registration. Full ID numbers (CNIC) are stored encrypted, kept while the school's record of your family lasts, then deleted with it. Only the last 5 digits of a CNIC are ever printed on a card or exported. A driver's full ID number and phone go only to their transporter, the schools they are assigned at, and the families they carry. Every time a family or school opens a full ID number, we log it.
  7. Your choices. Withdraw a request any time from its manage link. You can see, correct or delete your data. Email us about your data
  8. Changes. We may update this page. When we do, the version date above changes.