notific.me Privacy Policy

Version 0.3 · Effective to be announced

(this box is a summary and does not replace the text)

Your account data is handled by IDIE CONSULTING TECHNOLOGY LTDA.
What a company sends you through notific.me belongs to that company: we process it on its behalf, and it is responsible for what it sends.
Your biometrics never leave your device. We only receive the signature your device produces after confirming it is you.
To prove who answered what, we record the device, IP address, time and other data for each answer. The organization that asked can see this record.
We keep each piece of data only as long as needed: content and the evidence trail follow the workspace plan’s retention period.
We do not sell personal data. We do not use advertising cookies.
Creating an account includes agreeing to receive marketing about notific.me. You can unsubscribe at any time, and we never use the content of your notifications for marketing.
To exercise your rights, write to [email protected].

1. Who we are

notific.me is provided by IDIE CONSULTING TECHNOLOGY LTDA, registered under CNPJ no. 63.210.794/0001-38, with its head office at Rua Pais Leme, 215, conjunto 1713, Pinheiros, São Paulo, SP, 05424-150, Brazil (“IDIE”, “we”, “us”).

This Policy explains how we process personal data on the notific.me website, the customer area at app.notific.me, the API at api.notific.me, the MCP server and the official apps (the “Service”), in accordance with Brazilian Law no. 13,709/2018 (General Data Protection Law, “LGPD”), Brazilian Law no. 12,965/2014 (Marco Civil da Internet) and, for people in Europe, the GDPR (section 13). Capitalized terms have the meaning given in the Terms of Use.

2. Who this Policy applies to

Users: anyone with a notific.me Account.
Members: anyone who belongs to an Organization.
Recipients without an Account: anyone who receives a notification through a link, for example by email.
Customer contacts: anyone who talks to us on behalf of a Customer (purchasing, billing, support).
Visitors to the website and documentation.

3. Who decides about each piece of data

notific.me has two kinds of data, with different responsible parties:

Data	Who is the controller (who decides)	IDIE’s role
Your Account: registration, sign-in, devices, security, billing, support and Service usage data	IDIE	Controller
What a Customer sends through the Service (events, notifications, questions, forms, files) and the answers given within its workspace, with the evidence trail	The Customer that owns the workspace	Processor: we process it on the Customer’s behalf, following its instructions

This means: if you received a notification from company X, company X decides what to send you, why, and for how long to keep it, within its plan’s options. Questions and requests about that data should go to company X first. If you contact us, we will forward the request to it.

4. What data we process

4.1. Account and identity

name and profile photo (if you upload one);
@handle;
email addresses linked to the Account (you may have several);
language, time zone and preferences (theme, notifications, who can invite you);
invitation PIN, stored in protected form (never in plain text).

access codes and links sent by email, with the requester’s IP address and the time;
sessions: browser or app (user agent), IP address, creation and expiry dates;
second factor: the authenticator app (TOTP) key, stored encrypted;
sign-in attempts and lockouts after too many attempts;
records of access to the Service (IP address, date and time), as required by the Marco Civil da Internet.

4.3. Devices

device name, platform, operating system and app version;
push token, used to wake the app;
the device’s public key. The private key is created and stored on the device itself (in its security chip, where there is one) and is never sent to us.

4.4. Biometrics: what we do not collect

When a decision requires biometrics (fingerprint or face) or the device passcode, this check is performed by your device’s operating system. We do not receive, see or store your fingerprint, your face or your device passcode. We only receive the answer signed with the device key, which the system releases after confirming it is you.

4.5. Notifications, questions and answers

the content sent by Customers: titles, text, images, links, forms, files and data from the originating system. This content may contain any kind of personal data, as defined by the Customer;
your answers: the option chosen, free text, form values;
deliveries, reads and reactions: when the notification arrived, when it was read, whether it was opened, archived, muted or ignored, and how long it took.

4.6. Evidence trail

To prove what happened to each notification, the trail records, at each step:

the person or service that acted, device, session and channel;
IP address and the approximate country and city derived from it;
browser or app, platform and time zone;
server time and the time reported by the device;
the verification level required and used;
chained hashes of the content and of previous steps (the content itself is not copied into the trail).

Precise location: when the feature is available, and only if you allow it on your device, the app may record your location at the moment you answer a decision. You can deny or withdraw the permission in your device settings at any time; in that case, only the approximate location from the IP address is recorded.

4.7. Organization and billing

legal name, tax ID (such as CNPJ), billing address and billing contact;
plan, invoices, tax documents and payment history;
payment method data: the full card number is handled only by the payment processor (such as Stripe). We only receive limited data, such as card brand, last four digits and expiry date.

4.8. Integrations

names of services, tokens (stored as hashes, never in plain text), scopes, rules, hooks and webhooks configured;
records of calls to the API and the MCP server, with IP address, time and result.

4.9. Recipients without an Account and invitees

When a Customer invites someone by email, or sends a notification by link to someone without an Account, we receive from that Customer the person’s email address and, if the Customer provides it, their name. We use this data only to deliver the invitation or notification and to record the trail. Whoever opens the link may create an Account if they wish.

4.10. Support and communications

Messages you send us, attachments and the support history.

4.11. Technical and usage data

Server logs, performance metrics, errors and feature usage, to keep the Service running, secure and improving.

5. Why we use it and on what legal basis

Purpose	Data	Legal basis (LGPD)
Create and maintain your Account, sign you in, deliver notifications and return answers	4.1, 4.2, 4.3, 4.5	Performance of a contract (art. 7, V)
Record the evidence trail and issue decision receipts	4.6	Performance of a contract (art. 7, V), regular exercise of rights (art. 7, VI) and legitimate interest (art. 7, IX)
Record precise location at the moment of a decision	4.6 (precise location)	Consent, given through the device permission (art. 7, I)
Protect accounts, prevent fraud and abuse, limit sign-in attempts	4.2, 4.3, 4.8, 4.11	Legitimate interest (art. 7, IX), including fraud prevention and the data subject’s security
Keep access records for the legal period	4.2	Compliance with a legal obligation (art. 7, II; Marco Civil, art. 15)
Bill and meet tax obligations	4.7	Performance of a contract and compliance with a legal obligation (art. 7, V and II)
Provide support	4.10	Performance of a contract (art. 7, V)
Send notices about the Service (security, billing, changes to the Terms)	4.1	Performance of a contract (art. 7, V)
Marketing of notific.me and other IDIE products and services (details)	4.1, 4.7 (plan), 4.11	Legitimate interest (art. 7, IX, and art. 10, I), with agreement at sign-up as a condition for creating the Account, stated prominently (art. 9, § 3); you can object at any time
Measure, fix and improve the Service, including training and evaluating the models that prioritize, group and silence notifications	4.5 (reactions and metadata; content only after de-identification), 4.11	Legitimate interest (art. 7, IX), with data aggregated or de-identified when used outside its originating workspace
Defend our rights in proceedings and respond to authorities	As needed in each case	Regular exercise of rights and compliance with a legal obligation (art. 7, VI and II)
Process content sent by Customers	4.5, 4.6, 4.9	Basis defined by the Customer, as controller (section 3)

Model training. Reactions and metadata (what was read, ignored, muted, and timings) may be used to train and evaluate the models that prioritize, group and silence notifications. The content of notifications may also be used for this, but only after de-identification, that is, after removing names, email addresses, @handles, document numbers and other data that identify people. Customers may opt out at any time by writing to [email protected] (and, when available, in the workspace settings); opting out applies to content sent after the request.

Artificial intelligence. To provide features such as summaries, classification, prioritization and grouping, we may use artificial intelligence models, our own or third parties’ (including through model aggregators). Third-party providers receive only the data needed for each task.

Automated decisions. The Service applies rules and models to decide whether a notification is delivered right away, grouped into a digest or silenced. These rules are configured by the Customer, and critical decisions and questions always reach a person. You may request a review of decisions made solely on the basis of automated processing that affect your interests (LGPD, art. 20).

Marketing

When you create an Account, you agree to receive marketing from IDIE. This is a condition for creating the Account, and it is stated prominently at sign-up.

Who receives it: people with an Account. All Accounts are personal, including those of people who create or join Organizations. Recipients without an Account do not receive marketing.
What it is about: notific.me and other IDIE products and services. We do not send third-party advertising.
Channels: email, messages within the Service and notifications through notific.me itself.
Personalization: we may tailor messages to your plan and to how you use the Service (features used, volume, sign-in frequency).
What we never use: the content of notifications, questions, answers and files sent through the Service. We do not sell or rent contact lists.
How to stop: use the link in each email or the setting in your Account. Opting out does not affect your access to the Service. Service notices (security, billing, changes to the Terms) are not marketing and continue to be sent.

We do not sell or rent personal data. We share only what is necessary with:

6.1. The organization and the system that asked

When you are a Member of an Organization or answer a Customer’s question, that Customer sees what you received, read and answered, together with the evidence trail (device, IP address, time and, if you allow it, location). The answer is also returned to the Customer’s originating system by webhook or through the API, together with the identity of who answered.

6.2. Suppliers that help us provide the Service (sub-processors)

Category	Examples	Purpose
Network, security and storage	Cloudflare, Inc.	Content delivery network (CDN), DNS, protection against attacks, hosting of the customer area, long-term archive storage, and cookie-free analytics on the website
Cloud infrastructure	Cloud and server providers	Servers running the API, the database and background jobs
Mobile and browser push	Google (Firebase Cloud Messaging), Apple (Apple Push Notification service) and browser Web Push services (Google, Mozilla, Apple, Microsoft)	Waking the app and delivering push notifications
Transactional email	Email delivery provider	Sign-in emails, invitations and notices
Payments	Stripe, Inc. and affiliates	Payment processing
Artificial intelligence	Model providers, our own or third parties’, including model aggregators	Summarizing, classifying, prioritizing and grouping notifications, and other AI features
Tax documents	Tax document issuers, where applicable	Issuing tax documents when required by law

Push carries only the minimum needed to wake the app (identifiers and, when configured, a short summary). The app fetches the full content directly from our servers over an encrypted connection.

These suppliers may use the data only to provide the service we contracted. Customers may ask [email protected] for the current list of sub-processors.

6.3. Other cases

Authorities: when there is a court order, a lawful request or a legal obligation, and to protect rights and the security of the Service, people or third parties.
Corporate transactions: in a merger, acquisition, incorporation or asset sale, data may be transferred to the successor, who will follow this Policy.
With your authorization: in other cases, when you ask for it or authorize it.

7. Where the data is and international transfers

The Service runs on distributed infrastructure, across more than one region and more than one provider (application servers, content delivery network and file storage). For security reasons, we do not disclose the exact location of our servers.

Data may be processed in Brazil, in the United States and in other countries where our suppliers operate. These transfers are made with the safeguards of article 33 of the LGPD and, for data subject to the GDPR, Chapter V of the GDPR, such as standard contractual clauses approved by the ANPD or by the European Commission, adequacy decisions, or equivalent safeguards adopted by those suppliers. They are also necessary to perform the contract with you.

8. How long we keep it

We keep each piece of data only as long as necessary. After that, we delete or anonymize it.

Data	Period
Account (registration, email addresses, devices)	While the Account exists. After deletion, up to 30 days to complete removal
Free plan Accounts with no sign-in for 12 months	Deleted after an email notice sent at least 30 days in advance
Notifications, questions, answers and evidence trail	The workspace plan’s retention period: Personal 7 days, Pro 30 days, Teams 90 days, Business 1 year, Enterprise as agreed. The period is fixed when each record is written
Invitations no longer pending	30 days
Sign-in codes and links	Minutes, until used or expired
Records of access to the Service (IP address, date and time)	6 months, as required by article 15 of the Marco Civil da Internet
Tax and billing data	5 years, or the period required by tax law
Backups	Up to 35 days, when they are replaced by newer ones
Data under legal hold (an authority’s order, investigation or dispute)	For as long as the hold lasts

notific.me separates what is in use (hot storage) from the consolidated history, which goes to an immutable, signed archive (cold storage). Both follow the same plan period, and an automatic process deletes what has expired.

When you delete your Account, the answers you gave to an Organization remain in its trail until the end of the Organization’s plan period, because they are part of the record that belongs to it (section 3).

9. How we protect it

encrypted connections (TLS) for all traffic;
answers signed with each device’s key, released only after the device’s biometrics or passcode;
a hash-chained evidence trail that makes tampering detectable;
receipts and long-term archives signed with the server key (Ed25519), which can be verified publicly;
tokens and codes stored as hashes; second factor stored encrypted;
data encrypted at rest in storage;
attempt limits, role-based access control and an audit log of actions in the panel;
internal access restricted to those who need it, under a duty of confidentiality.

No system is completely secure. If a security incident may cause relevant risk or harm, we will notify the competent authorities and the affected people within the periods required by law and, when we act as processor, we will inform the Customer so it can do the same.

10. Your rights

Under the LGPD (art. 18), you may request:

confirmation that we process your data;
access to the data;
correction of incomplete, inaccurate or outdated data;
anonymization, blocking or deletion of unnecessary or excessive data, or data processed in breach of the law;
portability to another supplier;
deletion of data processed on the basis of your consent;
information about who we share your data with;
information about the possibility of not giving consent and its consequences;
withdrawal of consent;
review of decisions made solely on the basis of automated processing;
objection to processing carried out without consent, when it breaches the law.

How to ask: much of your data can be viewed and corrected in the customer area itself. For the rest, including account deletion and data export, write to [email protected] from an email address linked to your Account. We may ask for information to confirm your identity before acting. We will respond within 15 days.

Limits: some requests may not be met, in whole or in part, when the law requires us to keep the data, when it is needed to defend rights, or when the data belongs to a Customer (section 3). In the last case, we will forward the request to the Customer.

You may also file a complaint with the Brazilian National Data Protection Authority (ANPD), at gov.br/anpd.

11. Cookies and browser storage

The customer area uses the browser’s local storage (localStorage) and a service worker to:

keep you signed in;
remember language and theme;
receive push in the browser and work as an installed app (PWA).

These features are necessary for the Service to work. We do not use advertising cookies or third-party trackers in the customer area. On the website, we use Cloudflare Web Analytics, which measures visits without cookies and without identifying you. Infrastructure providers (such as Cloudflare) may use technical security cookies. If we start using analytics tools that require consent, we will update this Policy and ask for your consent where the law requires it.

12. Children and adolescents

The Service is intended for people aged 18 or over. We do not knowingly collect data from people under 18. If we find an Account belonging to a minor, it will be deleted. Customers must not send children’s and adolescents’ data through the Service without a legal basis and without the safeguards of article 14 of the LGPD.

13. People in the European Economic Area, United Kingdom and Switzerland

If you are in the European Economic Area, the United Kingdom or Switzerland, the following also applies:

Controller: IDIE CONSULTING TECHNOLOGY LTDA, as identified in section 1, for Account data and Usage Data. For content sent by Customers, the controller is the Customer (section 3).
Representative: to be appointed
Legal bases (GDPR, art. 6(1)): performance of a contract (b) for the Account, delivery of notifications and answers, billing and support; compliance with a legal obligation (c) for access records and tax data; legitimate interests (f) for the evidence trail, security, fraud prevention, improvement of the Service and model training with aggregated or de-identified data, and marketing about notific.me and other IDIE products and services, including tailoring it to your use (you can object at any time); consent (a) for precise location.
Your rights: access, rectification, erasure, restriction of processing, data portability, objection (including to direct marketing, at any time), withdrawal of consent at any time without affecting prior processing, and not being subject to a decision based solely on automated processing that produces legal or similarly significant effects. The Service’s filtering does not produce such effects: critical decisions and questions always reach a person.
How to exercise them: write to [email protected]. We will respond within one month, extendable as allowed by the GDPR.
Complaints: you may lodge a complaint with the data protection authority of your country of residence or work, or of the place of the alleged infringement.
Transfers: your data is processed outside your country (section 7), with standard contractual clauses or adequacy decisions as safeguards. You may request a copy of the safeguards from [email protected].
Retention: as in section 8.

14. Dedicated and self-hosted instances

When a company operates its own notific.me installation (dedicated or self-hosted), it is responsible for the data processed there, and this Policy does not apply to that processing. The notific.me push relay, used by those installations to wake the app, receives only an envelope with identifiers, without the content of notifications.

15. Changes to this Policy

We may update this Policy. The current version is always published, with its date and version history. Material changes will be announced by email or within the Service before they take effect. This Policy is written in English; we may publish translations, including in Brazilian Portuguese and Spanish. If there is a conflict, the English version prevails, except where mandatory law requires the version in the data subject’s language to prevail.

16. Contact


Controller	IDIE CONSULTING TECHNOLOGY LTDA, CNPJ 63.210.794/0001-38
Address	Rua Pais Leme, 215, conjunto 1713, Pinheiros, São Paulo, SP, 05424-150, Brazil
Data protection officer	IDIE is a small-scale processing agent and, under article 11 of ANPD Resolution CD/ANPD no. 2/2022, does not appoint a data protection officer. Our channel for data subjects and authorities is [email protected]
Privacy channel	[email protected]