01 · WHAT IS HANDLED
Only the data needed to run your garage.
When you create an account, SureCars stores your username, display name, password hash, and any invite and family membership. An essential session cookie keeps you signed in; your browser stores a local light-or-dark theme preference. If you add a profile photo, SureCars keeps a 512 by 512 copy with its location and camera details removed. If you use Google and have no photo, SureCars copies your Google picture, unless you removed a photo earlier. People who share a family, trip or group with you can see your name and photo.
A mobile number you sign up or sign in with, or add to your account, is kept only as a keyed hash plus its last 3 digits, never in full. If someone invites you to a group or offers you a car by your number, SureCars keeps that number the same way, with the name they typed. A number you give to connect a car maker, tracker or watch account is different: it is part of that account’s encrypted sign-in details, so SureCars keeps it in full until that connection is removed or your account is deleted. SMS codes are kept only as keyed hashes and work for 5 minutes. Counts of codes sent, with a hashed number and a hashed IP address, are kept for 30 days to limit abuse and cost, and sign-in records (the method, app or website, and the time) for 180 days. If you use Google in the SureCars app, SureCars keeps your Google account ID and the email address Google has verified.
The SureCars app now does almost everything itself. When it does send you on to this website, that browser is signed in for one day. Signing out in the app does not sign that browser out; use Sign out on the website. On a phone, your sign-in is kept in the phone’s secure storage.
When you add a car connection, SureCars may handle manufacturer account details or access tokens, vehicle identifiers, battery or fuel state, range, odometer, charging and security state, warnings, timestamps, journey records and location supplied by the connected service. For Hyundai, Kia, BYD and MG, that includes your password for that maker’s account, encrypted, because SureCars has to sign in again by itself. For Mercedes-Benz, the password is discarded once SureCars holds an access token. For Tata, there is no password: SureCars keeps the access details from Tata’s SMS sign-in. All of this is kept until you remove that connection or delete your account. From these readings SureCars also keeps a timeline of each car: its drives, parking, locking, charging, fill-ups, alerts and gaps in contact, and any reading it found doubtful, for 400 days or until you remove that connection. People you share the car with see that timeline only as far as their share goes: no places without location, no drives or locks at Readings only, and nothing at Basic.
Places you save, including with Name this spot on the Map, belong to your account. People who can see your car’s location can see the name you saved for where it is, unless they saved their own name for that spot. A car photo you upload is re-encoded, which drops its location and camera details, and shows to anyone who can see that car, except at Basic. It goes when that connection is removed; there is no other way to remove it yet. Fuel purchases you enter stay private to you. For a receipt, SureCars keeps a fingerprint and not the picture.
Spotify is optional and uses a separate approval on Spotify, not your Spotify password. For that connection, SureCars handles your Spotify account identifier and reported plan, available player identifiers, names, types and capabilities, and current playback information. Saved Spotify tokens, account details and linked-player details are encrypted at rest. The short-lived playback cache is held in memory, not saved as a listening history.
A minimal media-command journal stores internal account references, request hashes, timestamps and result codes to prevent duplicate sends. Car-linked controls also retain an internal car reference. It does not store song titles or the Spotify access token.
02 · HOW IT IS USED
To provide the product—not to control the car.
Vehicle data is normalized into the garage, map, activity history, trip summaries and freshness indicators. SureCars may use recent records to recognize places, understand journey context and calculate owner-facing summaries. Suggestions of where a car is going use where that car has driven before, the time of day, and the saved places of the people riding in it. They lean towards the places each of those people goes to most; the Phone location section says what SureCars keeps for that. Cost figures are estimates, not bills. They use the rates you save or, for fuel on some cars, the public daily prices for Kolkata published by India’s Petroleum Planning and Analysis Cell, with the latest price standing in for up to 5 days, after which no cost shows. Reading those prices involves no personal data.
SureCars reads vehicle data and does not implement vehicle unlock, lock, start, stop, climate or charging commands. To read a car, SureCars sometimes asks the maker’s service for a fresh report, which on some cars can wake its connection for a moment. Separately, optional Spotify controls send the actions you select to your account’s current player shown on screen. Moving playback to another player requires your explicit selection and can interrupt playback elsewhere. A car assignment is not required.
Optional navigation requests send the destination name, coordinates and required address fields to the manufacturer for the selected car, only after the connection owner reviews and confirms. A navigation PIN, where required, is used for that request only and is not saved in the request record. Encrypted destination request records are retained for request status and duplicate prevention. A manufacturer acknowledgement is not evidence that the car received or displayed the destination.
03 · WHO CAN SEE IT
Access follows the owner’s choices.
The vehicle owner can see the full data available for their connection. The owner chooses, car by car, what each family, trip or group gets. New shares at Everything are offered only inside a family. Everything shows where the car is, its fuel or battery, its past and future journeys and monthly reports, and who’s in it if they chose to share. Basic shows where the car is now, its fuel or battery and range, and if it’s parked, driving or charging, not its journeys or who’s in it; inside a family it also shows if the car is locked. Readings only shows the car’s own readings, such as fuel or battery, range, odometer and lock, not where it is, its journeys or who’s in it. Outside a family, Basic hides where the car is near its home and saved places, and, until SureCars knows its home, within 25 km of where the share began. A trip’s sharing stops by itself after its last day. Older settings made on the website still work: a family member sees a connection’s location only when the owner enables family location sharing, and a guest share receives vehicle status without precise location, routes or occupant information.
SureCars does not publish vehicle data, location or journeys. Data may pass to the relevant manufacturer, tracker or watch service and to the infrastructure, mapping and picture services described below. It is not sold as a data product.
Connecting Spotify sends you to Spotify for approval and returns through a dedicated Cloudflare callback bridge. Requested media actions are sent to Spotify for the displayed current player or the player you explicitly select. This is a personal connection: sharing a car or joining a family or group does not grant music-control access. A player name, active status or selection is not proof that it is physically in a car or that you are travelling with it.
When an authorised user opens a map, their browser or the SureCars app requests map tiles from OpenStreetMap. OpenStreetMap receives the device’s IP address, the SureCars site origin from a browser, and the requested map-tile area, which can be your own area, because Map opens around where you are; SureCars does not send account credentials or a vehicle identifier with that request. Once SureCars has switched Google maps on, a map that shows a chosen destination, or the results of a destination search, gets its map tiles from Google instead: Google receives the same kind of ordinary tile requests, with the area of the map being viewed, under the Google Maps Terms of Service and the Google Privacy Policy.
When you search for a place, SureCars’ server sends the words you type to a place search service: Google Places, once SureCars has switched it on and only where the result is shown on Google’s map, and otherwise Photon, a search service built on OpenStreetMap data, which also answers when Google can’t. A place that a Calendar suggestion fills in goes the same way when you search. The app may also send the search service a rough area, to about a kilometre, so that nearby places come first. SureCars does not send your name, account, IP address or a vehicle identifier with a search. Google handles what it receives under the Google Privacy Policy.
SureCars runs on a server rented from Vultr, and everything sent between your phone or browser and SureCars passes through Cloudflare. To send a sign-in code, SureCars gives your number and the code to its SMS provider, Karix, and the text comes from the sender SureHomz. To name where a car is or where a journey ended, the server sends OpenStreetMap’s Nominatim that position, rounded to about 100 metres, with no name, account or vehicle identifier; the names that come back go into a shared list with no link to any account. While a car or tracker is heading to a destination, the server can send Google Routes its current position and the destination, so the time to arrive allows for traffic, with no name, account or vehicle identifier. When you plan a trip to a place in Charging stops on a Google map, the server can send Google the car’s position, rounded to about 100 metres, and that place, to work out the road and its traffic, and can ask Google for the charging stations along that road, with no name, account or vehicle identifier. Google handles this under the same policy. Road matching runs on SureCars’ own server. To show a picture of a car you add yourself, SureCars sends its maker and model, spelled as in SureCars’ own list of cars, with its year and colour, to an AI image service, which draws it. A maker or model that isn’t on that list is never sent, and nothing about you, your account, your number plate or where the car is goes with them. The same picture is then used for every car of that maker, model, year and colour. Google and Apple carry phone alerts, if you turn them on, as the Phone alerts section says.
Where offered, if you choose a WhatsApp sign-in code, SureCars sends your linked number and that one-time code to Picky Assist and WhatsApp for delivery. The code follows the same expiry and abuse limits as an SMS code. If you choose to share an invitation in WhatsApp, your device shares the invitation link and code with WhatsApp; you choose the recipient and whether to send it.
If you allow direct WhatsApp group invitations, SureCars sends your verified number and the invitation link to Picky Assist and WhatsApp only when a group admin explicitly sends you an invitation. The message does not contain your group’s name, a vehicle or a location. SureCars stores your choice and uses keyed phone hashes to limit sends. A group admin who sends you an invitation can see whether WhatsApp accepted it for sending. You can turn off these messages in Groups, under WhatsApp invitation preferences.
The person who runs SureCars can see the list of accounts, each car’s name and whether its connection is working, and can reach the server that holds this data, to keep the service running and to answer a data request. The key that unlocks encrypted data is on that server. To diagnose a problem, scripts on that server can read location rows, keeping only distances and times. No screen shows that person a child’s name or position.
Like most servers, SureCars’ server logs each request’s IP address and the page asked for, to keep the service running and secure. SureCars blanks the words and rough area of a place search out of that log; logs from before 5 November 2026 can still hold them. There is no fixed time limit on these logs yet. A child’s name and position are never part of a page address.
Your Notifications page is worked out from what SureCars already holds when you open it. SureCars keeps a short list of which items you last saw or chose to leave, so that the count is right on every phone, and for 7 days a note when someone removes you from a group or stops sharing a car with you.
OPTIONAL PHONE LOCATION
Your phone’s location is your own choice.
Recognise me in cars is off until you turn it on. You then choose which family members may see the result, and this phone sends SureCars its precise location, either only while the app is open or also while the phone is locked, as you choose and as the phone allows. Nothing starts automatically, and new family members are never added by themselves.
SureCars compares those readings with the positions of cars you, or the people you chose, may locate to work out which car you are likely in, or parked beside. The regular cars you choose help when more than one car fits, and beside a regular car SureCars can name you sooner as it pulls away, once your phone has moved with it. This is a likely match from GPS, not a fact. Your phone’s position is not shown to anyone as a map of people.
Only the people you chose, and only where they may already see that car’s location, see your name on it: riding in it, parked beside it or using it. They can also see it on that car’s journeys, for as long as that record lasts. Turning sharing off hides it.
SureCars keeps your phone’s readings encrypted and deletes them after 3 hours. The running server can also hold them in its memory for up to 36 hours, to work out a finished journey, until it restarts or you turn sharing off. Its record of which car you rode in holds no coordinates, is encrypted and lasts 36 hours. Turning sharing off, leaving a family or deleting your account deletes both at once. Signing out stops that phone and clears what it had waiting to send.
One more record helps SureCars suggest where a drive is going, and it lasts longer. While your sharing is on, when a car that isn’t yours, in which SureCars has matched you, ends a drive at one of your own saved places, SureCars notes which of your places it was and the day: not the time, not the car and no coordinates. It keeps each note for up to 90 days. Nobody is shown these notes, and only your own suggestions use them. Turning sharing off, changing who may see you or leaving a family stops them being used at once and deletes them within minutes. Deleting that saved place deletes its notes at once, and deleting your account deletes them all.
An administrator can also connect their own Home Assistant, whose people’s positions can be used for this matching. If you link your account to your person there, which you have to accept, that position is used only while your sharing is on and only if you allow it. Someone in that Home Assistant who has not linked an account can still be named as a likely passenger to the person who connected it, and to family members who see that car’s location through family location sharing, and while a car’s own position isn’t updating, their phone can stand in for it. Older journeys of such a car can hold those names.
Phone trip recording, on Android, is a separate choice for one car you pick. Its points are encrypted and kept for 30 days, and its summary for 120 days. It shows only to people who may see that car’s location.
CAR TRANSFER
A transfer changes SureCars only.
You can transfer a car in SureCars to someone in your family, or to someone else by their mobile number. Nothing changes until they accept. It does not change the car’s papers or your account with its maker, and SureCars doesn’t move your password, readings or journeys to anyone’s account.
To someone in a family or group you share: they become the car’s owner in SureCars, with its past journeys (including the names of who rode along), its settings and its shares. Readings keep coming through your maker account until they connect their own, and they never see your password. Each share of the car stays as it was in every group they are in; a share in a group they are not in stops, and the people who lose the car are told that you transferred it, not who to. You see it only as it stays shared with you. It is theirs for good: to have it back, they transfer it to you. It comes back to you only if they delete their account. You can’t remove that maker account here while it reads a car someone else owns. After a transfer inside your family, a tracker of yours in the car stays on it, as your tracker, for as long as you still see that car’s location; its new owner is told and can take it off. After any other transfer it comes off.
To someone else: you type their name and number. SureCars keeps the number as a keyed hash plus its last 3 digits, the name as you typed it, which only you see, and the one-use code only as a SHA-256 hash. SureCars doesn’t send anything: you send the message yourself. If their account doesn’t hold that number, they prove it by SMS, and the number isn’t added to their account.
When they accept, the car leaves your garage, you can’t take it back, and every share of it stops. They add it with their own maker account and start with no past journeys. They see your name and the car’s model, nothing else. Your past journeys with it stay on your account, where you can’t open them in this version, and go when you remove that maker account.
While the car stays on your maker account, SureCars goes on reading that account, so this car’s readings still reach the server. SureCars drops them and keeps no history of them, apart from read timing for MG and BYD.
If a car comes to you, SureCars can’t stop what happens outside it. Until the last person takes the car off their maker account, they can still see it in that maker’s own app, and a tracker they left in the car keeps showing them where it is in its own company’s app, even after you take it off the car in SureCars. Ask them to remove both.
Transfer notices last 30 days. A waiting offer lasts 7 days; its hash, last 3 digits, name and code hash go 30 days after it ends. The record of an accepted transfer to someone else, with the name you typed, stays until you remove that maker connection, even if they delete their account. The person who runs SureCars can undo a transfer made by mistake.
OPTIONAL TRACKERS AND WATCHES
Trackers and watches report through their own companies.
When you add a JioFind, Qubo Go or Ajjas GO account, SureCars signs in once with the password or SMS code you give it, keeps an encrypted session and your account’s details, not the password, and saves each tracker’s model, battery, last position and trips or points. If you put a tracker in a car, people who may see that car’s location can see its position there. You can also put your tracker on a car that someone in your family shares with you with its location: its owner is told at once, sees it as your tracker, without your tracker account’s details, and can take it off, and it comes off by itself when you no longer see that car’s location through your family. On a car shared with you through another group, its owner has to say yes first, and even then it is used only if the owner chooses it as that car’s position. Disconnect stops the reads and ends its car assignments, and saved readings stay. Remove takes the account and its saved readings out of SureCars. Neither touches your account with that company.
For a JioFind tracker you own, you can also restart it. On the website, and not in the app, you can ask it to record one clip of the sound around it, after confirming you have permission from the people within listening range. Jio makes and holds the clip. SureCars keeps the clip’s link and details encrypted, and a record of each request, and passes the audio to you when you download it, without saving it. Qubo Go and Ajjas GO get no commands.
Watch accounts are separate from cars. When you connect an imoo or Noise Explorer account, SureCars signs in once and keeps, encrypted, your username, a session with that company, and each watch’s ID and latest position, which it reads about once a minute. It keeps no password and no history of positions, and sends nothing to a watch. Only you can see it, unless you put it on a child’s profile, which the next section explains. Otherwise a watch isn’t linked to a car or a passenger, or shared with a family or group. Pause stops the reads. Disconnect also removes the session and the watches, and your encrypted username and label stay until you delete your SureCars account. Connect only a watch you wear yourself, or one worn by a child whose parent or lawful guardian you are. SureCars asks you to confirm that when you connect, before it shows where the watch is. Don’t connect a watch another adult wears.
CHILDREN
A child’s profile is run by their parent.
SureCars is for people 18 or older. A child, meaning anyone under 18, never has an account, never signs in and never uses the app. SureCars runs nothing on a child’s watch or phone and sends a watch no commands.
Only a child’s parent or lawful guardian can add them, on a screen that says what SureCars will do, and only after confirming that they are 18 or older, that they are the child’s parent or lawful guardian, and that they agree. SureCars relies on the mobile number or Google account verified on their account and can ask for more. It keeps a record of who agreed, when and to which words.
For a child, SureCars keeps the name or nickname you type, the month and year they were born, which watch is theirs, that watch’s latest position and a regular car if you choose one, encrypted. It doesn’t ask for their school, address, phone number or photo, and copies nothing else about them from the watch company.
SureCars uses this for one purpose: so the parent or guardian, and people they pick by name, can see where the child is now and which car they are likely in now, in the interest of the child’s safety. The car is a likely match from GPS, not a fact, and a position can be late or wrong.
A parent or guardian can also ask SureCars to tell them when their child arrives at or leaves one of their own saved places, such as a school. People they pick by name can’t. SureCars works this out on its server from the watch’s latest position and keeps it in memory only, never in its database, its logs or a backup: it shows in the parent’s Notifications for up to 12 hours and is gone when the server restarts. The phone alert names no child and no place.
SureCars doesn’t keep a history of where a child has been. A child doesn’t appear on a car’s past journeys, monthly reports or costs. A child’s data isn’t used for advertising, analytics or anything else, isn’t sold, and isn’t sent to place-name or traffic services. If you open a map of where your child is, OpenStreetMap receives the area of the map, as described above.
Only you and the people you pick by name can see a child. Sharing a car with a family, trip or group doesn’t share a child, and neither does joining a family. Someone who can see a car, but wasn’t picked, sees nothing about a child in it. A child doesn’t move with a car you transfer.
imoo and Noise are separate companies. They hold a child’s data under their own policies, which can include a history of positions and can be outside India. SureCars can’t change or delete that. Connecting can sign you out of the company’s own app. SureCars doesn’t replace that app, and doesn’t show its calls or alerts.
You can pause or remove a child at any time on their screen. Removing them deletes the profile and position at once, and disconnects a watch account of yours that only fed them. If another parent has also confirmed, a note naming the child stays for that parent for 7 days. Backup copies, which can hold the profile, are kept for about three months. SureCars keeps the record that you agreed for 1 year, and what the law makes it keep. Deleting your account does the same, unless another parent has also confirmed. The profile ends by itself at the start of the month the child turns 18. SureCars tells you 30 days before.
A parent or guardian can ask SureCars for a summary of what it holds about their child and who else received it, and can correct or erase it. Anyone who thinks a profile shouldn’t exist, including a child or another parent, can write to aryasumant@gmail.com. SureCars answers within 30 days. If you aren’t satisfied, you can complain to the Data Protection Board of India, once it accepts complaints.
PHONE ALERTS
Phone alerts say as little as they can.
If you turn on phone alerts, your phone gives SureCars a token that reaches that phone. SureCars keeps it, encrypted, with the kind of phone, the app’s version, whether this phone allows alerts and whether the last alert was accepted, until you turn alerts off, sign out, your sign-in ends or you delete your account.
To send an alert, SureCars gives that token and a short line to Google’s Firebase Cloud Messaging, for an Android phone, or to Apple Push Notification service, for an iPhone. Most lines say only what kind of thing it is, such as "You have a new family invitation.", and name no person, car, place or group. Two kinds name more, because that is what they are for: a fill-up or a finished charge names the car and where, and a place alert about a car names the car and the name of your own place, such as "Creta arrived at Home", never who was in it. Google and Apple can see that an alert went to that phone, and when. Their own policies apply.
A place alert about a person or a child says only that, such as "A place alert about a child.", with no name and no place, and no child’s name or data goes to Google or Apple for it. An alert about a child is sent once, and SureCars keeps no record that it was sent.
You can ask SureCars to tell you when a car whose position you can see, or a person who shares their live location with you, arrives at or leaves one of your own saved places. SureCars keeps your rules and whether each car or person is at each of those places now for as long as the rule lasts, and, for 7 days, when they arrived or left. When you add a person to one of these alerts, SureCars tells them on their Notifications page, and they can see who gets alerts about them and switch them off at any time. A place alert never shows anyone else the names of your places, and nobody is checked against another person’s place.
SureCars keeps a short record of which alerts it has sent, with no words in it, so that it doesn’t send one twice. That goes when the item goes. Alerts aren’t an emergency or safety service: one can be late or not come at all.
OPTIONAL GOOGLE DATA
Calendar suggestions and contact selection are your choice.
Google sign-in alone does not give SureCars access to Calendar or Contacts. Each optional connection requests separate read-only consent. Calendar asks for your Google account ID (openid) and read-only access to events on calendars you own (calendar.events.owned.readonly). Declining or disconnecting either connection does not remove your Google sign-in or vehicle access.
Calendar access reads the next 7 days of timed events in your primary Google calendar, including events Google has added from Gmail. Only event identity, title, location, start/end time, type, status and your own response status are used to make private destination suggestions. SureCars does not read your Gmail inbox, edit your calendar, guarantee flight information, or set a car destination automatically. SureCars saves your Google account ID and the encrypted permission, not your events. Suggestions last at most 5 minutes, in memory, and are not shared with other members of a car, family or group. If you pick a suggestion, its place fills the search box, unless it is over 60 characters. It goes no further until you search.
While you use the app or the website, a private in-car hint may combine an upcoming event with your existing, consented current co-travel evidence. It uses your authenticated account’s own match, never a person’s name, a vehicle’s primary-user label or car motion alone. Event places remain suggestions; uncertain flight airports are marked for you to check. Calendar details are not added to shared vehicle reports, group feeds or recorded trip history. Revoked or expired access and no-longer-current presence remove these hints.
When you choose Google Contacts for a website invitation, SureCars temporarily reads matching contact names and phone numbers. It does not import or retain an address book. You select one mobile number, confirm it and create the invitation using the existing controls. Contacts access lasts no longer than ten minutes and is bound to the web session that connected it. A phone app contact picker, where available, receives only the contact property you select rather than bulk address-book access.
Resource grants are encrypted at rest and bound to your SureCars account. Calendar permission may renew for up to 30 days; Contacts permission is not renewed in the background. Disconnecting locally removes the corresponding active grant immediately and stops future reads. You can also revoke Google permissions in your Google Account. Account deletion removes these resource grants. Neither Google Calendar nor Contacts information is sold, used for advertising, or provided to advertising networks.
SureCars’ use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
THIS PHONE’S CALENDAR
Your phone’s calendar is read on your phone.
If you choose to use this phone’s calendar, the SureCars app reads events that have a place in the next 7 days, from the calendars you choose, only while the app is open. It uses each event’s title, place and start and end times, and leaves out all-day, cancelled and declined events. It doesn’t read notes, looks at an event’s guest list only for your own reply, and doesn’t change your calendar. Suggestions in the destination search are made on your phone. To suggest where you’re driving, the app sends SureCars only the events that start within the next 6 hours; SureCars uses them for that one answer and doesn’t store them. Only you see these suggestions. To stop, turn it off in SureCars (You, then Calendar) or turn off calendar access for SureCars in your phone’s Settings.
04 · ADVERTISING
No advertising code is running today.
The current SureCars website and app do not load an advertising network or an analytics service, or create an advertising profile. If advertising is introduced later, this notice and the required consent controls will be updated before that change is enabled.
Vehicle location, journey history and manufacturer credentials will not be made available as advertising targeting data.
05 · RETENTION AND CHOICES
You can disconnect a car.
Vehicle history is retained to provide the dashboard and journey features for as long as the connection stays, subject to the service’s operating and backup policy. Detailed readings are thinned to one an hour after 120 days and to one a day after 400 days; journeys are kept. Removing a car connection stops future reads and deletes its saved data and journeys, for everyone who could see them. A car you added with only a tracker is different: removing it takes it off your garage and keeps its history until you delete your account.
Disconnecting Spotify locally removes its active grant, cancels pending approval requests, and clears linked players and playback cache. The account-level command journal is retained for duplicate protection until your SureCars account is deleted; car-linked journal entries can also be removed when that car connection is deleted. Local disconnection does not revoke Spotify’s own permission or cancel playback already accepted by Spotify. You can revoke the registered application’s access in your Spotify account; this can also affect other integrations using that same app registration, such as Home Assistant. Backup copies follow the service’s backup schedule.
You can delete your own account at any time, in the app under You, then Delete account, or on the website in Account, then Delete account. An administrator’s account is deleted by another administrator. It removes the account, every car connection and its saved data and journeys, tracker and watch accounts and what they saved, the children you added, unless another parent has also confirmed them, your phone’s readings, your saved places, your profile photo, your phone alert tokens, sharing and group memberships, mobile numbers, the Google link, the permissions SureCars holds for Google and Spotify, and all sessions. A car you transferred to family leaves their garage with its journeys. A car transferred to you in a family goes back to the person who gave it. A group you run stays for the people in it, with nobody to run it. Spotify and Google keep their own permission until you remove it there.
A few records stay after deletion, because they belong to someone else or to no account: counts of codes sent, until their 30 days are up; a number someone else typed to invite you or offer you a car, on their record; your name on a note someone else got, such as that you removed them, left a group or stopped sharing a car, until it ages out: 7 days, or 30 for a car transfer; your name on older journeys of someone else’s car, if it came from their Home Assistant, and the label of a Home Assistant person you linked; and the shared list of place names, which has no link to any account. The server is backed up every day, and backup copies, which can hold deleted data, are kept for about three months. Deletion cannot be undone. Other questions can be sent to the service operator.
You can also change your password, leave or manage a family, stop sharing a car with a family, trip or group, turn Recognise me in cars off, remove a guest share, and turn family location sharing off from the signed-in app where those controls are available.
06 · INDEPENDENT SERVICE
Manufacturer services remain separate.
SureCars is independently operated and is not affiliated with or endorsed by any vehicle manufacturer or any tracker or watch company. Direct connections depend on manufacturer services, regional availability and account rules that may change.
Questions about this notice or a data request can be sent to aryasumant@gmail.com.