Privacy Policy

1. Who we are

• Legal name: LFKA DEV TECNOLOGIA LTDA
• Company ID (CNPJ): 60.825.050/0001-30
• City: Ourinhos / SP — Brazil
• Website: https://aufisoft.com
• General contact: contact@aufisoft.com

2. Data Protection Officer

• Officer: Luis Andriolo
• Email: privacy@aufisoft.com
• Alternative channel: dpo@aufisoft.com

The Officer receives your complaints, provides clarification and takes action (Art. 41, §2 of the Brazilian General Data Protection Law — LGPD).

3. Who this policy speaks to

Aufisoft is a restaurant management system, installed on the restaurant's computer and sold as a one-time-payment license, with remote access as an optional feature, subscribed to separately. That creates four different relationships, and the rules are not the same in all four. Find yours:

3.1 You buy Aufisoft or have an account at aufisoft.com

Whoever creates an account at aufisoft.com to buy the license, additional machines or a computer replacement, to subscribe to remote access and to follow their own licenses — usually the restaurant owner.

We are the controller of your account and purchase data. This policy applies to you in full.

3.2 You visit aufisoft.com

We are the controller. Sections 6, 7, 9 and 10 apply.

3.3 You are a customer of a restaurant that uses Aufisoft

You placed an order through the online menu, or the restaurant registered you in their system.

In this case the controller of your data is the restaurant, not Aufisoft. They decided to collect your data and for what purpose, and it stays on their computer, where Aufisoft has no access — even when the restaurant uses remote access, which only carries the traffic (see 5.1). The only exception is the support access, which exists only if the restaurant turns it on so a problem can be looked into (see 4.10). When you place an order through the online menu, the order passes through our cloud until it reaches the restaurant's computer: on that leg we handle your data only for the restaurant and on their behalf — the LGPD calls this a processor (Art. 39).

In practice, this means:

• To exercise your rights, contact the restaurant. Their contact details are on the online menu and on the receipt.
• If you write to us anyway, we will forward it to the restaurant within 2 business days and let you know. We will not ignore you — but we also cannot decide about data we do not control.
• The system gives the restaurant the technical means to serve you.

Section 5 describes the data that stays with the restaurant.

3.4 You work at a restaurant that uses Aufisoft

Manager or staff member with a user in the system installed at the restaurant.

Your user, your password and what you record in the system stay on the restaurant's computer. The controller is the restaurant, and Aufisoft has no access to that data, nor does it store it when the restaurant uses remote access. The exception is the support access, which the restaurant may turn on (see 4.10): then the Aufisoft team sees the system on screen, without storing anything. To exercise your rights, contact the restaurant. If you also have an account at aufisoft.com, item 3.1 applies to it.

4. Data Aufisoft keeps — and why

This section applies to those with an account at aufisoft.com (3.1). For each purpose we state the data, the reason, the legal basis and how long we keep it.

4.1 Account and access

• Data: name, email, password (stored encrypted, never in readable form) and the date you confirmed your email. If you provide them under "My details", also phone and tax ID (CPF or CNPJ) — both are optional
• Purpose: create and operate your account, and identify you when you ask for support. For that, the Aufisoft team looks at this data in an internal panel (see 4.11)
• Legal basis: performance of a contract — Art. 7, V
• Retention: for as long as the account exists. On deletion we anonymise this data (see 4.12)

4.2 Codes sent by email

• Data: email, a 6-digit code and the number of attempts. The code is requested at sign-up, at every login and for password recovery
• Purpose: confirm the email is yours, prevent someone from entering your account with your password alone, and let you recover access
• Legal basis: performance of a contract (Art. 7, V) and legitimate interest in security (Art. 7, IX)
• Retention: 10 minutes (login) or 15 minutes (sign-up and recovery). The code is erased as soon as it is used, or at the fifth wrong attempt

4.3 Access security

• Data: IP address and browser used (user agent), date and time each session started and was last active. To limit attempts, also temporary counters per IP and per email
• Purpose: keep your session, end the others when you sign in on a new browser, and detect misuse
• Legal basis: legitimate interest in security — Art. 7, IX
• Retention: 6 months after the session ends. The counters expire within 24 hours

4.4 License purchase

• What we keep: each order — what was bought (license, additional machines or computer replacement), the restaurant name, the number of machines, the amount, the number of installments, the payment status and the dates — and the identifiers Asaas returns to us (for the customer, the payment page and the payment)
• What you give Asaas: payment is made on the Asaas page, by PIX or card. There you enter name, tax ID (CPF or CNPJ), email, phone, address and, for a card, its details. Aufisoft neither receives nor stores your card details, and does not store the tax ID or the address you give Asaas
• Team lookup: to handle support requests, the Aufisoft team sees your purchase history in an internal panel — the kind, status, amount and date (see 4.11)
• Purpose: sell the license, additional machines and computer replacements, release what was paid for, handle refunds and chargebacks, and meet tax obligations
• Legal basis: performance of a contract (Art. 7, V) and legal obligation (Art. 7, II)
• Withdrawal request: you can withdraw from the purchase within 7 days of the payment confirmation (art. 49 of the Consumer Protection Code). The request is made by email, and the account area has a link that opens it pre-filled during those 7 days. We handle the email of the Account and the request: which purchase, the date and the reason, if you wish to give one — no justification is needed. Legal basis: performance of a contract (Art. 7, V) and legal obligation (Art. 7, II). We keep the record for the same period as the purchase, below
• Shared with: Asaas Gestão Financeira S.A., which processes the payment as our processor. As a payment institution, Asaas also handles part of this data under its own financial-sector obligations, such as anti-money-laundering rules — on those points it is the controller and follows its own privacy policy
• Ad measurement (Meta), only with your consent: when the payment is confirmed, and only if you accepted the Advertising category in the cookie banner at the time of purchase, our server reports the purchase to Meta Platforms to measure how ads perform. We send the amount, the order identifier, your email, name, phone number and address (city, state and postal code), all in hashed form — an irreversible code, not the readable data — plus the IP and browser used in the purchase. We look up the phone number and address in Asaas at the moment of sending and do not keep them. The server sends this with no cookie. If you refused Advertising, no data about you is sent to Meta because of the purchase. Legal basis: consent (Art. 7, I). You can withdraw it at any time through the Cookies link in the footer: a purchase already reported is not undone, but no new purchase of yours is reported to Meta after that (see section 9)
• Retention: for as long as the license exists, plus 5 years

4.5 Proof of acceptance of the terms

In every purchase — of the license, additional machines or a computer replacement — you tick the box accepting the License and Use Terms (aufisoft.com/termos-de-licenca) before going to payment. When you subscribe to remote access, it is the box for the Remote Access Terms (aufisoft.com/termos-do-acesso-remoto), and the record is the same. At that moment we record:

• The accepted text: the terms version and the cryptographic digest (sha256) of that version's text, which proves which text it was
• When: date and time of acceptance, the moment you opened the full text of the terms and the moment you ticked the box
• From where: the IP address, the addresses the connection passed through on its way to our cloud, and the approximate location that Cloudflare, the network that protects our cloud, derives from that IP — city, state or region, postal code, country, approximate coordinates and time zone
• With what: the browser and system used (user agent), the language and time zone set in the browser, the page the request came from (origin and referer) and the Cloudflare request identifier (cf-ray)

We do not ask for access to your device's location, nor to GPS, nor for browser permission to do so. The location comes only from the IP address and is approximate — usually the city of your internet provider.

• Purpose: prove, should there be doubt or a dispute, that the acceptance happened, which text was accepted, when and from where
• Legal basis: regular exercise of rights in contracts and in judicial or administrative proceedings (Art. 7, VI) and performance of a contract (Art. 7, V)
• Shared with: Cloudflare, which derives the approximate location from the IP (see section 6)
• Retention: for as long as the license exists, plus the applicable limitation period — 5 years (Art. 27 of the Brazilian Consumer Protection Code). After that, we delete or anonymise it

4.6 The license and the activated computers

• License: the restaurant name (which you choose at purchase and can change in the account area), the license key (stored encrypted), the additional machines bought and the license status
• CNPJ: the restaurant's company ID (CNPJ) and legal name, bound to the license on the first activation, and the history of changes made by support (previous and new CNPJ, who changed it and why). To confirm the CNPJ, we query the Federal Revenue's public register through BrasilAPI — legal name, trade name, registration status, city and state — and the result stays in temporary memory for 24 hours
• Changing the license's CNPJ: the change is made only by support, at no cost, upon proof — the sale or business-transfer agreement of the restaurant, or the document of the new CNPJ. For that, support checks the new CNPJ, the legal name, the email of the Account and the supporting document, and the change is recorded in the history above. The document is handled only for that check. Legal basis: performance of a contract (Art. 7, V)
• Each activated computer: the computer name; a fingerprint of the hardware, made of cryptographic digests of the Windows, motherboard, disk and processor identifiers — no hardware value leaves the computer; the computer's public key; the Aufisoft version; the dates of activation, end and last contact; and the computer replacements
• Contact with the cloud: the computer's IP address, kept for 10 minutes
• Team lookup: to handle support requests, the Aufisoft team sees the license and main computer data in an internal panel — restaurant name, status, CNPJ and legal name, additional machines, Aufisoft version, last contact and how long the license has existed — without the full key (see 4.11)
• Purpose: issue the license and email the key, activate the computer, verify the license, bind the CNPJ printed on tax invoices and receipts, manage machines and computer replacements, and detect the use of an unauthorised copy
• Legal basis: performance of a contract (Art. 7, V) and, for detecting unauthorised copies, legitimate interest (Art. 7, IX)
• Retention: for as long as the license exists, plus 5 years

CNPJ and legal name are company data. They can be personal data when they identify a person — a sole trader (MEI), for example — and that is why they are listed here.

4.7 Online menu and iFood

• Data: the menu copy the restaurant's computer sends — the restaurant's name, phone, description, address and location, opening hours, products, prices, coupons, delivery zones, payment methods, colours and the identifiers of measurement tools the restaurant configured — and the photos; the menu address and, if any, the restaurant's own domain
• iFood: when the restaurant connects or renews its access to iFood, the authorisation codes pass through our cloud, which holds the secret of Aufisoft's app on iFood. We do not store these codes: the response is kept encrypted in temporary memory for 5 minutes, only to repeat an attempt that failed
• Purpose: publish the online menu, which works even with the restaurant's computer switched off, and connect the restaurant to iFood
• Legal basis: performance of a contract — Art. 7, V
• Retention: the 10 most recent versions of the menu; the photos, for as long as the restaurant's menu exists

Orders placed on the online menu also pass through our cloud, but they are the restaurant's customers' data: they are in section 5.

4.8 Error diagnostics

• Data: server technical logs — your account or computer identifier, the route, date and time, the error code and, in security alerts, the IP address. We do not log the content of requests
• Purpose: identify and fix failures
• Legal basis: legitimate interest — Art. 7, IX
• Retention: 30 days

4.9 Remote access

Remote access is optional and unrelated to the license: subscribing to, cancelling, suspending or losing remote access does not change the license or the right to use the installed system. It applies to whoever subscribes to it, usually the restaurant owner (3.1).

We do not store your restaurant's data. Orders, customers, finances and everything the user sees or types in remote access travel through Cloudflare, which carries the connection between the browser and the restaurant's computer, without passing through Aufisoft's servers and without being stored by us. What we do keep is only what is below:

• Connection state: an opaque identifier of the access address (which does not carry the restaurant's name), the status (on, off or blocked), the date of the computer's last signal, whether the tunnel is connected, and the technical identifiers of the tunnel at Cloudflare
• Access history: date and time, event type (access turned on or off, block, suspension, access requested, opened or refused, login to the system), the IP address and browser of whoever accessed, and the account user who requested the access. The owner sees this history in the portal
• Entry pass: the single-use pass, valid for 60 seconds, is stored only as a cryptographic digest, with the IP and browser of whoever requested it, and erased within 24 hours
• Suspension: when Aufisoft suspends access, we keep the date, who suspended it and the reason, for internal control.
• Subscription and charges: the subscription status, the paid period, the charges and the acceptance of the terms. The card details and the CPF or CNPJ entered at payment stay with Asaas
• Proof of acceptance: as in 4.5 — the accepted text, the date and the origin (IP and browser)
• Purpose: turn on, cut off and bill remote access, and give the owner security and auditing over who got in
• Legal basis: performance of a contract (Art. 7, V) and, for security and the access record, legitimate interest (Art. 7, IX)
• Retention: the connection state, for as long as remote access exists; the access history, 90 days, deleted automatically every day; the subscription, charges and proof of acceptance, for as long as the license exists, plus 5 years, as in 4.4 and 4.5
• Shared with: Cloudflare, which carries the traffic, and Asaas, which processes the billing (section 6)

The restaurant is responsible for its use of remote access: credentials, users with permission, data accessed, computer and network. As to the data accessed, the restaurant is the controller, and Aufisoft is the processor of a channel that only carries the traffic.

4.10 Aufisoft support access

Support access is an optional feature, off by default, that lets the Aufisoft team enter the restaurant's system to look into a problem. It exists only if the restaurant turns it on, at the main computer, in Settings → Remote access → “Enable access for Aufisoft support”, after reading and accepting the text the screen shows. It does not depend on the remote access subscription, and the restaurant can turn it off whenever it wants, in the same place. It applies to whoever turns it on, usually the restaurant owner or administrator (3.1).

Who enters, and how. Only members of the Aufisoft team, from a closed list, who sign in with their work e-mail and a code sent to it. Each entry lasts up to 2 hours, and there is one at a time. The person uses a support user of their own, which does not appear in the restaurant's user list. We use the access only to look into and fix a problem in the restaurant's system.

What the team can do. While the session is open, the person sees and can change what a restaurant administrator can change, such as orders, customers, finances, users and roles, always to solve the problem that led to the access. That data stays on the restaurant's computer and travels through Cloudflare, without passing through Aufisoft's servers and without being stored by us, as in 4.9. The restaurant remains the controller, and Aufisoft is the processor (Art. 39), acting only while the access is turned on.

What we keep in our cloud about the support access is only what is listed below:

• Enablement: whether the access is on, the date the restaurant turned it on and the version of the text it accepted. When it is turned off, we delete the date and the version
• Access history: date and time and the type of event (support access enabled or disabled, access requested, opened or refused). The owner sees this history in the portal as “Aufisoft support”, without the name and without the e-mail of whoever entered, and without IP or browser
• Entry pass and internal record: the single-use pass, valid for 60 seconds, is kept only as a cryptographic digest, with the work e-mail and the IP of the team member who asked for it, for internal control and audit. That e-mail is not shown to the owner or to the restaurant
• Purpose: to look into, at the restaurant's request, a problem in its system, with security and an audit trail of who entered
• Legal basis: the restaurant's consent, given when it turns the access on (Art. 7, I), and, for the access record, legitimate interest in security and audit (Art. 7, IX)
• Retention: the enablement, while the support access is on; the access history, 90 days, deleted automatically every day; the pass, within 24 hours; the internal record with the team e-mail, together with the history
• Sharing: Cloudflare, which carries the traffic (section 6)

When the access ends. The restaurant turns it off at the computer; the owner blocking remote access in the portal also turns it off; and it drops when the license is suspended or revoked or the installation ends. The end of the remote access subscription does not turn it off. To bring support access back, the restaurant switches the option on again at the computer.

4.11 Team lookup of account data

To handle support requests, the Aufisoft team looks up, in an internal panel, the sign-up data of people with an account on aufisoft.com (3.1). Only team members on a closed list, who sign in with their work e-mail and a code sent to it. The lookup is read-only: the panel does not change account data.

• What the team sees: the name, email, phone and tax ID (CPF or CNPJ) you gave when you created the account (4.1); the licenses — restaurant name, status, bound CNPJ and legal name, additional machines bought, the main machine's Aufisoft version and last contact, and how long the license has existed (4.6); the purchase history — kind, status, amount and date (4.4); and the support tickets
• What is not in that lookup: your password, the full license key, the card data and what you type on the Asaas payment page. The team also does not see the restaurant's data, which stays on its computer (section 5)
• Purpose: handle support requests — identify who asked and see the license, purchase or ticket in question — and keep the account secure
• Legal basis: performance of a contract (Art. 7, V) and, in handling support, legitimate interest (Art. 7, IX).
• Who has access: only the closed list of team members. No other employee or third party uses this panel
• Record of lookups: today these lookups are not logged one by one: we do not keep a history of who looked up which account and when. The protection is the closed list and signing in with a work e-mail and a code
• Retention: the lookup creates no copy. The panel reads the data we already keep, for the periods in 4.1, 4.4 and 4.6
• Sharing: none, beyond the section 6 suppliers that already host and protect the cloud

4.12 When you delete your account

How to ask: write to privacy@aufisoft.com. Our Officer handles the process and replies within the deadline in section 8.

We anonymise your name, email, phone and tax ID, and end your sessions.

We keep the purchase records and the proof of acceptance for the periods in 4.4 and 4.5 — and, for remote access and the support access, those in 4.9 and 4.10 —, because the LGPD allows keeping them to meet a legal obligation and for the regular exercise of rights (Art. 16, I, and Art. 7, VI).

The license does not depend on the account to work on a computer already activated. Without the account, however, nobody can see the key, buy machines or pay for a computer replacement through the account area — so, if there is an active license, we let you know before completing the deletion. If there is an active remote access subscription, we let you know as well.

5. Data that stays with the restaurant

Aufisoft is installed on the restaurant's computer, and the system's database sits on that computer. Aufisoft has no access to that database and keeps no copy of it. That also holds when the restaurant turns on remote access (see 5.1). The only exception is the support access, which the restaurant turns on at its computer (see 4.10): the team sees the system on screen, to look into a problem, and Aufisoft still keeps no copy. Here the controller is the restaurant (see 3.3 and 3.4). We list it for transparency — and so you know what the system keeps.

How long this data stays is the restaurant's decision, which must respect legal periods — tax documents, for example, must be kept for 5 years. Backups of that database also belong to the restaurant: the system writes them on the computer itself and, if the restaurant connects a Google account, to its Google Drive.

iFood orders create a customer record. When an order arrives through iFood, the system creates or updates that customer's record on the restaurant's computer, including the tax ID if provided. This is necessary for the restaurant to fulfil the order.

Order printing. Order data is sent to the restaurant's printer by the system itself, on their computer. From that point on, the data is under the restaurant's physical control.

5.1 What leaves the restaurant's computer

The system only sends data off the restaurant's computer in these cases:

For services hired by the restaurant, the data goes from their computer straight to the provider, with the restaurant's own account and key: it does not pass through Aufisoft, and the relationship is between the restaurant and that provider.

Online menu and measurement tools. Some restaurants enable analytics and advertising tools on their menu. When that happens, we ask for your consent before any tool loads. The restaurant that configured them is responsible for those tools.

5.2 Deleting a customer's data

How to ask. If you are a customer of a restaurant and want your data deleted, talk to the restaurant — they decide. You can also write to our Officer at privacy@aufisoft.com; we forward it to the restaurant within 2 business days.

The restaurant does the deletion, in its own system. Aufisoft has no permanent access to their computer — it only enters if the restaurant turns on the support access (see 4.10) — and does not delete anything there on its own. If there is data about you in online menu orders still kept in our cloud, we delete or anonymise it when the restaurant asks.

Why the invoice stays. The LGPD expressly allows retaining data to meet a legal obligation (Art. 16, I), and tax documents have their own retention period. It is neither the restaurant's choice nor ours — it is an obligation nobody can waive.

You have the right to know exactly what was deleted and what was kept, and why. The restaurant is responsible for answering; if they do not, write to privacy@aufisoft.com and we will help as far as we can.

6. Who we share with

We do not sell data. We share only with those who need to perform part of the service:

Providers the restaurant hires for its own system (5.1) are not in this table: they do not receive data from Aufisoft.

We also share when required by law, a court order or legal proceedings.

7. Where your data is

The restaurant's system lives on their computer. Customers, orders, staff and tax invoices are in that computer's database (section 5).

Aufisoft's cloud runs in Brazil. Its database — accounts, purchases, proof of acceptance, licenses, activated computers, menu copy and online menu orders — sits on a server in Brazilian territory. The restaurant's customers, orders, staff and tax invoices are not in it: they stay on the restaurant's computer.

Some data is stored or processed outside the country, and we want to be clear about what:

These transfers are made under arts. 33 to 36 of the LGPD, on the basis of standard contractual clauses in the form of ANPD Resolution No. 19/2024. All of these providers are bound by contractual data protection commitments, and we choose each one considering the safeguards they offer. Only the data necessary for the stated purpose is sent to them.

8. Your rights (Art. 18 of the LGPD)

You can:

• Confirm whether we process your data
• Access your data
• Correct incomplete, inaccurate or outdated data
• Anonymise, block or delete unnecessary data or data processed unlawfully
• Export your data in a machine-readable format
• Delete data we process based on your consent
• Know who we share your data with
• Be informed about the option not to consent and what happens if you do not
• Withdraw consent at any time

In the account area you can see and correct your name, phone and tax ID yourself, and see your licenses and your orders.

How to exercise them: write to privacy@aufisoft.com. We reply through the same channel.

Response time: up to 30 days. The LGPD sets 15 days in Art. 19, II, doubled for small processing agents by Art. 14 of ANPD Resolution 2/2022, which is our case. Simple requests we answer immediately.

If you are a customer of a restaurant or work at one, contact the restaurant (see 3.3 and 3.4).

9. Cookies and similar technologies

This section covers the site aufisoft.com — including the account area and the purchase — and each restaurant's online menu. The choice you make in the banner is stored in a root-domain cookie and applies to both — you decide once, not once per address.

The Meta Pixel loads in your browser only if you consent to Advertising. The purchase confirmation that our server sends to Meta is a separate technical path, but follows the same rule: it only happens if you accepted Advertising at the time of purchase (see below and 4.4).

In your browser, nothing beyond the essential loads before your consent. You choose in the banner shown on your first visit, and you can change it at any time through the Cookies link in the footer — which reopens the panel with your current choice, without erasing it.

Refusing is as easy as accepting — the reject button sits next to the accept button, with the same prominence. Between them there is a Customize option that opens the categories one by one. Refusing takes no functionality away from you.

Legal basis and international transfer

The browsing data handled by the Analytics and Advertising categories is processed on the basis of your consent (art. 7, I of the LGPD), given voluntarily and revocable at any time through the same footer link. Revoking does not erase what was already collected or sent — it stops collection and sending from that point on.

That data is transferred to the United States, where Google's and Meta's servers are. The transfer is made under arts. 33 to 36 of the LGPD, on the basis of standard contractual clauses in the form of ANPD Resolution No. 19/2024, signed with each supplier.

From your browser, these tools receive random identifiers generated by the cookies themselves and browsing data — in the purchase steps, the internal order identifier and the amount. We never send your tax ID.

The purchase confirmation, sent by the server

When a payment is confirmed, our server reports the purchase to Meta (section 4.4) to measure how ads perform. This sending uses no cookie, but only happens if you accepted the Advertising category in the cookie banner at the time of purchase. Anyone who refuses Advertising has no data sent to Meta. The legal basis is consent (art. 7, I of the LGPD), limited to what section 4.4 lists.

You can withdraw your consent at any time through the Cookies link in the footer. A purchase already reported to Meta is not undone, but no new purchase of yours is reported after the withdrawal. To also ask for the data to be deleted, write to privacy@aufisoft.com. The data goes to the United States, under the transfer described above.

10. Security

We adopt, among other measures:

• Cloud database in Brazil
• Encryption in transit (HTTPS/TLS)
• Passwords stored encrypted, never in readable form
• A code sent by email at every account login
• A single session per account, with the ability to end it
• License key stored encrypted; the account area shows only the last 4 characters and asks for the password to reveal the whole key
• Each activated computer signs its requests to the cloud with its own key, which never leaves it
• Each account sees only its own licenses and its own orders
• Aufisoft support access depends on the restaurant turning it on, is limited to a closed list of people who sign in with e-mail and code, lasts up to 2 hours per entry and is recorded in the owner's history
• The team's lookup of account data, in the internal panel, is limited to a closed list of people who sign in with a work e-mail and a code, and is read-only; the password, the full license key and the card data do not appear in it. These lookups are not yet logged one by one
• Incident response procedure

In the installed system, which has role and permission-based access control, the security of the computer, of the staff's passwords and of the backups is the restaurant's.

If a security incident occurs that may pose relevant risk or harm to you, we will notify you and the ANPD within the deadlines of ANPD Resolution 15/2024.

11. Children and adolescents

Aufisoft is a management system for businesses and is not directed at anyone under 18. We do not knowingly collect data from children or adolescents.

The online menu is a general-purpose service, operated by each restaurant. If you are a legal guardian and identified improper use, write to privacy@aufisoft.com.

12. Changes to this policy

We may update this policy. Relevant changes will be communicated by email to those with an account at aufisoft.com, with reasonable advance warning.

Every version gets a number and an effective date, and previous ones remain available at aufisoft.com/privacidade/v/{version}. This is version 2.3.

13. Contact us and the ANPD

• Data Protection Officer: privacy@aufisoft.com
• General contact: contact@aufisoft.com
• Brazilian Data Protection Authority (ANPD): https://www.gov.br/anpd

You may petition the ANPD at any time (Art. 18, §1), but we ask that you talk to us first — it is usually faster.

Version history

• v2.3 — 05/10/2026: the Aufisoft team's lookup of account data, in an internal panel, to handle support requests, is added. The new section 4.11 says who looks up — only people on a closed list, with a work e-mail and a code —, what the team sees (name, email, phone, CPF or CNPJ, licenses, purchases and tickets), what it does not see (password, full license key, card data and what is typed at the Asaas payment), the purpose and legal basis (performance of a contract and, in support, legitimate interest) and that these lookups are not yet logged one by one. The former 4.11 becomes 4.12. The summary, sections 4.1, 4.4 and 4.6 and section 10 follow.
• v2.2 — 05/10/2026: Aufisoft support access is added, an optional feature that the restaurant turns on at its computer, with consent, so the Aufisoft team can look into a problem. The new section 4.10 says who enters, what the team sees, what Aufisoft keeps — the enablement, the history for 90 days, visible to the owner as “Aufisoft support” without anyone's e-mail, and the pass with the team member's work e-mail for internal control — and how the access ends. The former 4.10 becomes 4.11. The summary and sections 3.3, 3.4, 5, 6, 7 and 10 follow: Aufisoft still does not store the restaurant's data, but stops saying it has no access to it when the restaurant turns support on.
• v2.1 — 04/10/2026: remote access is added, an optional feature subscribed to separately and unrelated to the license. The new section 4.9 says what Aufisoft keeps — the connection state, the access history for 90 days, the subscription and the proof of acceptance — and that it does not store the restaurant's data, which only travels through Cloudflare. The restaurant is responsible for, and the controller of, that data. The former 4.9 becomes 4.10. The summary and sections 3, 4.5, 5, 6 and 7 follow, and Cloudflare and Asaas are now also listed for remote access.
• v2.0 — 02/10/2026: reporting the purchase confirmation to Meta from the server now depends on consent: it only happens if you accepted the Advertising category in the cookie banner at the time of purchase, and the legal basis changes from legitimate interest to consent (art. 7, I), which can be withdrawn at any time. The statement that the sending did not depend on the banner is removed from the summary, from 4.4 and from sections 6, 7 and 9, and the description of the Advertising category in section 9 follows the banner. The international transfer (arts. 33 to 36 of the LGPD, standard clauses, ANPD Resolution No. 19/2024) continues. Amazon Web Services is now listed only for what it does today — the site and the installer, menu photos and the backups of the cloud database — and sections 6 and 7 say the restaurant system's database is never in them. Section 4.6 explains that changing the license's CNPJ is done only by support, at no cost, upon proof, and which data support checks. Section 4.4 now covers the withdrawal request made by email.
• v1.3 — 01/10/2026: Aufisoft now reports each purchase to Meta from the server — the amount, the order, and your email, name, phone number and address in hashed form, plus the IP and browser — without depending on the cookie banner, on legitimate interest as the legal basis with a right to object. It appears in the summary, in 4.4, in section 6, in section 7 and in section 9, which no longer says that the site loads no advertising tool and now describes the pixel, which still loads only with consent.
• v1.2 — 27/09/2026: rewritten for installable Aufisoft, sold as a one-time-payment license. The system and the data about customers, orders and staff now stay on the restaurant's computer, with no access by Aufisoft (section 5, with what leaves that computer and where to). Section 4 now describes only what Aufisoft's cloud keeps: the account, with optional phone and tax ID; the code sent by email at every login; the license purchase, with Asaas as payment processor; the proof of acceptance of the terms (4.5), which is new; the license, the activated computers and the bound CNPJ; and the menu copy. Recurring billing, the restaurant profile in the cloud, and the AI assistant and notifications operated by Aufisoft are removed. Section 3 gains item 3.4, for those who work at the restaurant; section 6 now names each provider, including Asaas and Cloudflare; and section 9 no longer mentions the admin panel.
• v1.1 — 27/08/2026: section 9 now names who operates each cookie category — Google LLC for Analytics, Meta Platforms for Advertising — states the legal basis of consent (art. 7, I) and the international transfer under arts. 33 to 36 with standard clauses in the form of ANPD Resolution No. 19/2024, and says explicitly that the admin panel is covered by the same choice. Advertising is no longer consented together with Analytics: they are two separate categories in the banner. It replaces v1.0, which was dated 01/09/2026 and was superseded before taking effect; its text remains available at /privacidade/v/1.0.
• v1.0 — 01/09/2026: full rewrite based on the actual processing inventory. It now identifies the controller, names the processors, distinguishes controller and processor roles, states retention per purpose, declares the response deadline, and aligns the text with what the system actually does.