Privacy Policy
Version: 2026-11-13 | Established: 5 July 2026 / Last revised: 13 November 2026 | Revision history
KARIN, Inc. (株式会社KARIN, "the Company", "we", or "us") sets out this Privacy Policy ("Policy") for the browser extension Pepetto (the "Service") regarding how we handle User information.
Article 1 (Scope)
This Policy applies to use of the Service, including the browser extension, the accompanying website, and the sign-in and administration functions.
Pepetto places one dedicated container on the host page and displays content only inside it. Pepetto does not change the host page's existing elements or attributes.
In this Policy, "Tenant" means a Tenant as defined in the Terms of Use (shown as a "workspace" in the Service).
Article 2 (Operator)
- Operator: KARIN, Inc. (株式会社KARIN)
- Corporate number: 5013301055426
- Address: 1206 BIG Office Plaza Ikebukuro, 2-62-8 Higashi-Ikebukuro, Toshima-ku, Tokyo 170-0013, Japan
- Service name: Pepetto
- Contact: info@karin-inc.co.jp
Article 3 (Information we collect)
We collect the following kinds of information. The categories follow the Google Chrome Web Store categories.
| Category | What | Why |
|---|---|---|
| Personally identifiable information | Email address, display name, department, and other fields a User chooses to enter | To create an account and to identify the User to other Members |
| Authentication information | Sign-in information handled by Firebase Authentication. Firebase Authentication holds the password. Our servers keep the login record | Sign-in and identity checks |
| Web history | For pages where the Service displays notes or memos, the extension reads the page URL and document title. We read them at startup and regularly while the page is open, including while a User is signed out. Marks for notes that a User has hidden or shown again on a page are kept on the device for each signed-in User, as hashes made from the URL and title, and are not sent to our servers. (1) For matching, the Company uses one-way identifiers (such as SHA-256 hashes of a normalized page URL and, where applicable, the page title) that cannot be reversed to recover the original URL or title. (2) For display and lists, the Company stores a redacted page URL (with sensitive query parameters removed) and the page title, including for shared notes and private memos. The Company does not load personal memo content from the server until the User has agreed to the Terms of Use and this Policy. The Company does not collect the body of pages you view, cookies, or form field contents on those pages. When a User pastes into the User's own note, we read the pasted text, including its formatting, and place that text in the note | To provide the core Service function of showing notes and memos on the correct page (matching and showing where they were created) |
| User activity | History of creating, editing, and confirming notes, and logs of invitations and permission changes (including records when our staff view the text of your notes or memos for an inquiry, security, or to comply with law; we do not copy that text into the record). Each Member's last use time (updated at most about once per hour). We use it for the Last active column on the member list, display on the member edit screen, and member CSV export. | To provide the Service, to audit misuse, and to show read state |
| Website content | Content that the User creates in the Service (notes, memos, portal entries, etc.). This does not include the body of web pages the User views outside that User-created content | To provide the core Service function of information sharing |
| Tenant attributes | Country of residence, preferred language (entered when the Tenant is created), time zone, and the path by which the User reached the Service (collected automatically) | To optimize notice delivery (language and region), to consider service localization, and to analyze marketing effectiveness |
| Technical information | The IP address sent by the browser when it connects. When Firebase Authentication makes a request, the request carries the browser name, an app identifier, and component versions. When the extension calls Cloud Functions, the data includes the extension version. When a User requests a password reset, we send the email address, the language when it is Japanese or English, and the extension version to Cloud Functions in asia-northeast1 | To detect unauthorized login and automated mass registration, and to limit access frequency. Records used for access-frequency limits are deleted after the period in Article 11. Version and browser name are used to identify the client that sent the request |
| Contract and billing information | When a Tenant uses a paid plan, the extension's plan screen shows contract details (contracted seats, billing interval, and displayed monthly or yearly amounts, among other fields), the next renewal date based on subscription information we hold on our servers, and the next invoice amount obtained from the payment processor Stripe. We do not show card numbers, invoices, or payment history on the Service's screens; those are handled on Stripe's screens. For transactions shown as "Sold through Link", receipts, invoices, and payment history are handled on Link's screens and emails. | To let Users check their plan and their next charge |
| Records of contract | The time the User agreed to the Terms and to this Policy, the version agreed to, the language shown at that time, and identifiers of the User who agreed (account ID and email address) | To prove that the contract was formed and to perform legal retention duties |
Portal icons are shown with Chrome's favicon feature. Chrome may obtain the icon from the site registered on that portal. The image is placed inside Pepetto's own element. The icon request carries that registered URL.
Creating the Firestore client does not open a connection by itself. While a User is signed out, Pepetto does not call Firestore reads or listeners.
Credit card numbers are obtained and managed by the payment processor Stripe. The information we collect is the fields listed in the table in this Article. Browsing history of websites unrelated to the Service's note and memo features, the body text of pages you view, cookies on those pages, contents of form fields on those pages, and sensitive information that a User did not enter (such as beliefs or medical history) are not among those fields.
Article 4 (Purposes)
We use collected information for these purposes only:
- To provide, maintain, and improve the Service (showing notes, sending notification email, managing permissions, and similar work)
- To verify identity and prevent unauthorized access
- To respond to failures and investigate the cause of errors (see Article 8 below)
- To respond to inquiries
- To send important notices (specification changes, maintenance, and similar notices)
- To keep a record of agreement to the Terms and this Policy, and to prove that the contract was formed
- To comply with law
The text of the notes and memos you write is yours. Our staff view that text only when you ask us to in an inquiry, or when it is necessary for security or to comply with law. For an inquiry, we view a private memo only when the member who wrote it asks us to. An owner's permission alone is not enough. When we view it, we make a record.
Provision to third parties other than the above is as set out in Article 7. We do not sell information in a form that identifies an individual User to third parties.
Article 5 (Legal bases)
This Article is for Users in jurisdictions that require a stated legal basis for personal data processing, including the EU General Data Protection Regulation (GDPR). For Users in Japan, Article 4 (Purposes) applies.
| Information | Legal basis |
|---|---|
| Account information (email address, display name, department, and similar fields) and authentication information | Performance of a contract (GDPR Article 6(1)(b)) |
| Content of notes and memos, the URL and title of the page where they are shown, and note confirmation history | Performance of a contract (GDPR Article 6(1)(b)) |
| Tenant attributes (country, preferred language, time zone) | Performance of a contract (GDPR Article 6(1)(b)) |
| Records of contract | Legal obligation (GDPR Article 6(1)(c)), and our legitimate interests (Article 6(1)(f): the need to prove the contract) |
| Payment records | Performance of a contract (GDPR Article 6(1)(b)), and legal obligation (Article 6(1)(c)) |
| Activity logs (audit records such as invitations and permission changes, and records when our staff view the text of notes or memos for an inquiry, security, or to comply with law) | Legitimate interests (GDPR Article 6(1)(f): preventing misuse and keeping an audit trail) |
| Inquiry records | Performance of a contract (GDPR Article 6(1)(b)), and legitimate interests (Article 6(1)(f): refunds and disputes) |
| Error information | Legitimate interests (GDPR Article 6(1)(f): keeping the Service stable and safe) |
| IP address (used to limit how often a client may connect) | Legitimate interests (GDPR Article 6(1)(f): preventing unauthorized access and automated attacks) |
For processing we carry out on the basis of "legitimate interests," a User may object as set out in Article 12 (Your rights).
Article 6 (Anonymized and aggregated information)
We may use anonymized and aggregated information internally for service improvement, analysis of defect trends, understanding of usage, market research and analysis to inform future service development, and research and development of new features of our services (including features using artificial intelligence and machine learning). We use such anonymized and aggregated information only for the purposes above, and we do not restore it to a form that identifies individuals or Tenants, or provide or sell it to external third parties.
Article 7 (Provision to third parties)
We do not provide collected information to third parties except in the following cases:
- Where the User has consented
- Where disclosure is required by law
- Where necessary to protect life, body, or property
- Where we entrust information to subcontractors necessary to operate the Service (see Article 8), within the scope necessary for them to perform their work
- Where personal information is provided in connection with business succession such as merger, company split, or business transfer (in that case also, use is only within the purposes of this Policy)
- Where we provide contract information (such as the Tenant identifier, the Owner's email address, the number of seats, and the Tenant's country of residence) to Sold through Link, LLC, as needed for payment, tax, and support for transactions where it is the merchant of record (see Article 8). In that case Link handles personal data on its own responsibility under Link's privacy policy.
Article 8 (Subcontractors and storage locations)
We use the following external services to store and process information. Please also see each provider's privacy policy.
| Service | Purpose | Main storage region |
|---|---|---|
| Firebase (Google Cloud) | User data, authentication, note data. Password reset and other calls use Cloud Functions in asia-northeast1. Attachments are saved to Firebase Storage when the User is signed in. | Tokyo region (asia-northeast1) |
| Stripe Japan, Inc. (Stripe Payments Europe, Limited is also a party for personal data) | Payment processing and subscription management (Stripe obtains and manages card data directly, not through us) | Includes locations outside Japan (under Stripe's privacy policy) |
| Stripe Payments Europe, Limited | Processing of personal data related to payments | Includes locations outside Japan (under Stripe's privacy policy) |
| Sold through Link, LLC (an affiliate of Stripe) | Merchant of record for transactions shown as "Sold through Link", such as paid plans for Tenants outside Japan: payment, tax calculation and remittance, receipts, transaction support, and refunds. Link handles personal data for those transactions as an independent controller (Article 7, item 6). | Includes locations outside Japan (under Link's privacy policy) |
| Resend | Sending notification email. Resend keeps records of sent mail (including logs) for 30 days. | United States |
| Sentry | Recording and analyzing errors. Data sent includes extension version, environment name, operation name, browser language, time zone, and calendar. Before sending, we remove request, user, and breadcrumb fields, replace http(s) URLs in messages, and remove host-page URLs from stack filenames. We design error reports so that they do not include page URLs, page titles, the text of notes or memos, email addresses, or account identifiers. We have configured Sentry not to store IP addresses. | United States |
| Cloudflare, Inc. | Detecting automated access and fraudulent registration (Turnstile), and DNS. On website pages that do not require login, measuring access and display speed (Web Analytics). Cloudflare states it does not use cookies or localStorage for tracking and does not fingerprint users. | Includes locations outside Japan (under Cloudflare's privacy policy) |
| Vercel | Website hosting | Global CDN |
| Microsoft (Microsoft 365) | Sending, receiving, and storing support inquiry email | Japan (region Microsoft commits to for mail storage; some processing such as spam filtering may occur outside Japan) |
These subcontractors take appropriate security measures under their contracts with us or their policies.
Turnstile processes IP addresses, TLS connection information, User-Agent, site keys and where they are sent from, and similar data to detect and block automated misuse (bots). Cloudflare processes data both on our instructions and for its own purposes to improve Turnstile detection (under Cloudflare's Turnstile Privacy Addendum).
Article 9 (Cookies and similar technologies)
The Service uses the browser's chrome.storage feature (extension) and localStorage (website) to maintain login state and save display settings. Page identifiers (host, port, path, title), whether the User is signed in, account ID, email address, and the User's agreement status for the Terms of Use and this Policy are stored in the extension's storage (chrome.storage). Page identifiers are not written to the host page's storage. Values that earlier versions placed on the host page's storage are moved to the extension's storage, and Pepetto's old values are removed from the host page. On the website, we store login state, the selected Tenant, and how the User learned about the Service (referral source). We use these only to provide and improve the Service, not for third-party advertising tracking.
Article 10 (Chrome Web Store User Data Policy)
If the Service uses information obtained from Google APIs, that use follows the Chrome Web Store User Data Policy, including the Limited Use Requirements. That includes not using obtained information for any purpose other than the single purpose the Service publishes, not using it for advertising, and not selling it to third parties. The Service's extension does not currently use APIs such as chrome.identity to obtain Google account user data.
Article 11 (Retention)
We set the retention periods below by type of information, retain information for those periods, and delete it automatically after they elapse.
| Information | Retention |
|---|---|
| Tenant data (notes, memos, portals, Member information, note confirmation history, and operation logs such as permission changes) | 90 days from a deletion request (kept after cancellation unless a request is made) |
| Deleted notes, personal memos, portals, groups, or tags | Deleted 30 days after deletion (recoverable until then; deleted immediately if permanently purged). Attachments to notes and personal memos are deleted together |
| When a Member is removed from a Tenant | That Member's personal memos, personal ToDos, personal portals, and My Sets are deleted immediately and cannot be restored. Shared notes, portals, tags, creator names, and audit records remain as Tenant data |
| Account (login information, language settings) | 30 days after the User belongs to no Tenant |
| Announcement read state | Deleted when the account is deleted |
| Inquiry records (content, name, email, attachments) | 365 days from the last message; kept after Tenant cancellation |
| Records of contract (consent time, version, language, identifiers) | 10 years from consent |
| Payment records | Kept by Stripe (or by Link for transactions shown as "Sold through Link") for periods required by tax and other laws |
| Error information | Up to 30 days (Sentry's retention period) |
| Records used to limit access frequency | 2 days |
| Record of Tenant deletion (Tenant identifier, request and execution times, Member count) | 5 years from deletion (does not include name or email) |
After we delete data, it is removed from recovery copies within up to 30 days, and then removed from the subcontractor (Google) within up to about 180 days under Google's policy.
We keep inquiry records for continuity of support and to handle refunds and disputes. We keep records of contract to perform retention duties under Article 432, paragraph 2 of the Companies Act of Japan and the Corporation Tax Act, and because we need to prove that the contract was formed. We keep other information for the periods required by applicable law where retention is mandated.
Article 12 (Your rights)
A User may ask us to do the following regarding the User's information:
- Disclosure (confirmation of what information we hold)
- Correction, addition, or deletion
- Suspension of use
Users to whom the GDPR applies also have the following rights in addition to the above:
- The right to request restriction of processing (GDPR Article 18)
- The right to receive information the User provided in a structured, commonly used, machine-readable format and to transmit it to another controller (GDPR Article 20)
- The right to object to processing we carry out on the basis of "legitimate interests" (GDPR Article 21)
- The right to lodge a complaint with a supervisory authority in the User's location (GDPR Article 77)
If a User objects under item 6 above, we stop that processing unless we can demonstrate compelling legitimate grounds to continue it.
If you wish to exercise these rights, contact us at the inquiry address in Article 2. We respond within a reasonable period.
Article 13 (Minors)
The Service is provided as business groupware for companies and organizations, and we do not intend it to be used by anyone under 18. If we learn that we collected personal information from a minor without intending to, we delete it promptly.
Article 14 (International transfers)
The main location where we store data is Japan (Tokyo region); however, some of the subcontractors listed in Article 8, including businesses in the United States, handle personal data outside Japan. When we transfer personal data to a subcontractor outside Japan, we require the subcontractor, by contract, to maintain a system that meets the standards set by the rules of the Personal Information Protection Commission of Japan, and we take the measures needed to ensure that the system continues to operate. On request, we will provide information about those measures through the inquiry address in Article 2. Personal data transferred from the European Union to us relies on the European Commission's adequacy decision for Japan, and when we transfer that data onward to a subcontractor outside Japan, we rely on the subcontractor's certification under the EU–U.S. Data Privacy Framework where it holds one, and otherwise on the European Commission's standard contractual clauses. For other countries and regions, we follow the transfer mechanisms required by applicable law, and you may request a copy or summary of the safeguards from the inquiry address in Article 2.
Article 15 (Changes to this Policy)
We may change this Policy in response to changes in law or the Service. If a change materially affects Users' rights or duties or how information is handled, we notify Users at least 30 days in advance by notice in the Service or by email. The changed Policy takes effect on the effective date we announce. Other changes take effect when posted on the Service.
If the content of how we handle information in the Service changes, we disclose that change actively within the Service. This follows the Chrome Web Store requirement to disclose changes to information handling after the extension is installed.
We assign a version to this Policy and make past versions available on the Service website in the language in which that version was published. An English text is published for a version only when an English text of that version exists.
Article 16 (Language)
This Policy is made in Japanese, and the Japanese version is the original. If there is any discrepancy between the Japanese version and any English or other-language translation of this Policy, the Japanese version shall prevail.
Contact
Questions about this Policy:
KARIN, Inc. (株式会社KARIN) Email: info@karin-inc.co.jp