Privacy
What we collect, and what we do with it.
In effect 19 November 2026 · Premise
Who is responsible
Premise is operated by FindFetch S.A.R.L. (Sole Partner), a Lebanese limited liability company registered under commercial register no. 2073544 at the First Instance Court of Baabda (Mount Lebanon), with its registered office at Lot 1707/4, Mansourieh, Lebanon. In this notice, “we” and “us” mean FindFetch. Contact: hello@premisepm.com. Full company details are in the legal notice.
Your building operator is the controller of data held for your building. FindFetch processes it on their instructions. FindFetch is responsible for enquiries sent through this website.
We have not appointed a data protection officer. Write to hello@premisepm.com about anything to do with your data.
1. Two different situations
Premise is software that building operators run for their buildings. That means personal data reaches us two different ways, and our responsibilities are not the same in each. Mixing them up is how privacy policies become useless, so they are separated here.
- You contacted us through this website. We decide what to do with what you sent. We are responsible for it.
- You are a tenant, resident or member of staff using the Premise app. Your building operator decides what goes in and who sees it. We hold and protect it on their instruction. In data-protection language they are the controller and we are the processor — practically, if you want your data in the app changed or removed, you ask them first, and they can instruct us.
2. If you use this website
The demo form
For demo enquiries, we rely on consent for optional fields and our legitimate interest in answering your enquiry.
For security logs and IP addresses, we rely on our legitimate interest in protecting the service from abuse.
When you ask for a demo you give us, and we receive:
| What | Why |
|---|---|
| Your name | To reply to a person rather than an address. |
| Company or building | To understand what you manage before the call. |
| Email address | To reply. This is the only field we reply to. |
| Phone or WhatsApp (optional) | Only if you would rather we called or messaged. |
| How many buildings | To know whether Premise fits before we take your time. |
| Your message (optional) | Whatever you choose to tell us. |
| Country of your connection | Added automatically by our host. Used to prioritise replies in our own time zone. |
| Your IP address | Added automatically by our host, and kept with the enquiry for the same 90 days. It is how we tell a real enquiry from a flood of automated ones. It is not used to identify or track you anywhere else. |
Your name, company or building, email address and number of buildings are needed to send the form; without them it is not sent. Phone or WhatsApp and your message are optional, and leaving them out does not stop the form from being sent.
That form sends one email to hello@premisepm.com and nothing else. It does not create an account, does not add you to a mailing list, and does not start an automated sequence. We reply, or we do not, and that is the end of it.
3. If you use the Premise app
Your building operator is responsible for this data. We hold it for them. What exists depends on what your building uses, and typically includes:
- Your account — name, email address, and a password we never store in readable form. Preferred language.
- Where you belong — the building, and the company or unit you are attached to, plus your role: tenant, resident, reception, valet, manager.
- What you do in the app — maintenance requests you report and any photos on them (photos are added in the web app or the phone app, by you or by the building’s team), rooms you book and the colleagues of your company you invite to a booking, questions you ask the help assistant, visitors you invite (their name and, if you add it, their car’s plate), parcels logged for you, valet requests (your car’s plate and, if you add it, a description of the car), survey answers, notices you post, and which notifications you have read.
- Messages, forms and suggestions: messages you exchange with your building’s team in a private conversation (web app); answers you give to a form your building publishes, or to a question when you book a room (web app); and suggestions you send, with your name or anonymously (web and phone apps). An anonymous suggestion is stored with nothing that identifies you, so nobody, your building’s managers included, can tell who sent it.
- Your building’s community: posts and comments you write on the building’s community page, which every member of your building can read; listings your company places in the building’s marketplace, which members of the building operator’s buildings can see, and messages about them; and perk vouchers you claim (we keep a four-character hint of a voucher’s code, never the code itself). All of these are in the web app.
- Groups and shared links: your building’s managers can put you or your company in a group, to send notices or documents to it; building staff can see who is in a group. A manager can also share one document through a link that works for 1 to 30 days. We record when the link was last opened, not who opened it.
- Reports and blocking in the phone app: you can report a notice, a notification or a person from the phone app, and block the author of a notice. A report goes to FindFetch, which runs Premise: we keep the reason, your description, a copy of the reported notice, the building, who sent the report and who it is about, and our decision, to review it and act on it under the app stores’ rules and our terms. We rely on our legitimate interest in keeping the app safe, and on the app stores’ requirement that we handle reports. We do not tell your building’s management who sent a report, and a blocked author is not told. What you hide or block stays until you undo it or close your account.
- Passkeys: if you add a passkey to sign in on the web with your face, your fingerprint or your computer’s screen lock, our sign-in provider stores the public part of the key, the device name and the date you added it. Your face or fingerprint never leaves your device. You can remove a passkey in your account settings.
- Money — invoices issued to your company, payments recorded against them, receipts, and your share of any split building cost.
- Documents — leases, insurance certificates and house rules your building shares with you or with your company.
- Help assistant: if you choose to use it, your questions, its answers and the conversation they belong to (see “The help assistant” below).
- Technical records — timestamps and identifiers needed to make the audit trail meaningful. A request having a time and an owner is the point of the product.
How it reaches us
- From you — when you sign up, sign in, or enter something in the web app or the phone app.
- From your building operator and its staff — when they approve your access, record you in the building’s register, log a parcel for you, share a document or issue an invoice to your company.
- From other people in your building — when a tenant invites you as a visitor, they enter your name and, if they choose, your car’s plate, so reception or security can check you in.
- From your building’s records: managers can import the records they already keep, such as a list of tenant companies, contacts (name, email, phone, job title), leases or car plates. An import does not create an account for anyone and does not send them anything.
- From visitors themselves: if your building publishes a visit page, a visitor can ask to visit by entering their name, who they are visiting and when, and, if they choose, a phone number or email, the company they are visiting, their car’s plate and whether they need parking. The front desk sees the request and decides on it. To limit abuse we keep a coded fingerprint of the visitor’s network address that changes every day, never the address itself. At check-in the front desk may take a photo of a visitor for the badge; only the front desk sees it.
- Automatically — as the service records when things happen and who did them.
What you must give, and what is optional
- Creating your own account on the web — your name, email address, a password of at least 10 characters, and your acceptance of the terms and this notice. Without them, no account can be created. For an invited account, your inviter supplies your details; you set your password and accept the terms before completing onboarding.
- Asking to join a building — your name, the building, and whether you are a company, a resident or staff. Your company’s name, a phone number and a note are optional; they help the manager recognise you. Without a building the request cannot be sent, and nothing is visible until a manager approves it.
- Inviting a visitor — the visitor’s name. Their car’s plate or a description of the car is optional. Without a name, no pass can be created.
- Asking to visit through a building’s visit page: your name, who you are visiting, the start and end of the visit, and ticking that you have read how your details are used. A phone number or email, the company you are visiting, your car’s plate and parking are optional. Without the required details, the request cannot be sent.
- Asking the valet for your car — your car’s plate. The car’s make and colour, and any note, are optional. Without a plate, the request cannot be sent.
- Everything else — requests, bookings, notices, survey and form answers, messages, suggestions, posts, reports and passkeys are given only when you choose to use that feature.
What it is used for
Only to run the service for your building, on your building operator’s instructions: who belongs where, maintenance, bookings, visitors and deliveries, messages and notices, the building’s financial records, access and security, and a reliable record of who did what. It is also used to send the emails the service needs — sign-in links, password resets and notifications.
FindFetch processes building data on the controller’s documented instructions. Your building’s privacy notice identifies the controller, its contact details, purposes and applicable legal bases.
Do not enter health, genetic or other sensitive information in requests, messages or uploads. If we discover such information, we restrict access, notify your building operator and act on its documented instructions, unless applicable law requires otherwise.
On your phone
- The phone app keeps your sign-in session in your phone’s secure storage (the iOS Keychain or Android Keystore). Two settings stay on the phone and are never sent to us: which building or company you are viewing, and whether the app lock is on.
- If you turn on the Face ID or fingerprint lock, your phone performs the check. The app only learns whether it passed; it never receives or stores your face or fingerprint.
- The phone app does not ask for access to your location, contacts, calendar or microphone. It asks for your camera only when you choose to take a photo for a maintenance request, and you can refuse. A photo from your library is chosen through your phone’s own picker, so the app receives only the photo you pick.
- It shows invoices but never takes a payment. It contains no advertising, and it does not track you across other companies’ apps or websites.
- Alerts. If you turn on push alerts, the app asks your phone for its push address and sends it, with a random code for that installation of the app, the phone type (iOS or Android), the app’s id and Premise’s project id with Expo, to Expo (see section 4). Expo passes each alert on to Apple or Google, which deliver it to your phone, so the text of an alert passes through Expo. Since 13 November 2026 this happens for anyone who turns alerts on; if you never turn them on, nothing is sent. You can turn alerts off in your phone’s settings.
- Updates. New versions of the phone app reach you through the App Store or Google Play. From the next version of the phone app it can also receive small fixes directly from Expo. That check is switched off when the version is released. We switch it on only after the building operator’s 30-day notice has ended or it has agreed in writing. Until then the app contacts no update service. Once it is on, each check sends Expo the phone’s operating system, Premise’s project id and a random code for that installation of the app, and, as with any internet request, Expo sees the phone’s IP address.
The help assistant
From 23 October 2026 the web app has a help assistant that answers questions about your building. It sends data to Anthropic PBC (United States), which generates the answers.
- Who can use it. Tenants (company admins and employees), residents, and building owners and managers. Building staff (maintenance, valet, reception, accounting and general building staff) can use it only when their building’s manager switches it on for staff. A building manager can also switch the assistant off for one person.
- Nothing is sent before you agree. The app first shows a screen that explains this. You can withdraw from that page at any time. The rest of Premise works the same either way.
- What is sent to Anthropic with each question. Your question; the earlier messages of that conversation (up to the last 12 exchanges); and the building’s shared information: its name, address, description, number of floors and public contact details, the handbook your building’s management writes, building-wide notices of the last 30 days, the titles of building-wide documents, upcoming building-wide events, and bookable rooms with their rules.
- Tenants and residents: your own records. To answer, the assistant may also look up records of yours, read with your own permissions, and these are sent too: your maintenance requests, your company’s invoices, your room bookings, your guest passes (guest name, dates, and car plate if entered, never the pass code), deliveries logged for your company, events and your reply, and notices sent to your company or group.
- Owners, managers and building staff: building records. Where Premise has switched record look-ups on for a building, the assistant on the management desk may also look up that building’s spaces, current leases, tenant companies, maintenance requests, invoices and what is owed, the visitors expected on a day (their name, the company expecting them and the times of the pass, never the pass code or the car’s plate), room bookings (room, time and company) and the building’s own figures, read with the permissions of the person asking, and these are sent too. Elsewhere it sends only the question, the conversation and the building’s shared information.
- It never acts by itself. It can prepare a request, booking, guest pass or event reply, for a company admin an invitation for a colleague to join their company, and on the management desk a change to a maintenance request or a space. You must confirm it in the app before anything is saved.
- How long we keep conversations. Premise keeps each conversation for 30 days so you can read it back, then deletes it automatically. You can delete it sooner. If you report an answer, its text goes to Premise’s support team.
- Answers can be wrong. Check anything that matters with your building’s management before you rely on it.
Who can see it
Separation between buildings, and between tenant companies inside one building, is enforced in the database itself rather than by hiding buttons in the interface, and an automated isolation test runs before every release. In practice:
- A tenant sees their own things, and what their company shares with them.
- A tenant of one company never sees another company's requests, invoices or documents.
- Someone in one building never sees anything from another building.
- Managers and staff of your building see what their role requires — a maintenance request has to reach whoever fixes it.
What we never do with it
- We do not sell it, and we do not share it with advertisers.
- We do not use one building operator's data to serve another.
- We do not use it to train machine-learning models, and Anthropic does not use it to train its models either.
- We do not read your content except when we have to fix a fault you or your operator reported, and only as far as that fault requires.
4. Who else touches the data
Running software means using other companies' infrastructure. The providers used by the service are listed below. This website loads its typefaces and its animation library from its own server, so no font or script provider receives your IP address when you visit:
| Who | What for |
|---|---|
| Supabase | The database, sign-in, and stored files (documents, photos on requests), hosted in Frankfurt, Germany. |
| Vercel | Runs the app itself; functions are configured for Frankfurt, Germany. Provider account data and logs may be processed outside the EU. |
| Cloudflare | Serves this website and protects traffic from attack through its global network. Its Turnstile check also confirms that a sign-in or a password reset in the web app or the phone app, or a new account made in the web app, comes from a person and not an automated program: for that it processes your IP address and the technical details your browser or phone sends with the check, solely to detect and block automated programs. |
| Resend | Sends email — sign-in links, password resets, notifications, and the demo form on this site. Email content and delivery records are stored in the United States. |
| Anthropic | Answers questions in the help assistant, only for people who have agreed to use it (see “The help assistant” in section 3). The United States. |
| Expo (650 Industries, Inc., United States) | Delivers push alerts from the phone app (since 13 November 2026, only for people who turn alerts on) and, from the phone app’s next version and only once we switch it on, delivers app updates (see “On your phone” in section 3). Expo passes alerts on to Apple and Google. |
| Sentry | Tells us when the web app breaks or responds slowly. It has been switched on for the web app since 28 October 2026, and its reports are stored in the European Union (Frankfurt, Germany). Before a report is sent we remove your name and email, what you submitted in forms, cookies and the details in web addresses; a report does carry your account's internal id, so we can tell whether a fault hit one person or everyone. |
The same list, with each provider’s region and a link to its terms, is on the sub-processors page.
How they protect it
Supabase, Vercel and Resend receive personal data from the Premise app, and provide protection at least equivalent to this privacy notice. Each is bound by data processing terms that form part of its standard terms for the plan Premise runs on: it may process the data only on our documented instructions, must keep it confidential, must protect it with appropriate security measures and must tell us about a breach. Under our agreement with your building operator, we remain responsible to it for each of them.
Expo (650 Industries, Inc.) receives personal data from the phone app: for push alerts, the push address of the phone, a random code for that installation of the app, the phone type, the app’s id and Premise’s project id, and the text of each alert; for app updates, once switched on, the operating system, the project id, a random code for the installation, and the phone’s IP address. It provides protection at least equivalent to this privacy notice: under section 3.2 of its terms (expo.dev/terms, updated 2 November 2026), where the GDPR applies Expo acts as a processor for this data and applies module two of the EU Standard Contractual Clauses, and it states that it participates in the EU-U.S. Data Privacy Framework (expo.dev/privacy). Unlike Supabase, Vercel and Resend, Expo has no separate data processing agreement with us on the plan Premise runs on; its terms are the basis. Under our agreement with your building operator, we remain responsible to it for Expo too.
Cloudflare, which serves this website and receives the demo form, applies its data processing addendum to personal data of people in Europe and California.
Anthropic receives personal data from the help assistant. Its data processing addendum forms part of its Commercial Terms. Anthropic may not train its models on the questions and answers it handles for us. It deletes them from its systems within 30 days of receipt or generation, with the exceptions in section 5.
Where it is processed, and how transfers are protected
- Supabase — the database and files are stored in Frankfurt, Germany; Supabase and its sub-processors may process data wherever they have facilities. Its data processing terms include the EU Standard Contractual Clauses.
- Vercel — the app’s functions run in Frankfurt, Germany; Vercel’s main processing facilities are in the United States. Its data processing terms include the EU Standard Contractual Clauses.
- Resend — email content and delivery records are stored in the United States. Its data processing terms include the EU Standard Contractual Clauses, and Resend participates in the EU-U.S. Data Privacy Framework.
- Cloudflare — a global network. Its data processing addendum applies the EU Standard Contractual Clauses, and Cloudflare participates in the EU-U.S. Data Privacy Framework.
- Anthropic: the help assistant sends data to Anthropic PBC in the United States. Its data processing addendum includes the EU Standard Contractual Clauses.
- Expo: Expo, a company in the United States, receives the data described above for push alerts and, once switched on, app updates. Under section 3.2 of its terms it applies the EU Standard Contractual Clauses (module two) where the GDPR applies, and it participates in the EU-U.S. Data Privacy Framework. Apple (APNs) and Google (FCM), which deliver the alerts to your phone, are Expo’s own recipients.
- FindFetch — we are in Lebanon and access data from there to run and support the service. The European Commission has not recognised Lebanon as providing adequate protection. Where the GDPR applies to a building operator’s processing, our data processing agreement commits us to sign the appropriate transfer instrument with that operator.
- Sentry — error and slow-page reports from the web app are stored in Frankfurt, Germany. Sentry is a company in the United States.
Whether the GDPR applies depends on the building operator and the people concerned; this notice does not assume it. To get a copy of a transfer safeguard that applies to your data, or to ask exactly where your data is, write to hello@premisepm.com.
5. How long we keep it
| What | How long |
|---|---|
| Demo enquiries | The enquiry our website stores, with your IP address, is deleted automatically after 90 days. A counter tied to your IP address, used to limit repeated submissions, is deleted automatically after one hour. Our email provider keeps the email copy for 30 days; the copy in our mailbox is deleted within 12 months after our last contact with you, unless we are still discussing a subscription with you, and sooner if you ask. |
| App data while the subscription runs | For as long as your building operator uses Premise, unless it deletes records sooner or its agreement with us sets a shorter period. Premise deletes building records automatically only under a retention schedule your building operator has agreed with us, or where this table gives a fixed period. Records with an accounting purpose — invoices, receipts — are kept as long as the law that applies to them requires. |
| Your account after you close it | Closing an account anonymises the profile and signs the account out permanently. Building records your building operator must keep (requests, bookings, invoices, visitor passes, audit entries) stay with it, because the building’s history and accounts depend on them. Remaining records are deleted according to the building operator’s agreed retention and exit instructions, subject to specifically identified legal retention requirements. Subscription termination does not itself immediately delete every record. Ask your building operator how long it keeps them; if you cannot reach it, write to hello@premisepm.com and we will pass your question on. See how to delete your account. |
| After a building operator’s subscription ends | Our data processing agreement requires us to return or delete its data as it instructs, keeping a copy only where a specific law requires it. It can ask for a copy of its data, provided within 30 days of the request. |
| Backups | Daily database backups at our database host are kept for 7 days, then overwritten. We also keep a second, encrypted daily backup on our administrator’s computer; each one is deleted at the first backup run after it is 6 days old, and that job runs every night and whenever the computer starts. Deleted data therefore normally leaves our backups within 7 days. A copy on that computer can stay longer only while the computer is switched off or asleep (it is then deleted when the computer is back on), or if a deletion fails, in which case our administrator is alerted and deletes it by hand. |
| Technical and security logs | Kept by our providers on their own schedules: request logs at Vercel for 1 day and at Supabase for 7 days on the plans Premise runs on, and email delivery records at Resend for 30 days. Cloudflare applies its own retention to the traffic it handles. |
| Help assistant conversations | At Premise, 30 days, then deleted automatically; you can delete one sooner. At Anthropic, deleted within 30 days of receipt or generation. Longer only if Anthropic’s systems flag a conversation as a possible breach of its usage policy (inputs and outputs up to 2 years, safety classification scores up to 7 years), or where the law requires it. |
| Help assistant usage counts | Premise keeps a count of questions and their cost per person per day, for the building’s limits. Deleted automatically after 13 months. |
| Push alerts and app updates at Expo | Expo states that it keeps personal information only for as long as reasonably necessary. We have no fixed period from Expo for push addresses or update requests, so we cannot give you one. Turning alerts off stops new data going to Expo; write to hello@premisepm.com if you want your push address removed. |
| Reports from the phone app | Deleted 12 months after we close them, unless a legal hold applies; a report we have not closed yet is kept until we do. When you close your account, your reports lose your name and what you hid or blocked is deleted. A report about someone who later closes their account keeps only an internal id for them until the report is deleted. |
| Visitor photos taken at the desk | Deleted automatically 30 days after the visit ends. |
| Visit requests from a building’s visit page | Deleted automatically 30 days after the visit ends. |
| Messages, form answers and groups after you close your account | Conversations you opened are deleted with their messages; your messages in other conversations are replaced with “(message removed)”; your form answers are emptied; and you are removed from the groups you were in. Your company’s place in a group stays. |
| Your sign-in on the phone | Stays on your phone until you sign out or close your account. |
6. Your rights, and how to use them
Under Lebanese Law No. 81 of 2018 on Electronic Transactions and Personal Data, and as a matter of how we would want to be treated, you can:
- Ask what we hold about you, and get a copy.
- Have anything wrong corrected.
- Ask for it to be deleted.
- Object to a particular use, or withdraw a consent you gave. Withdrawing consent does not affect processing that took place lawfully before you withdrew it.
- Request restriction of processing and portability where GDPR applies.
- Complain to a supervisory authority: the Lebanese Ministry of Economy and Trade for Lebanese data subjects under Law 81, or the data-protection authority where you live if its law gives you that right.
We do not make decisions about you by automated means alone that have a legal or similarly significant effect, and we do not build a profile of you.
You can close your own account at any time, in the web app or the phone app — see how to delete your account.
For anything else, write to hello@premisepm.com. For people in Lebanon, a request to see or correct your data is answered within 10 working days (Law 81/2018 Art. 107), and a correction or erasure is made free of charge within 10 days of the request (Art. 101). Other requests are answered without undue delay and within one month of receipt. If your request is about data inside the app, we will tell your building operator, because it is theirs to decide — and we will say so plainly rather than going quiet.
7. Cookies
This website sets no cookies at all. The app sets what signing in requires: a cookie that keeps you signed in, and a short-lived one that protects the sign-in itself. It also sets two cookies that remember the building or the company you last chose, for one year. There is no advertising cookie, no analytics cookie and no third-party cookie anywhere in either. Clearing them signs you out and forgets that choice; nothing else breaks.
8. Security
- Everything travels over HTTPS. The site is served with a strict content policy and HSTS.
- Passwords are hashed, never stored in a form anyone can read, and checked against known-breached password lists at sign-up.
- Separation between buildings and companies is enforced by database row-level security, not by the interface.
- No security is absolute. If a breach affects data held for your building, we tell your building operator without undue delay and help it inform you; if it affects an enquiry you sent us, we tell you directly. Either way we say what we know rather than what sounds reassuring.
9. Changes, and how to reach us
Changes on 19 November 2026: section 4 now says that Cloudflare’s Turnstile check confirms that a sign-in or a password reset in the web app or the phone app, or a new account made in the web app, comes from a person, and what it processes for that (your IP address and the technical details your browser or phone sends with the check, solely to detect and block automated programs).
Changes on 16 November 2026: Expo, the company whose tools we use to build the phone app, receives data from the phone app, and our statement of 27 September 2026 that Expo no longer receives anything from it stopped being true when push alerts reached the phone app on 13 November 2026. Since that date, for people who turn on push alerts, Expo receives the phone’s push address and the app’s details and passes each alert on to Apple or Google. From the phone app’s next version Expo may also deliver app updates, only once we switch that on. We added Expo to the recipients, the protection and transfer lists and the retention table (sections 3, 4 and 5).
Changes on 12 November 2026: the help assistant section now says that, where Premise has switched record look-ups on for a building, the management desk’s assistant can also look up that building’s invoices and what is owed, the visitors expected on a day, room bookings and the building’s own figures; and that for a company admin the assistant can prepare an invitation for a colleague, which is sent only when the admin confirms it; section 3 now says that when you invite colleagues to a room booking, we keep who was invited and by whom.
Changes on 11 November 2026: we added that we have not appointed a data protection officer, that we make no decisions about you by automated means alone and build no profile of you, and the legal basis for reports made in the phone app; section 7 now names the two cookies that remember the building or company you last chose; section 3 now says that the phone app asks for your camera when you take a photo for a maintenance request, and that a photo can also be chosen from your library through your phone’s own picker; the list of what we collect in the same section is updated to match. Section 4 now says that Sentry, which tells us when the web app breaks or responds slowly, has been switched on for the web app since 28 October 2026, with its reports stored in the European Union (now also in the list of where data is processed), and states more exactly what is removed from a report before it is sent.
Changes on 28 October 2026: the help assistant section now says that, where Premise has switched record look-ups on for a building, the management desk’s assistant looks up that building’s spaces, current leases, tenant companies and maintenance requests to answer, and can prepare changes you confirm.
Changes on 24 October 2026: this notice now describes reports and blocking in the phone app, messages with your building’s team, forms, suggestions, the community page, marketplace and perks, groups and shared document links, passkeys, the records managers import, and visits requested through a building’s visit page, including the desk’s visitor photo (section 3), and how long reports, visitor photos and visit requests are kept and what happens to messages, form answers and groups when you close your account (section 5). Changes on 23 October 2026: the web app has a help assistant that sends data to Anthropic PBC (United States), only after the person agrees in the app. We added it to sections 3, 4 and 5. Changes on 13 October 2026: this website no longer loads fonts or scripts from Google Fonts or jsDelivr, so neither receives visitor IP addresses. Changes on 29 September 2026: for people in Lebanon, a request to see or correct your data is now answered within 10 working days, as Lebanese law requires; other requests are answered without undue delay and within one month of receipt (section 6). Changes on 27 September 2026: the phone app no longer used the update service of Expo, the company whose tools we use to build the app, so Expo received nothing from it. That was no longer true from 13 November 2026 (see the change of 16 November 2026). Changes on 26 September 2026: Premise’s operator is now FindFetch S.A.R.L. (Lebanon); written for general availability. We also set out how data reaches us, what you must give and what is optional, what it is used for, what the phone app keeps on your phone, the visitor and valet details, how providers protect data and where it is processed, and how long each kind of record is kept.
If this notice changes in a way that affects you, we will say so in the app and update the date at the top. We will not quietly widen what we do with your data and leave you to notice.
Questions, requests, or a complaint about how we have handled something: hello@premisepm.com.