Skip to main content

Privacy Policy

Effective . This document is provided in English.

This policy explains what LUCAS collects when you file or follow a repair request, use your building’s resident portal, work in a staff portal, or visit our website; what we do with it; and the choices you have.

In short: your request goes to the people who manage your building, a few service providers help us run LUCAS, and we never sell your information. Text messages are optional, and you can stop them at any time. So are the emails the resident portal sends about your requests.

Who we are

LUCAS is a repair request service for residential buildings. Tenants use it to report a problem and follow the repair; building staff use it to assign, schedule and record the work.

LUCAS is a product of Couwed Inc (“Couwed”, “we”, “us”). We provide LUCAS to the companies that manage residential buildings, so when you file a repair request you are sending it to your building’s management, and we carry it for them.

Mailing address: 301 W 45th Street, New York, NY 10036. Email: [email protected]

Who this policy covers

  • Tenants and residents who file a repair request, follow one on its status page, or answer the survey after a repair.
  • Residents who use their building’s resident portal, whether they asked the building for access or were invited by it: to sign in, file and follow their requests, and write to the people handling them.
  • Building staff who sign in to a LUCAS portal because they work for a building that uses LUCAS.
  • Visitors to our website, lucasmanages.com.

Your building’s management decides how repairs are run in your building, and its own policies may also apply to how it uses your request.

What we collect

When you file a repair request

  • What is wrong: your description, the kind of problem, how urgent it is, and the short title the crew sees.
  • A photo of the problem, if you add one.
  • Your apartment, your name and your phone number, so building staff can reach you about the repair.
  • How staff can get in (whether someone will be home, or whether they may come in while you are out), the days and times that suit you, and any note you add about access.
  • Whether you checked the box to get text messages and, if you did, when you sent the request with it checked and which version of its wording you saw.

If you use the microphone button to speak instead of typing, your browser turns your speech into text before anything reaches us. “Tools you or building staff choose to use” below explains what that involves.

After you file

  • Messages you send, and changes you make, from your request’s status page.
  • Your rating and comment, if you answer the survey after the repair.
  • A copy of each text message we send you about your request, with when it was sent and whether it was delivered.
  • Your replies to our texts, and a record of each time you text STOP or START, with the date.

If you use the resident portal

  • Your account: your name, the email address you sign in with, the phone number and apartment your building has on file for you, the language you use the portal in, and when you last signed in. If the building office changes your email address, we record when it was changed and by whom.
  • If you ask for access: what you enter on the form (your name, email address and apartment, and your phone number and a note if you add them), the language of the page, the internet (IP) address the request came from, and whether the building approved or declined it.
  • Sign-in links: when each link was sent, the internet address it was asked for from (when you asked for it yourself), and whether it was used. The link itself is stored only in a form that cannot be turned back into a working link.
  • The conversation on each of your requests: the messages and photos you and the building’s staff send, when each was sent, when you read the building’s replies, and when each of your messages was read and by which member of staff.
  • Whether you want emails about your requests, and when and how you last turned them on or off.
  • A record of each update email we send you: the address it went to, what it was about, when it was sent, and whether our email provider accepted it.

What building staff add

  • Notes about the job, who it is assigned to, and any appointment that is booked.
  • When staff arrive at and leave your apartment, and how each visit went.
  • A photo of the finished work.
  • Notes from any call the front desk makes to you after the repair, including how you rated the work.

If you report a problem to building staff by phone or in person, they can file the request for you, with your name and contact details.

If you work for a building that uses LUCAS

  • Your account: your name, email address, phone number, job title, role and, if you add one, a photo. We never store your password itself, only a hash of it that cannot be turned back into the password.
  • Text alerts, if you turn them on: when you did, the number you agreed for, the wording you agreed to and the alerts you picked; a copy of each alert and each code text we send you (never the code itself), with when it was sent and whether it was delivered; your replies; each STOP or START; and, if someone turns your alerts off for you, who did it and why.
  • Your work: the jobs assigned to you, your notes, your visits and the times you checked in and out, the materials you request or approve, reviews of finished jobs, and the performance figures worked out from all of these.
  • If you answer residents in the resident portal: your replies and the photos you add to them, and when you mark a resident’s messages as read.
  • The notifications LUCAS shows you.
  • Feedback you send with the feedback button, together with the page you were on, your portal, your language, your screen size and your browser.

When you visit our website

Like most web servers, ours keeps an access log of each request it answers: your IP address, the date and time, the address of the page, and the technical details your browser sends with every request, such as its type and version. We use it only to keep the service running and secure.

If you email us, we keep your message and your address so we can reply.

We do not use analytics or advertising services, and we do not track you across other websites.

How we use it

  • To get your request to your building’s management and let the people they choose handle it: assign it, book a visit, do the work and keep a record of it.
  • To keep you informed: on your request’s status page; if you use the resident portal, there and by email to the address you sign in with (you can turn these emails off); and by text if you asked for texts. Building staff may also call you about the repair.
  • To let you follow your request, correct it, send a message about it and rate the repair.
  • In the resident portal: to sign you in with a one-time link sent to your email, to show you the requests that are yours, and to let you and your building’s staff write to each other about them. A request is shown to you when the email address or phone number given with it matches yours and no one else’s in your building, or when building staff link it to you.
  • For building staff: to run your account, show you your work, text you alerts about it if you turned them on, and give your managers the records and reports they use to run the building.
  • To keep LUCAS working and secure: to limit how often one connection can send forms, to investigate problems, and to recover from failures.
  • To improve LUCAS, using the feedback staff send us.
  • To meet our legal obligations.

We do not use your information for advertising, we do not sell it, and we do not build advertising or marketing profiles of you.

Who can see it, and who we share it with

We never sell personal information, and we never share it for advertising. These are the people and companies who can see it, and why.

Inside LUCAS

Your building’s management and staff. Your request goes to the company that manages your building and to the staff it gives access: the resident manager, the front desk, the handyman assigned to the job, and managers who can view requests but not change them. Handymen see only the jobs assigned to them, and some notes are visible to management only.

The conversation in the resident portal. Everyone on your building’s staff who can open your request can read its conversation, photos included, and can see when you have read their replies and whether an update email was sent to you. Your building chooses who among them may answer you. Other residents never see your requests or your messages.

Anyone who has your status link. The link you get when you file is the key to your request’s page. Whoever has it can see the request and add to it, so keep it to yourself. For a request you filed on the form, it stops working 90 days after you file.

If you work for a building: people at your building’s management company who use LUCAS can see your name and role, and anyone who can open a job can see your work on it. Every performance figure your managers see about you, you can see too, but some notes and reviews about your work are visible to management only. A tenant whose repair you are assigned to sees your name, job title and photo on their status page, and the message telling them who is handling it includes your name. Feedback you send with the feedback button comes to us, not to your building’s management. If you answer residents in the resident portal, a resident sees your name and your role, not your job title, beside each of your replies and in the update email about it; the people who can open the job see your replies, and who marked a resident’s message as read.

Service providers

These companies run parts of LUCAS for us, and may use the information only to provide their service to us:

  • Amazon Web Services (AWS) hosts our servers, our database, our backups and the photos sent in the resident portal.
  • Cloudflare runs our domain name system and carries traffic between your browser and our servers.
  • Twilio sends our text messages and passes your replies back to us.
  • Resend sends our emails, such as sign-in links and updates about your requests, and receives the address and the content of each email only to deliver it.

Tools you or building staff choose to use

Dictation. The microphone button uses your browser’s own speech recognition. Some browsers, including Chrome, Edge and Safari, may do that on their maker’s servers, so while the microphone is on your voice may be sent to Google, Microsoft or Apple under their own privacy terms. Nothing is sent until you press the button, and we receive only the text.

Translation. If building staff cannot read the language your request is written in, they can choose to open its description in Google Translate, which sends that text to Google.

When the law requires it

We will disclose information when the law requires us to, for example to answer a valid court order.

Text message opt-in data

All the above categories exclude text messaging originator opt-in data and consent; this information won’t be shared with any third parties.

Text messages

Texts are optional. We text you only if you check “Text me updates about this work order” on the repair request form, and only about that request: that we have it, who is handling it, when a visit is booked, moved or cancelled, and, once the work is done, a link to a short survey. We never send marketing.

If you work for a building, we text you only if you turn on text alerts on your Profile page and confirm with the code we text you, and only the alerts you picked about your own work: a new emergency, a job assigned to you or taken off you, a visit on your job moved or cancelled, an approval waiting for you, a report that someone couldn’t get in, or a resident waiting for your answer. We never send marketing.

We use your agreement to receive texts only to decide whether to text you about your request, and we keep it as the record that you agreed. We never sell your mobile number or that agreement, and never share them with anyone for marketing or promotional purposes. Twilio, which delivers our texts, receives your number only to deliver them.

If building staff turn on text alerts, your request’s reference and apartment, the kind of problem, the time of a visit and the fact that you sent a message may be texted, through Twilio, to the building staff working on it. Your name, your number and what you wrote never are.

The people handling your repair can see on its page whether texts are on for it, only so they know how you will hear about the repair. This is part of handling your request, not sharing.

If you work for a building and turn on text alerts, your resident manager can see your replies to them, can turn your alerts off at your request, can see how many people get each kind of alert, and can see each staff alert’s kind, job and time, and whether it was delivered or held back and why, only to run the building’s work. This is not sharing.

Message frequency varies; most requests get 4 to 6 texts. Message and data rates may apply. Reply STOP to any text to stop them, or HELP for help. You can also email us at [email protected]. Stopping texts never affects your repair request.

Staff alerts are never more than 5 texts an hour (only an alert about a new emergency can go past that) or 20 a day to one phone, and they can come at any hour, day or night. Staff can also turn them off on their Profile page, or ask their resident manager to.

The full terms, including every reply that stops texts, are in our SMS Terms of Service for LUCAS repair updates.

Cookies and storage on your device

We set three cookies, and all three are needed for the site to work:

  • couwed_session keeps building staff signed in, for up to 30 days. It is set only when someone signs in to a staff portal; tenants and visitors never get it.
  • lucas_resident keeps residents signed in to the resident portal, for up to 30 days. It is set only when a resident signs in with a link from their email; staff and visitors never get it.
  • couwed_lang remembers the language you pick, for up to a year.

We use no advertising or analytics cookies.

The repair request form also saves your answers in your browser’s storage as you go, so a dropped connection does not lose them. That draft stays on your device and reaches us only when you send the request. It never includes your name, apartment, phone number, photo or your choice about texts. It is deleted when you send the request, and a draft older than 7 days is no longer offered and is deleted the next time the form opens.

The resident portal keeps a message you have not sent yet, or a new request you have not finished, in your browser’s storage in the same way, never with a photo. It is deleted when you send it or sign out, and, like the form’s, a draft older than 7 days is no longer offered. The portal also notes in your browser which sign-in is in use, as a code that cannot be used to sign in, so that when you sign out your other tabs on that device stop showing your pages at once.

The staff portals keep a few display preferences in your browser’s storage too, such as the columns you chose and whether you have seen the guided tour. A reply to a resident that you have not sent yet is kept there as a draft until you send it, for up to 7 days.

How long we keep it

  • Repair requests, with their photos, notes, visits, messages (including the conversation in the resident portal) and survey answers, are kept as your building’s maintenance record. LUCAS does not delete them on a schedule.
  • Status links for requests filed on the form stop working 90 days after you file. The request itself is kept.
  • Update emails. The words of each update email are deleted once it has been sent, or once it cannot be. We keep a record of it — the address it went to, its subject line, which says what the email was about and never contains anyone’s messages, when it was sent, and whether our email provider accepted it — for as long as we keep the request it was about. Records of updates we did not email, and of emails that could not be sent, are deleted after 90 days.
  • Requests for access to the resident portal are deleted 90 days after the building declines them, or 120 days after they were made if the building never decides. An approved request is kept with the resident’s account.
  • Resident portal accounts are marked as moved out rather than deleted when a resident leaves, so the history of their requests stays accurate. A resident who has moved out can no longer sign in. Records of sign-in links are kept with the account.
  • Photos added to a message that was never sent are deleted after a day.
  • Text message records, including every STOP and START, are kept as the history of what you agreed to and when you said stop.
  • Staff accounts are switched off rather than deleted when someone leaves, so the record of the work they did stays accurate.
  • Form drafts on your device are deleted as described under cookies and storage.
  • Web server logs are rotated automatically as they fill, and the oldest files are deleted.
  • Backups. We back up the database every night so we can recover from a failure. Each backup is kept for a limited time and then deleted, so something removed from LUCAS can remain in a backup until that backup expires.

To ask us to delete something sooner, see your choices and rights.

How we protect it

Every page and form on LUCAS uses an encrypted connection (HTTPS). Staff passwords are stored only as hashes. Only people we authorize can reach our database. Staff see only what their role allows: handymen see only the jobs assigned to them, and notes marked for management are hidden from them. Status links for requests filed on the form expire. Resident portal sign-in links work once and expire after 15 minutes, or after 7 days for a link the building sends (an invitation or an approval), and we store them only in a form that cannot be turned back into a working link. Update emails never contain a sign-in link or a status link. Photos sent in the resident portal are re-saved on the device before they leave it, which removes where they were taken and other hidden details; they are kept in private storage and shown only through links that work for one minute, after a check of who is asking. The keys that let LUCAS send texts are kept apart from the database.

No system is perfectly secure, so we cannot promise that information will never be exposed. If we learn of a breach that affects your information, we will tell the people affected as the law requires.

Your choices and rights

Texts. Reply STOP to any text, or email us, and the texts stop. Your repair request is not affected.

Update emails. Turn off emails about your requests in Profile in the resident portal, or with the link at the end of any of them; your email app may also offer an unsubscribe button. Sign-in links, and the notice we send if the building office changes your sign-in email, still come. Turning these emails off never affects your requests or your texts.

Your portal account. You can change the portal’s language in Profile. Your name, email address, phone number and apartment are your building’s record of you: ask your building to correct them.

Correcting your request. While your request is still waiting to be assigned, you can change the description, the access details and your contact details yourself, from your status link. After that, send a message from the same page and the people handling it will see it.

Seeing, correcting or deleting your information. Email us at [email protected]. We may need to confirm that the information is yours first, for example by contacting the phone number on the request. A repair request is also your building’s maintenance record, so we may need to involve your building’s management before changing or deleting one, and some of it may have to be kept. If so, we will tell you what and why.

If you work for a building. You can change your name, phone number, job title, photo, password and text alerts on your Profile page. For anything else, ask your building’s management or email us.

Depending on where you live, the law may give you other rights over your information. You can use any of them by emailing us, and we will not treat you differently for doing so.

Children

LUCAS is meant for adults: tenants, residents and the people who work in their buildings. It is not directed at children under 13, and we do not knowingly collect personal information from them. If you believe a child under 13 has given us information, email us at [email protected] and we will delete it.

Changes to this policy

When we change this policy, we post the new version on this page and update the effective date at the top. We will not start using your mobile number for anything new without asking you first.

Contact us

Questions about this policy, or about your information, go to Couwed Inc (LUCAS), 301 W 45th Street, New York, NY 10036, or [email protected].