OptiBridge (Chrome extension)
Privacy Policy
Last updated: 15 November 2026 (version 1.3.16)
OptiBridge (until version 1.3.11 named "OptiBridge — כניסה ללקוח") is an internal tool of OptiCity for its staff. It works only on the OptiCity site (app.opticity.co.il and its server, server.opticity.co.il) and on OptiBridge, the company's internal tool (optibridge.app); signing in, the report, the employee list and an address update happen only when an employee asks for them in OptiBridge. It does seven things:
- Signs the employee in to app.opticity.co.il as the client they chose - in the normal window, or, on request, in a separate private (incognito) window, so a second client can be open side by side. Since 1.3.13, an employee who switches "פרהפרוד" on in OptiBridge is signed in to OptiCity's test site instead (pre-app.opticity.co.il and its server, pre-server.opticity.co.il), with the same details. The extension reaches the test site only after that employee allows it once in Chrome; nobody else's extension asks for it. A sign-in to the test site is never kept for a quick switch and never handed to a sign-up site.
- Switches clients quickly (1.3.8; bound to the password since 1.3.9): after a sign-in it keeps that client's OptiCity sign-in, with a fingerprint of the password it was made with, for up to 7 days of the browser session, so the next switch to the same client - with the same password - does not sign in again. Since 1.3.10 it first reads, inside the browser, which OptiCity account the sign-in belongs to: a sign-in that landed in another account is signed out at once and never kept.
- Hands the client's sign-in to OptiBridge's server (1.3.6; since 1.3.9 only for a client that has a sign-up site): when OptiBridge asks for it at a sign-in in the normal window, so the server can pass it on to that client's employee sign-up site, which uses it to add the client's new employees to the client's OptiCity account.
- Reads the client's monthly "כספי מחיר ספק" (supplier price) report for the finance department, so OptiBridge can turn it into an Excel file.
- Reads the client's employee list (1.2.0), so the company can keep its WhatsApp contact list of that client's employees up to date.
- Makes OptiCity's own screens clearer (1.3.12): on app.opticity.co.il it shows the status of each ride sent to Gett (waiting, reserved, cancelled...) as a coloured label beside its icon, read from the screen itself, and marks "לא סונכרן" on a ride that changed after it was sent to Gett (a new pickup time, stations, passengers or supplier). For that it reads the ride's change history from server.opticity.co.il - the same request as the site's own "היסטוריית שינויים" button. It also hides the site's "receive notifications" pop-up. This happens only on the screen: nothing is stored (beyond the open page's memory) or sent anywhere else.
- Updates one employee's address in OptiCity (1.3.16): when a member of staff changes an employee's address in OptiBridge and confirms it, the extension signs in as that employee's client, finds the employee by phone number and saves the new address in the client's OptiCity account - the same save the site's own employee screen makes - then reads the employee back to check it. To place the address on the map it uses the Google Maps service the OptiCity site itself loads on its pages, as that site does for any address typed into it.
What personal data it handles
- Sign-in details: the username and password for app.opticity.co.il that the employee's OptiBridge account holds for the chosen client; and, after signing in, the three cookies that make up that client's OptiCity sign-in.
- The finance report: the month's trips as OptiCity returns them - dates, cities, prices, the trip's free-text remarks, the driver's name and code, and for each trip the passengers' names, departments and pickup addresses.
- The employee list: for each of the client's employees, the name, the phone number and whether the employee is active - the same list the site's own "employee details" Excel export holds - and, since 1.3.15, the address OptiCity holds for that employee (street, house number and city, as text).
- An address update (1.3.16): the employee's phone number and the new address a member of staff typed in OptiBridge; and, while saving it, that employee's record as OptiCity returns it, which is sent back to OptiCity with only the address changed.
How we use it, and why
We use the data only for the seven purposes above: to sign the employee in, to switch between clients faster, to let a client's sign-up site add new employees, to give the finance department the client's report, to keep the company's WhatsApp contact list of the client's employees current, to show the status of Gett rides on OptiCity's own screen, and to update an employee's address in OptiCity when the company's staff change it. None of it is sold, used for advertising, or used to decide creditworthiness or for lending.
Who it is shared with
- The username and password go only into the app.opticity.co.il sign-in form (or, with "פרהפרוד" on, the pre-app.opticity.co.il one).
- The sign-in cookies go back into the browser for a quick switch. Only for a client that has a sign-up site, and only when OptiBridge asks for it at a sign-in in the normal window, they also go from the OptiBridge page to OptiBridge's own server, which passes them on to that site; for every other client they never leave the extension. OptiBridge's change log records who handed a sign-in to which client, and when. Since 1.3.14, when a sign-in fails because the browser is still signed in to another client, the extension tells the OptiBridge page that client's OptiCity username - read from the sign-in cookie, nothing else from it - and the failure line in the change log names that client and the extension's version. The sign-up site keeps the latest copy, encrypted, and uses it until the OptiCity sign-in itself runs out - at most seven days after each hand-off - until the next one replaces it. (Version 1.3.8, until Chrome updates the extension to 1.3.9, sends the sign-in of every client to OptiBridge's server after each sign-in in the normal window and each quick switch; the server passes on only those of a client that has a sign-up site, which keeps that copy for seven days, and drops the rest without storing them. 1.3.8 also reuses a saved sign-in whatever password comes with the request.)
- The finance report goes only to the OptiBridge page that asked for it, in the same browser, which builds the Excel file on the employee's computer. OptiBridge records when a report was downloaded, how many trips it had and its total - not the trips or the passengers.
- The employee list goes to the OptiBridge page that asked for it. The page sends the employees who joined (name and phone) and the phone numbers of those who left through OptiBridge's server to respond.io, the company's messaging provider (a service provider acting for the company), where they are added to, or removed from, the company's WhatsApp contact list of that client; a contact whose only client this was is deleted there. OptiBridge keeps, for 180 days, the names and phone numbers of the employees a sync removed or could not add, and its change log keeps the phone number of each contact removed (six months by default). Since 1.3.15 an employee's address goes with their name and phone to OptiBridge's own database only - it is not sent to respond.io - where the company's staff see it beside the phone number; it is deleted there when the employee is removed from the client's contact list.
- An address update (1.3.16) goes from the OptiBridge page to the extension, and from the extension into the client's own OptiCity account (server.opticity.co.il), where that employee's address is replaced. To find the address on the map, the typed address - the address text only, nothing else about the employee - is sent from OptiCity's own page to Google Maps, the map service that site already uses for every address. OptiBridge keeps the new address beside the employee's phone number, and its change log records who changed it and whether OptiCity was updated.
Nothing leaves the company's own systems - OptiBridge and the sign-up sites it runs, both hosted on Cloudflare - except the contact list kept in respond.io and, for an address update, the address text looked up on Google Maps through OptiCity's page. It is not shared with any other third party: nothing goes to an advertiser or anybody else. The extension's own network traffic is the sign-in to app.opticity.co.il, the same requests OptiCity's own screens make to server.opticity.co.il (reading, and for an address update saving one employee), and, after a sign-in of a client that has a sign-up site, the one request from the OptiBridge page to OptiBridge's own server that carries the sign-in.
What it stores, and how long it is kept
- The sign-in cookies of the clients signed in during this browser session, each under the client's OptiCity username, in
chrome.storage.session- the browser's memory, never written to disk - with a fingerprint of the password they were made with: an HMAC of it under a random key kept in the same memory, never the password itself. A quick switch reuses a copy only when the password that comes with the request makes the same fingerprint and the copy is less than 7 days old; otherwise the employee is signed in from the start. A client's copy is replaced at its next full sign-in, dropped when a quick switch finds it no longer works or the password differs, and all of it is gone when the browser closes. - The username, OptiCity user id and password fingerprint of the client it signed in last, in memory only, while Chrome keeps the extension running - so a second report of the same client, asked with the same password, does not sign in again.
- The password, the report, the employee list and an address update are not stored by the extension: they are discarded as soon as the request is done.
What it removes and closes
Before signing in as a different client it closes the app.opticity.co.il tabs that are open and clears, in the browser, the cookies of app.opticity.co.il and of server.opticity.co.il and app.opticity.co.il's site storage, so that the previous client's session ends - and, once the test site is allowed, its tabs, cookies and site storage too. A report or an employee list is read, and an address update is made, in a minimized private window with its own cookies, so the employee's own sign-in is not touched, and the extension closes it when done. Without permission for private windows it happens in a background tab instead, which signs the browser in as that client and leaves it signed in as that client. It touches no other site.
Where it runs
On app.opticity.co.il and server.opticity.co.il (and, for an employee who allowed it, on pre-app.opticity.co.il and pre-server.opticity.co.il), and - only to pass requests and answers between the page and the extension - on OptiBridge's own page, optibridge.app, behind the company's sign-in. It accepts requests only from that page's main frame. (Up to 1.3.8 it also ran on OptiBridge's original address, optibridg.pages.dev, and its preview versions; 1.3.9 does not.)
Your rights
What the extension keeps is in the browser's memory and is gone when the browser closes; uninstalling the extension removes it at once. The usernames and passwords it is handed are kept, encrypted, in OptiBridge: each employee can see, change or delete their own, and an administrator manages the shared ones. The copy of a sign-in at a sign-up site is replaced at each hand-off and stops being used when the OptiCity sign-in runs out, at most seven days after it; to have it removed sooner, ask the operations team. The trip data and the employee list belong to the client's OptiCity account; the WhatsApp contact list is the company's, in respond.io.
Changes to this policy
When the extension changes what it handles, this policy changes with it: the date and the version at the top say which version of the extension it describes.
Contact
Questions about this policy: the OptiCity operations team, through OptiBridge.
מדיניות פרטיות
התוסף הוא כלי פנימי של OptiCity, ופועל רק כשעובד מבקש מתוך OptiBridge (optibridge.app). הוא מקבל מ-OptiBridge את שם המשתמש והסיסמה של העובד ללקוח שנבחר ונכנס בשמו לאתר app.opticity.co.il - בחלון הרגיל או, לפי בקשה, בחלון גלישה בסתר נפרד. מגרסה 1.3.13, עובד שהדליק את "פרהפרוד" ב-OptiBridge נכנס עם אותם פרטים לאתר הבדיקות של OptiCity (pre-app.opticity.co.il), אחרי שאישר לתוסף פעם אחת גישה אליו; כניסה כזאת לא נשמרת למעבר מהיר ולא עוברת לאתר הרשמה. אחרי הכניסה הוא שומר את עוגיות הכניסה של הלקוח, יחד עם טביעה של הסיסמה (HMAC במפתח אקראי שנשמר באותו זיכרון - לא הסיסמה עצמה), בזיכרון של הדפדפן בלבד (chrome.storage.session, לא על הדיסק), עד שבעה ימים ולכל היותר עד שהדפדפן נסגר, כדי לעבור שוב לאותו לקוח מהר - ורק עם אותה סיסמה. רק ללקוח שיש לו אתר הרשמה לעובדים, ורק כש-OptiBridge מבקש זאת בכניסה בחלון הרגיל, עוגיות הכניסה עוברות מדף OptiBridge לשרת של OptiBridge, שמעביר אותן לאתר ההרשמה; של כל שאר הלקוחות הן לא יוצאות מהתוסף (גרסה 1.3.8, עד ש-Chrome מעדכן אותה, שולחת לשרת את הכניסה של כל לקוח אחרי כל כניסה וכל מעבר מהיר, והשרת מוותר על מי שאין לו אתר הרשמה בלי לשמור). אתר ההרשמה שומר את העותק האחרון מוצפן ומשתמש בו עד שהכניסה ל-OptiCity עצמה פגה, ולכל היותר שבעה ימים, כדי להוסיף עובדים חדשים לחשבון OptiCity של הלקוח, ויומן השינויים של OptiBridge רושם מי העביר כניסה, לאיזה לקוח ומתי. מגרסה 1.3.14, כשכניסה נכשלת כי הדפדפן עדיין מחובר ללקוח אחר, התוסף מוסר לדף OptiBridge את שם המשתמש של אותו לקוח ב-OptiCity (מתוך עוגיית הכניסה, ושום דבר אחר ממנה), ושורת הכישלון ביומן השינויים מציינת את הלקוח הזה ואת גרסת התוסף. עבור מחלקת הכספים התוסף קורא את דו״ח "כספי מחיר ספק" של הלקוח - נסיעות, מחירים, הערות, שם וקוד הנהג, ושמות, מחלקות וכתובות איסוף של נוסעים - ומעביר אותו רק לדף OptiBridge שביקש אותו. לסנכרון עובדים הוא קורא את רשימת העובדים של הלקוח (שם, טלפון, פעיל או לא, ומגרסה 1.3.15 גם הכתובת ש-OptiCity מחזיק לעובד; הכתובת נשמרת רק במאגר של OptiBridge עצמו, מוצגת לצוות ליד הטלפון, לא נשלחת ל-respond.io ונמחקת כשהעובד מוסר מרשימת אנשי הקשר של הלקוח) ומעביר אותה לדף OptiBridge, ששולח דרך השרת של OptiBridge את המצטרפים (שם וטלפון) ואת הטלפונים של העוזבים ל-respond.io, ספק ההודעות של החברה, כדי לעדכן את רשימת אנשי הקשר בוואטסאפ של אותו לקוח. OptiBridge שומר 180 יום את השמות והטלפונים של עובדים שסנכרון הסיר או לא הצליח להוסיף, ויומן השינויים שומר את הטלפון של כל איש קשר שהוסר (שישה חודשים כברירת מחדל). מגרסה 1.3.16, כשאיש צוות משנה ב-OptiBridge כתובת של עובד ומאשר, התוסף נכנס בשם הלקוח של אותו עובד, מאתר את העובד לפי מספר הטלפון ושומר את הכתובת החדשה בחשבון OptiCity של הלקוח, כמו שמסך העובדים של האתר עצמו שומר; כדי למקם את הכתובת על המפה, מלל הכתובת בלבד נשלח מהדף של OptiCity ל-Google Maps, שירות המפות שהאתר כבר משתמש בו. OptiBridge שומר את הכתובת ליד הטלפון של העובד, ויומן השינויים רושם מי שינה אותה ואם OptiCity עודכן. שום מידע לא נמכר, ושום מידע לא יוצא מהמערכות של החברה (OptiBridge ואתרי ההרשמה שהיא מפעילה, ב-Cloudflare) מלבד רשימת אנשי הקשר ב-respond.io ומלל הכתובת שנבדק ב-Google Maps דרך הדף של OptiCity. לפני כניסה ללקוח אחר התוסף סוגר את לשוניות OptiCity ומנקה את העוגיות והאחסון של אתר OptiCity בלבד. יצירת קשר: צוות התפעול של OptiCity, דרך OptiBridge.