Privacy Policy

This Privacy Policy explains how 1602637 BC Ltd., operating as Fylely ("we," "us," or "our"), collects, uses, discloses, and protects personal information in connection with fylely.com (formerly luminoussocial.com) and the fiduciary workspace software available through it (the "Service"). We are a British Columbia, Canada company, and we handle personal information in accordance with the Personal Information Protection and Electronic Documents Act (PIPEDA) and, where it applies, British Columbia's Personal Information Protection Act (PIPA).

This policy applies to visitors, trial users, and paying customers of the Service. It does not apply to third-party sites you may reach through links on our site.

1. Information We Collect

Information you give us directly

• Account information: email, account credentials, optional name and firm details, your confirmation that you are 18 or older, and agreement timestamps. We do not collect a date of birth for signup.
• Matter records you enter: the estate or guardianship data you choose to store — deadlines, documents and document metadata, asset and account information, beneficiary and interested party contact details, creditor claims, ledger entries, hearings, time entries, invoices, expenses, notes, care-log entries, client-roster information, the names and email addresses of people you give a sign-in to a matter, and the messages your firm and those people exchange in the Service, with any files attached to them. When one of those people is co-counsel, we also keep their firm and, if you add it, their bar number, and record when they last opened the matter and which of its documents they opened; they see only the parts of the matter you choose for them, and a note only when you share that note with them. Messages your firm's own people send each other in Firm chat are kept the same way and are shown only inside your firm: a conversation to the people in it, and a matter's discussion to those at the firm who can open that matter.
• Billing information: processed directly by our payment processor, Stripe. We do not collect or store full payment card numbers ourselves.
• Support communications you send us by email.
• Files you send us to prepare an import, if you use “Send us the files” under Settings → Import: the exports from the system you are leaving, which hold your clients' and matters' information. They are kept in your firm's private storage, opened by people at Fylely only to prepare files for you to import, and deleted when the request is finished, declined or withdrawn. The files we prepare stay with the request for you to download until you delete them there or withdraw it.

Information collected automatically

• Technical and log data needed to operate and secure the Service: IP address, browser and device information, timestamps, and error/diagnostic reports.
• Cookies: strictly necessary ones that keep you signed in and operate the Service, and preference cookies that remember a choice you make, such as a tip you skipped. See our Cookie Policy for detail — we do not use advertising or analytics cookies.
• Use of the workspace: when someone at a firm does certain things in the signed-in workspace, such as opening it for the first time that day, adding a matter or a date, inviting a colleague or starting a subscription, we record which thing happened, when, and the account and firm, in our own database. We never record a matter's or client's name, an email address or a date's title this way, and no cookie or third-party tool is involved. It tells us whether firms keep using the Service and where people get stuck.
• Visits to our public pages (the homepage, pricing, the free calculators, guides, comparison and practice-area pages, help and these policies — never the signed-in workspace). We count these ourselves, with no cookie and no third-party script. For each visit we keep the page's path (never its query string), a source label when the link you followed carried one (?ref= or utm_ tags), the hostname of the site that linked to us, and the two-letter country code our hosting provider attaches to the request. To count distinct visitors in a day without keeping anyone, your IP address and browser string are hashed on our server with a random salt that is deleted the next day; neither the address nor the browser string is stored, and a hash cannot be matched to anyone once the salt is gone. If your browser sends Global Privacy Control or Do Not Track, the visit is not counted at all. Crawlers are not counted. These totals tell us how many people reach the site and from where; they are not linked to any account or firm.

Some matter records you choose to enter (for example, financial account information connected to an estate) can be sensitive. We ask that you enter only what the matter genuinely requires and avoid storing full government identification numbers or unrelated third-party sensitive data where a shorter reference would do.

Connected email and calendar accounts. If a user chooses to connect their Microsoft Outlook account, we receive an access credential for that account and may read messages in the mailbox, write calendar events into it, and send messages at the user's request. If a user chooses to connect their Gmail account, we receive an access credential that lets us send messages from it at the user's request and tells us the account's email address; it does not let us read the mailbox. If a user separately chooses to connect their Google Calendar, we receive an access credential that lets us add, change and remove the matter-date events we put in their primary calendar, and read those events back to see whether the user moved or deleted them, so that a date moved there can update the matter; we do not read the other events in it. If the firm turns on video links for booked consultations, the same permission is used to put each confirmed consultation in the firm owner's Outlook or Google Calendar as a Microsoft Teams or Google Meet meeting, with the prospect's name and the time; the meeting's join link is kept with the booking and sent to the prospect, and cancelling the booking removes the meeting. A user booking a meeting on a matter can ask for the same, made in their own connected calendar, with the meeting's title, time and matter; deleting the meeting removes it. We process this content only to provide those features — filing correspondence against a matter, showing it in the Service, keeping matter dates in the calendar, and making consultation meetings. Outlook mailbox content is read when the user opens it and is not copied into the Service except for a message or attachment the user chooses to file to a matter. If the user also allows OneDrive, the same connection can list and read the files in their OneDrive, and a file is copied into the Service only when the user chooses it for a matter. If the user uses “Edit in Word” on a matter document, Microsoft gives Fylely write access to their OneDrive; we use it only to put a copy of that document in a Fylely folder of their own OneDrive so Word can open it, and to read that copy back. The edited copy is filed back into the Service only when they choose to bring it back, and the copy in their OneDrive is theirs and is not removed by Fylely. We do not change or delete their other files. If the user adds Teams chat, the same connection can read and send messages in their own one-to-one and group Microsoft Teams chats (not team channels). The names of the people in each chat and the text of its messages are copied into the Service about every 15 minutes so the user can read and reply there; files, pictures and cards are not copied. These copies are visible only to that user, including when they file a chat to a matter, and are deleted when they turn Teams chat off or disconnect the account. A reply is sent to Teams only when the user presses Send. The same applies to the Outlook add-in: it reads the message open in Outlook only when the user files it. The Word add-in reads the document open in Word only when the user saves it to a matter, and writes into that document only what the user inserts and a reference to the matter document it was saved as. A message the user schedules through Outlook is kept, visible only to that user, until it goes at the time they chose, and afterwards so they can see that it went; presets they save are kept the same way. A message the user sends through Gmail from the Service is kept, visible only to that user, so they can find it again, and is filed to a matter if they choose. Credentials are stored encrypted, are accessible only to the user who created the connection, and are deleted when that user disconnects the account.

Google user data. Fylely's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Data received through Gmail access is used only to send the email the user asks to send; it is not used for advertising, not sold, not used to train artificial-intelligence or machine-learning models, and not read by people at Fylely except with the user's express permission, where needed for security, or where the law requires it.

Clio. If a user chooses to connect their own Clio account, we receive an access credential that acts as their Clio user. We use it to read the firm's matters, contacts, time entries and expenses from Clio only when that user asks to bring them into the import page, where nothing is saved until they confirm, and time brought in this way is never sent back to Clio; to copy the documents on a Clio matter onto the matching matter here only when that user asks; to read their own name, email address and calendar; and, only if they turn it on, to put the firm's court dates and deadlines in their Clio calendar, and to send the time entries they record to the Clio matter with the same matter number. Nothing read from Clio is used to train any model. The credential is stored encrypted, only that user can see or remove the connection, and it is ended at Clio and deleted when they disconnect; what was already sent stays in the firm's Clio account.

Files from Google Drive, Dropbox and Box. A user copying files into a matter from their own Google Drive or Dropbox chooses them in that company's own window, and we receive only the files chosen: Google gives a permission that opens only those files and lasts an hour, which we use for that copy and do not keep, and Dropbox gives a download link for each file that lasts four hours. For Box, the user signs in to Box and chooses files in the Service; the sign-in is kept, encrypted, in a cookie in their browser for the hour Box allows, and is not stored by us. Each copied file is then a matter document like any other. Google user data received this way is used only to copy the chosen files, under the Google API Services User Data Policy described above.

Connected accounting. If the firm owner connects the firm's QuickBooks Online company, we receive an access credential for it and use it only to create, in that company, a customer for each client invoiced and each invoice and payment the firm records, and to read back only what that needs: the company's name and home currency, its products and services, its invoice-numbering setting, whether a customer of the same name exists, and a record's version before voiding or deleting what Fylely sent. The credential is stored encrypted, only the firm owner can see or remove the connection, and it is revoked with Intuit and deleted when the owner disconnects.

If the firm owner connects the firm's Xero organisation instead, the same applies with Xero: we create a contact for each client invoiced and each invoice and payment the firm records, and read back only the organisation's name, base currency and short code, its chart of accounts, whether a contact of the same name exists, and whether Fylely already created an invoice with the same reference. Nothing read from Xero is used to train any model. The credential is stored encrypted, only the firm owner can see or remove the connection, and the connection is removed at Xero and the credential deleted when the owner disconnects.

Text messages. If the firm owner asks Fylely for a texting number, we open a Twilio subaccount for the firm under our own Twilio account, buy a toll-free number in it, and send Twilio the business details the owner enters (the firm's legal and trade name, website, EIN, address, and a contact person's name, email and phone) for the toll-free verification US carriers require; we keep those details so the owner can correct a rejected request, and publish the firm's name, website, city and number on a page that shows Twilio's reviewers how the firm asks clients' permission to text them. If instead the firm owner connects the firm's own Twilio account, we store its Account SID and Auth Token (the token encrypted, and never shown again). Either way we use the account only to send the texts people at the firm choose to send to their clients, to check, when they are saved, that Twilio accepts them, and to check that a reply really came from Twilio. Fylely texts a client only at a number the firm has recorded the client agreed to be texted at, and keeps a record of each text: the number, the words, who sent it and what Twilio answered. Replies go to the firm's Twilio number. With a number from Fylely, or if the firm owner points the firm's own number's incoming messages at Fylely, we receive and keep the texts people send to it: the number they came from, the words, when, and whether it was STOP, START or HELP. When a court date reminder text asks the client to reply YES to confirm and they do, we record that reply as the client's confirmation of that date and show it to the firm. Pictures and files sent with a text are not fetched or kept. Those texts are seen by people at the firm, and the notification that one arrived names the contact or the last four digits of the number, never the words. They stay until the firm's account is deleted. Only the firm owner can set up or stop texting.

Consultations booked on a firm's booking page

If a firm turns on consultation booking, anyone with its booking page link can book a consultation without an account. We collect what they enter: their name, an email address and/or a phone number, optionally what the matter is about and a short note, and the time they choose. It goes to that firm, as an enquiry in its Potential matters and a consultation on its calendar (and in the calendar the firm syncs or subscribes to, with the person's name and the time only). We hold it on the firm's behalf as its service provider and use it for nothing else. The person's IP address is used to limit abuse: only a one-way fingerprint of it is stored, with the time, and not with the booking.

If they give an email address, we send it at most two emails about that booking, in fixed wording that never repeats what they wrote: a confirmation (when the firm confirms the booking, or at once if the firm confirms bookings straight away), and a cancellation if the firm cancels a booking it had confirmed. A confirmation sent at once, without anyone at the firm involved, goes to an address at most once a day and from a firm at most 20 times a day; past that, none is sent. Nothing is sent to an address the firm has marked as not wanting automated email. The booking page shows the person a link to see or cancel their booking; we keep only a one-way fingerprint of that link.

Fee quotes

When a firm emails someone a fee quote, we store the quote and the name and email address the firm sent it to, which may be a person who is not yet the firm's client. When that person accepts the quote from its link, we record the name they type, the sentence they tick (with the total in it), the time, the IP address and browser they accept from, and a fingerprint of the quote as it was shown, so the firm has a record of what was agreed. If they decline, we record when, and any reason they choose to give. Accepting a quote charges nothing.

Questions you choose to share from Ask

Ask's built-in mode answers questions on your own computer and sends nothing. Two things do send. One is Ask Claude, if your firm's owner has switched Claude on: what you ask Claude goes to Anthropic, as Section 4 describes. The other is "Help improve Ask", which is off unless you turn it on. If you switch it on on the Ask page, and your firm's owner has not turned sharing off for the firm in Settings, we receive a question when Ask could not answer it, or when you mark its answer wrong. Nothing else you ask is sent to us.

Before the question leaves your computer, Ask removes what it can recognise:

• names that appear in your firm's records (matters, clients, colleagues, parties and counsel, judges, courts and places) become labels such as [MATTER], [CLIENT] and [PERSON];
• every amount and number becomes [AMOUNT] or [NUMBER], and every email address or link becomes [EMAIL] or [LINK]; and
• any word that is neither in Ask's own vocabulary nor in a standard English word list becomes [NAME] or [WORD]. Our server repeats this step before anything is stored.

For example, "what's owed on the Whitfield estate over $5,000?" is received as "what's owed on the [MATTER] estate over [AMOUNT]?". Ask shows you, under the answer, exactly what was sent. We store that text, whether Ask missed it or you marked it wrong, when it arrived, and which account and firm it came from, so that it can be deleted when you or your firm stop sharing. We never receive your records, the answer Ask gave, or the question as you typed it.

This removal is automatic and cannot be perfect. A name that is also an ordinary English word (for example "rose") may be kept if it is not in your records and is typed without a capital letter. Turn sharing on only if your professional obligations and engagement terms allow it, and do not type details you would not want us to read.

Meetings taken down as text

If someone at your firm uses "Take it down as text" in court or meeting mode, their own browser turns the words into text on their device, no audio is kept or sent to us, and the text is stored with that session on the matter, inside your firm's records and in your firm's export.

Where you go after a search finds nothing

This is also off unless you turn it on ("Help improve search", in Settings or under a search that found nothing), and your firm's owner can turn it off for everyone in the firm in Settings. While it is on, when a search in the Service finds nothing and you open a different page within two minutes, we add one to a count for that day: which search box it was, and which page you opened, named from the Service's own list of pages (for example "Trust ledger" or "An estate: Assets").

Your browser sends a count on its own, to a fixed address, with only the search box and the page's name: we never receive what you typed, which matter or client the page was about, or the page's address with it. A count is sent while you are signed in, so that we can check both switches, but who sent it is not stored. A count records no account, firm, device or time of day, so it cannot be traced back to you or your firm.

Until you open that next page, your browser keeps a note of which search box it was, the time, and the page you searched from (its address without any search words), in its session storage for that tab only. The note never leaves your browser. It is removed when the next page is counted or after two minutes; if you leave Fylely in that tab sooner, it is removed when you come back to Fylely there, or when you close the tab. No cookie is used.

Bug reports you send

When you use Report a bug, we receive what you write in it, the page you name, your email address, your firm, the time, and your browser's user-agent string (the browser and device type it reports). The form asks you not to include client names or confidential details. People at Fylely read each report to find and fix the bug, and may email you about it. If we confirm it, we record the discount on your firm's subscription with Stripe (Section 4). Everyone at your firm can see the firm's reports, who sent each one, and what we decided.

2. How We Use Information

We use personal information to:

• Provide, maintain, and secure the Service, including generating the reports, exports, and read-only share links you request, and the signed-in view and private messages for people you name on a matter;
• Create and administer your account, and authenticate you when you log in;
• Process subscription payments and send billing-related communications through Stripe;
• Send the deadline-digest email if and while you enable it in Settings, and other service-related notices (for example, a password reset or a security notice), including telling a person you named on a matter that your firm has sent them a message (the email says a message is waiting and how many files are attached, not what it says, and never carries the files);
• Respond to support requests, and prepare import files from exports you send us for that purpose (Section 1);
• Improve Ask, if you choose to share questions from it (Section 1). People at Fylely read shared questions to find what Ask gets wrong, and may rewrite them, with made-up names, as examples that Ask is trained and tested on. Those examples become part of Ask for every customer. They contain nothing from your records and are not linked to you or your firm;
• Improve how the Service is organized, if you choose to let us count where you go after a search finds nothing (Section 1). People at Fylely read the counts to see what people look for and cannot find;
• Find and fix bugs you report, and apply the discount for each one we confirm (Section 1);
• Send promotional messages only when you separately opt in; each promotional message includes an unsubscribe link;
• Detect, investigate, and prevent fraud, abuse, and security incidents; and
• Comply with legal, tax, and accounting obligations.

We do not sell personal information, and we do not use the content of your matter records to train public or third-party AI models. Ask's own model is trained only on examples we write, including those we write from questions people choose to share. Nothing is sent to an outside AI service unless your firm's owner switches on Claude in Settings. Then only what someone at the firm asks Claude about is sent, to Anthropic, which by default does not train its models on it; the security page (section 9) says exactly what each request sends. Where a request concerns a matter, a record of what Claude read and what it wrote is kept on that matter, with your firm, and is in your firm's export.

3. Consent

By creating an account you consent to the collection, use, and disclosure of personal information as described in this policy, to the extent required by applicable law. Where the law requires express consent for a particular use (for example, sending you promotional email under Canada's Anti-Spam Legislation, CASL), we obtain it separately and you can withdraw it at any time — see Section 8. You can withdraw consent for non-essential processing at any time by contacting us, subject to legal or contractual restrictions and reasonable notice; withdrawing consent for information we need to operate your account (for example, your login email) may mean we can no longer provide the Service to you.

Sharing questions from Ask is a separate choice. It is off until you turn it on, and you can turn it off on the Ask page at any time, which also deletes what you have shared. Your firm's owner can turn it off for everyone in the firm in Settings.

Counting where you go after a search finds nothing is a separate choice too. It is off until you turn it on, and you can turn it off in Settings at any time. Because a count is not linked to you, turning it off stops new counts but cannot pick out ones already made; they are deleted as Section 6 describes. Your firm's owner can turn it off for everyone in the firm in Settings.

4. How We Share Information

We share personal information only as needed to run the Service, and never sell it. We share information with:

• Service providers (subprocessors) who host, run, or support the Service under contract, currently:
  • Supabase, Inc. — database, authentication, and file storage;
  • Vercel Inc. — application hosting and content delivery;
  • Stripe, Inc. — payment processing;
  • Resend — transactional and deadline-digest email delivery.
  • Microsoft — mailbox content, recipients and calendar entries when you connect Outlook and use those features; and, if you also allow OneDrive, the files you copy into a matter and the copies Edit in Word places in your OneDrive; and, if you add Teams chat, the names of the people in your Teams chats and the text of their messages.
  • Google — the messages you send, and their recipients, when you connect Gmail and send from it; and your matters' hearings, court dates, deadlines and dated tasks when you connect Google Calendar.
  • Anthropic, PBC — only while your firm's owner has switched on Claude: the question and the records Claude reads to answer it, which are the matters, deadlines, contacts and invoice totals and, as far as the asking person's role allows, matter notes, family messages, the text of documents (never one marked privileged or internal), time entries and trust balances; for a drafted reply, that family conversation, the names in it and the matter's coming dates; for a summary, that document's text and file name; for “Fill from this document”, the same, that one document's text and file name; for a letter, email or memo from “Write with Claude”, what the person typed and the matter's facts listed under the draft (its details, its people, with an address only for the person written to, its coming dates and, on an estate, accounts by their last four digits, assets, claims and ledger totals); for suggested bill wording, each flagged time entry's description, date and length, the matter's name, the first name of the person who logged it where we hold one, and the titles and first lines of that day's records on the matter, never the hourly rate or the amount billed; for “Describe the report you want” on Reports, what the person typed and the list of report columns their role may use, never the firm's records; for an attendance note drafted with Claude in court or meeting mode, the matter's name, that session's title and times, its notes and its transcript. By default Anthropic does not train its models on what businesses send it.
  • Twilio — when the firm owner sets up texting: the mobile number and the words of each text someone at the firm sends to a client, sent through a subaccount Fylely opens for the firm under our agreement with Twilio, or through the firm's own account under its own agreement; for a number from Fylely, the firm's business details for toll-free verification; and Twilio sends us the texts clients send back to the firm's number (for the firm's own account, if the owner sets it up).
  • Intuit — when the firm owner connects QuickBooks Online: clients' names and email addresses, and the invoices and payments sent to the firm's own QuickBooks company, which the firm holds under its own agreement with Intuit.
  • Xero — when the firm owner connects Xero: clients' names and email addresses, and the invoices and payments sent to the firm's own Xero organisation, which the firm holds under its own agreement with Xero.
  • Clio (Themis Solutions Inc.) — when a user connects their own Clio account and turns sending on: the firm's court dates and deadlines, with the matter's name, and that user's own time entries, sent to the firm's own Clio account, which the firm holds under its own agreement with Clio.
  Each is contractually restricted to using personal information only to provide their service to us.
• People you choose to share with — a read-only share link you create is only accessible to someone who has the link, and you can revoke it at any time from the matter it belongs to. A person you name on a matter signs in with a code sent to their own address, sees only that matter, and can exchange private messages with your firm, with files attached; you can remove their access at any time, and their messages stay with the matter as part of its record. A file they attach is kept in your firm's private storage as a document on that matter, marked as received from them. They can open only the files in their own conversation with your firm, and never a document your firm marks privileged or internal. A personal-items link you send a beneficiary shows them only the items still to be divided (with any photos and, if you choose, values you entered), the items already set aside for them, and their own wish list; it never shows what anyone else asked for or received, and you can turn it off at any time.
• A successor lawyer a firm owner names — if the owner sets up a continuity plan and the lawyer they named asks for access, and the owner does not refuse within the waiting period they chose, that lawyer can read a summary of the firm's open matters, each client's name, email and phone, overdue dates and dates in the next 90 days, the responsible lawyer and each client's trust balance, using a code emailed to them each time, for 30 days, with every request and view logged with its IP address and emailed to the owner, who can end it at any time.
• Legal and safety disclosures — we may disclose information where required by law, court order, or valid legal process, or where necessary to protect the rights, property, or safety of Fylely, our customers, or others.
• Business transfers — if we are involved in a merger, acquisition, or sale of assets, personal information may be transferred as part of that transaction, subject to this policy or a policy providing at least equivalent protection.

5. Cross-Border Data Transfer

We are based in Canada, but the infrastructure providers listed in Section 4 store and process data primarily in the United States (our database is hosted on Supabase infrastructure in the AWS us-east-1 region, in Virginia, USA). This means personal information about you may be accessible to those providers, and to courts, law enforcement, or regulators, under the laws of the United States, which may differ from Canadian law. We select providers with strong contractual and technical safeguards and do not transfer personal information internationally for any purpose beyond operating the Service.

6. Data Retention

Use Delete your data for self-service deletion instructions and retention limits. Deletion removes live workspace records and files, stops billing, and removes the owner’s login. Recipient copies, legally required payment records, and provider backups or security logs have separate retention limits.

We retain matter records for as long as your account is open, or until you delete the specific record. You can close a matter, delete rows you added, or request deletion of your entire account by emailing cole@fylely.com. We retain billing records for as long as required by tax and accounting law (in Canada, generally six years), and may retain limited technical logs for a shorter period for security purposes even after account deletion.

One of those logs is a security log: sign-ins and refused sign-ins, and changes to sign-in codes, authenticator apps, the team, share links, exports and connected accounts, each with the email of the person, the time, the IP address and the browser. It helps us and your firm's owner spot and investigate misuse. The owner can read your firm's part of it in Settings. Entries cannot be edited, and each is kept for 400 days, including after an account is closed. Encrypted backups of the Service, where they exist, are kept for no more than 30 days.

Questions shared from Ask (Section 1) are deleted 90 days after we receive them. They are deleted sooner: yours when you turn off "Help improve Ask", all of your firm's when the owner turns sharing off for the firm, and with your account or firm when either is deleted. Examples we have already written from them (Section 2) are not linked to anyone and are kept.

Counts of where people went after a search found nothing (Section 1) are deleted 90 days after the day they count.

Bug reports (Section 1) are kept while your firm's account is open, so we can tell when a later report is the same bug, and are deleted with the firm's account. A report stays with the firm, with the sender's email, if the person who sent it later leaves the firm or deletes their own login.

7. Security

We use encryption in transit (TLS) and at rest for stored data, role-based access controls, and row-level database security so that one customer's matters are not accessible to another. Read-only share links are scoped to a single matter and can be revoked at any time. No system is perfectly secure, and we cannot guarantee absolute security; contact us immediately at cole@fylely.com if you believe your account has been compromised.

8. Your Privacy Rights

Under PIPEDA/PIPA, you have the right to:

• Access the personal information we hold about you;
• Correct inaccurate or incomplete information — most account fields can be edited directly in Settings;
• Withdraw consent for a use of your information, subject to Section 3;
• Request deletion of your account and associated personal information, subject to our retention obligations described in Section 6;
• Opt out of the deadline-digest email at any time from Settings, and of sharing questions from Ask at any time from the Ask page; and
• Complain to our Privacy Officer (Section 12) or, if unresolved, to the Office of the Privacy Commissioner of Canada or the applicable provincial privacy regulator.

To exercise any of these rights, contact us using the details in Section 12.

9. Cookies

We use strictly necessary cookies to operate the Service (primarily to keep you signed in), and preference cookies that remember a choice you make; no analytics or advertising cookies. See our Cookie Policy for full detail, including what we will do if that changes.

Client information can be stored on your own device in two ways. If you turn on "Keep this page on this device" on the Court day page, a copy of that page is kept on that device so it can be read without a signal. It is deleted when you sign out or turn the setting off, and a copy older than 7 days is never shown and is deleted the next time Fylely opens. And Ask keeps what you type into it in your browser: the conversation in that tab until you clear it or close the tab, and phrases you teach it until you clear them. Neither is removed when you sign out, so clear them on a computer other people use. The Cookie Policy (sections 2a and 2b) lists everything the Service keeps on a device, and fylely.com/app explains how to remove it.

10. Children's Privacy

The Service is intended for use by adults acting in a professional capacity and is not directed to children. Account holders must be 18 or older, which they confirm in the box they tick to agree to the Terms when they sign up; we do not ask for a birth date. If a child has created an account, contact us so we can investigate and delete improperly collected data. Professional users may enter information about minors when necessary and lawful for a guardianship or other matter; they are responsible for their authority to provide that information.

11. Changes to This Policy

We may update this policy from time to time. If we make a material change, we will provide reasonable notice (such as an email or an in-app notice) before it takes effect. The "Last updated" date at the top of this page reflects the most recent version.

12. Contact / Privacy Officer

Our designated Privacy Officer can be reached at cole@fylely.com for any question, request, or complaint about this policy or how we handle your personal information.

1602637 BC Ltd., operating as Fylely. British Columbia, Canada.