Pending Privacy Policy
Effective date: 13 October 2026
This Privacy Policy explains in clear terms what personal information Pending collects and processes, where the information comes from, whether you must provide it, how Pending uses it, who may receive it, how long it may be kept, how it is protected, and what rights and choices you may have.
1. Who We Are and Who Controls Your Information
Pending ("Pending," "we," "our," or "us") is a consumer digital service operated by Sarel Kaminsky, an individual based in Israel. Pending helps users organize and track purchases, orders, shipments, and delivery-related information.
For purposes of Israeli privacy law, Sarel Kaminsky is the person responsible for the Pending processing activities he determines and operates and, where the statutory concept applies, is the controller of the relevant database ("baal hashlita bemaagar"). Some service providers may have separate legal responsibilities for activities they independently control. That does not remove Pending's responsibility for the processing Pending itself determines or carries out.
This Policy applies to Pending's website and service, including account registration, Google Sign-In, the optional Gmail connection, order and shipment tracking, CSV/PDF purchase imports, Pending Inbox, manual shipment tracking, paid scan packs and recurring subscriptions, support, waitlist and invitation features, and related product operations.
Privacy contact: hello@pending.to
2. Do You Have to Give Us Information?
Unless we tell you that information is required by law, providing personal information to Pending is generally voluntary. Some information is nevertheless necessary if you want to create an account, connect a Gmail account, import a file, track a shipment, make a purchase, receive support, or use another feature. If you choose not to provide information that a feature needs, Pending may be unable to provide that feature. Connecting Gmail is optional, and you may use only the features that are available without a Gmail connection.
This section, together with the sections below describing purposes, recipients, contact details and user rights, is intended to provide the transparency information required when Pending asks a person to provide personal information, including where Section 11 of the Israeli Privacy Protection Law applies.
3. What Information We Collect
The categories below describe personal information Pending may collect or otherwise process. The exact categories depend on which features you choose to use and on information that appears in the records you connect, forward or upload.
| Category | Information and source | Purpose |
|---|---|---|
| Account and authentication | Email address; authentication/session identifiers; optional profile information; records of acceptance of terms, policies, and age eligibility. Source: you, Google Sign-In, and authentication infrastructure. An authentication identity may be created before the age/Terms confirmation step is completed. | Create and secure the account, maintain sessions, and record account choices. |
| Google / Gmail connection | Google OAuth access and refresh tokens, credential expiry and connection records. These are Google-issued credentials, not your Google password. Source: Google after you authorize the connection. | Maintain the optional Gmail connection and perform scans you request. |
| Candidate emails and order information | For messages returned as candidates: message/thread identifiers, headers, sender, subject, date, Gmail snippet, MIME information and text content. Pending may extract merchant/sender, order reference, tracking number, amount, expected delivery date, status and limited supporting evidence. | Identify orders and shipments, create timelines, prevent duplicates, and support repair or reprocessing. |
| CSV/PDF purchase imports | Transaction date, merchant, amount, currency, transaction identifier and payment-card or account identifiers that may appear in the source file. If the source contains full identifiers, they may be present during parsing. The uploaded file, extracted text and intermediate parsing material may be processed temporarily as needed to complete the import or handle a failure. The final Pending purchase record is designed to retain no more than the last four card digits and does not include the original transaction row. | Create purchase records you ask Pending to create. |
| Manual shipment tracking | Tracking number and carrier supplied by you, plus shipment status, events and location information returned by the tracking provider, which may include city, postal code, country and in some cases street-level information. | Provide manual shipment tracking. |
| Pending Inbox | Forwarded message content, routing information, receipt/delivery metadata and derived order/evidence data. Administrative retry may retrieve message content again, and the Rescue function may forward up to 12,000 characters of message-body text to the user's login email address. | Receive and process forwarded order/shipment messages and support retry/rescue functions. |
| Billing and subscriptions | Customer, transaction, subscription, payment-status and related billing references received through Paddle. Pending does not use Gmail message content or Google access credentials as checkout inputs. | Manage one-time purchases, monthly subscriptions, credits, refunds, disputes and account administration. |
| Usage, diagnostics and attribution | Product/onboarding events, scan records, error information, feature impressions/clicks/conversions, UTM parameters, referrer host, user identifiers, timing/status and rate-limiting information. Pending may process an IP address for rate limiting/security and may store a derived HMAC value rather than the raw IP in the relevant rate-limiting record. | Operate, secure, troubleshoot and improve Pending and measure product or campaign performance. |
| Support, contact, waitlist and invitations | Email address, message, category, reference information, campaign attribution and operational records. If another user invites you, Pending may receive your email address from that user. | Respond to requests, manage support, waitlists, invitations and related communications. |
4. How We Use Information
Provide, operate, maintain and secure Pending.
Identify purchase- and delivery-related messages and extract order or shipment information.
Create, update and display order, shipment and delivery records and timelines.
Prevent duplicate imports and maintain links between Pending records and source messages.
Maintain authorized Gmail connections and perform scans you request.
Provide CSV/PDF import, Pending Inbox, manual tracking, support, waitlist and invitation features.
Manage purchases, recurring subscriptions, scan credits, refunds, payment status and billing administration.
Troubleshoot failures, prevent abuse or fraud, maintain operational records and protect the service.
Measure product usage, onboarding, feature performance and first-touch attribution.
Send service, support, account, billing and other operational communications.
Comply with legal obligations and establish, exercise or defend legal claims.
Where the EU GDPR or UK GDPR applies, the legal basis depends on the purpose. Pending may rely on contract or steps requested by you for features you choose to use; legitimate interests for security, fraud prevention, troubleshooting and service improvement where those interests are not overridden by your rights; legal obligations where applicable; and consent where a particular activity requires consent. Google OAuth authorization is the technical permission that allows Gmail access. It is not, by itself, the legal basis for every related processing activity.
5. How Pending Uses Google and Gmail Data
Google Sign-In and the optional Gmail connection are separate authorization steps. When you choose to connect Gmail, Pending requests the Google OAuth permission gmail.readonly. That permission is read-only but broader than the order-related search criteria Pending applies inside the service. Pending does not use Gmail write permissions and does not use the Gmail connection to send, modify, label, archive, move or delete messages in your mailbox.
Pending uses targeted Gmail searches designed to find messages that may relate to purchases, receipts, orders, shipping, tracking or delivery. Messages returned as candidates may be retrieved using Gmail's full message format so Pending can determine whether a message is relevant and extract order or shipment information. Deeper relevance filtering therefore occurs partly after message content has reached Pending's server.
The initial Gmail connection is designed to review up to the preceding 120 days. User-initiated scans may use the date ranges offered in the interface, including 30, 90 or 120 days or a selected calendar month. Pending uses those date and search criteria to reduce the messages considered by the service, but they do not narrow the underlying read-only Gmail authorization.
Candidate messages can contain signatures, quoted conversations, recipient information or unrelated content. They can also incidentally contain personal information about other people or information that may be sensitive. Pending processes that incidental content only as reasonably needed for the requested service function, security, legal compliance or request handling and does not use it to infer sensitive traits, advertise to you or create unrelated profiles.
Pending is designed not to keep a separate complete copy of the full Gmail message body as an application record. It may retain structured order/shipment data, source identifiers, snippets, previews and limited evidence excerpts needed to provide and support the service. Pending's Gmail parser is not designed to parse images, PDF files or named attachments, although a text part may in some cases be retrieved through Gmail's attachment-related API mechanism depending on message structure.
A candidate message that is ultimately rejected as unrelated is not intended to become an order record. Because the message may already have been processed on Pending's server, limited technical, retry, security or provider-side records may nevertheless exist for a period under the retention practices described in this Policy.
Pending does not currently provide continuous automatic Gmail monitoring or delivery alerts. Gmail processing occurs through service flows such as initial connection, scans you request or initiate, and limited technical retry, repair or reprocessing. A repair or reprocessing operation may reread a message already linked to a Pending order so saved information can be corrected or completed.
Google Limited Use disclosure. Pending's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Pending uses Google user data only to provide or support user-facing service features; does not sell Google user data; does not use Gmail content for targeted advertising; does not transfer Gmail data to data brokers; and does not use raw, derived, aggregated or anonymized Google Workspace API data to train generalized or personalized AI or machine-learning models.
The current Gmail extraction path uses deterministic rules rather than sending Gmail message content to a third-party AI or machine-learning service. Human access to Google user data is restricted to situations where access is reasonably necessary to provide support or a feature you requested, investigate a security, abuse, fraud or technical issue, comply with law, or otherwise act in a manner permitted by Google's policies and applicable law. Pending does not permit human access to Gmail content for advertising or unrelated purposes.
6. Who We Share Information With and Why
Pending shares or makes information available only as reasonably needed for the relevant feature, service operation, security, legal compliance or transaction. The main provider categories currently identified are below.
| Provider / category | Why it is used | Information involved |
|---|---|---|
| Google Sign-In and optional Gmail API authorization/access. | Identity/authentication data and Gmail data you authorize Pending to access. | |
| Supabase | Authentication, database and application infrastructure. | Account, connection, order/tracking, operational and related application records. |
| Resend | Inbound and outbound email, including Pending Inbox functions. | Forwarded message content, routing/delivery metadata and service communications. |
| 17TRACK | Manual shipment tracking when you submit a tracking number/carrier. | Tracking number/carrier; shipment status/events/location returned by the provider. Gmail content is not automatically sent through the manual-tracking flow. |
| Paddle | Checkout, billing, reseller and Merchant of Record services for purchases made through Paddle checkout. | Buyer, billing, transaction, subscription, refund/dispute and payment-related information as needed for the transaction. Pending does not use Gmail message content or Google access credentials as checkout inputs. |
| Hosting and application delivery | Web and application delivery/infrastructure. Pending deployment materials and public delivery identify Vercel for at least part of the service; other infrastructure processing can depend on the live configuration. | Request, device/network, application and technical service data may be processed as part of hosting, delivery, security, diagnostics and logs. |
Providers may act as processors or service providers for some activities and may have independent legal responsibilities for others. Their own terms and privacy notices apply to activities they control. Pending may also disclose information where required by law, to protect users or the service, to investigate fraud or security issues, or in connection with a business reorganization, subject to applicable law.
7. We Do Not Sell Your Information or Use Gmail Content for Targeted Advertising
Pending does not sell personal information to data brokers or other third parties for monetary consideration. Pending does not sell Google user data and does not use Gmail content for targeted advertising. Pending may use internal product measurement and first-touch attribution, such as UTM parameters or referrer host information, to understand how users reached or used Pending. Those activities are separate from Gmail content.
Pending does not use Google Workspace API data to train generalized or personalized AI or machine-learning models. If Pending materially changes these practices, it will update this Policy and provide any notice, choice or opt-out required by applicable law before relying on the changed practice.
8. Cookies, Local Storage and Similar Technologies
Pending uses cookies, localStorage and similar browser storage for authentication, OAuth state, short-lived scan state, user preferences, dashboard state, theme, attribution and related service functions. Some items are short-lived; others may remain until replaced, cleared by Pending, or cleared through your browser.
| Technology / category | Purpose | Retention / notes |
|---|---|---|
| Authentication / session | Keep you signed in and maintain account security. | Duration depends on session and authentication configuration. |
| OAuth state | Protect the Google authorization flow. | Short-lived; Pending uses approximately 10 minutes for this state. |
| Scan intent | Preserve short-lived state during scan/authorization flows. | Short-lived; Pending uses approximately 5 minutes for this state. |
| Preferences / dashboard / theme | Remember interface and product choices. | May remain in localStorage until replaced or cleared. |
| First-touch attribution | Remember campaign/referrer information and support internal measurement. | May remain in browser storage and associated server records; there is no single fixed retention period for all attribution records. |
| Billing interface | Support checkout and payment-related functionality when you use a paid offering. | Paddle may use its own cookies, local storage or similar technologies as part of checkout and fraud/payment operations, subject to its own privacy practices. |
You can clear cookies and localStorage through your browser, although doing so may sign you out, reset preferences or interrupt a feature in progress. Some non-essential storage or access technologies may be subject to consent or another user-choice requirement depending on your location and how the technology is used.
9. How Long We Keep Information
Pending does not use one fixed retention period for every category of personal information. Retention depends on the type of information, the feature used, your actions, operational and security needs, and applicable accounting, fraud-prevention, dispute-resolution or legal requirements.
Account information is generally kept while the account remains active and until account deletion is completed.
Local Gmail connection credentials are kept while Gmail remains connected and are removed from Pending's local Gmail connection storage when you disconnect Gmail or delete the account.
Order, tracking and limited Gmail-derived evidence records may remain until you delete the relevant record or account.
Operational logs, product events, analytics, support/contact records and invitation records do not all share one fixed retention period.
Certain security, access-control or audit records may be retained for a period required by applicable law or security rules, including where the Israeli Privacy Protection Regulations (Data Security), 2017 prescribe retention for the relevant security data.
Billing, transaction and subscription references may be kept as needed for transaction administration, accounting, fraud prevention, disputes and legal obligations.
Provider-side copies, email-provider records, hosting logs and backups may follow separate retention cycles and may persist for a period after deletion from the primary Pending account.
Pending will not intentionally retain personal information longer than is reasonably needed for the purposes described in this Policy or another purpose permitted by applicable law. Where Israeli rules concerning information received from the EEA apply, Pending will also apply the applicable requirements concerning deletion, accuracy and the continued holding of information that is no longer necessary.
10. What Happens When You Disconnect Gmail or Delete Data
You may disconnect Gmail through Pending. Pending then removes the local Gmail connection and stored Gmail credentials and attempts to revoke the Google authorization. Disconnecting Gmail does not delete the source messages in Gmail and does not automatically delete orders, evidence excerpts or manual tracking records already created in Pending.
If a scan or technical process was already running when you disconnect Gmail or delete the account, the request to disconnect or delete does not necessarily stop every in-flight operation at the same instant. Pending will not intentionally initiate new Gmail access after the connection has been removed, and will treat any late-arriving write, retry, webhook or provider event consistently with the deletion or disconnection request as reasonably possible.
Pending provides controls for deleting certain order and tracking records. Archiving an item or marking it as not an order is not necessarily the same as deleting the underlying record.
Pending also provides an account-deletion flow. Account deletion is designed to address active billing or subscription steps, attempt Google revocation, remove eligible tracking records, delete core Pending product data and remove the authentication account. If an external billing or provider step temporarily prevents completion, some parts of deletion may require retry or support handling. Limited billing references, support/contact records, invitation records created through another user, browser storage, provider-side records, logs or backups may remain where reasonably needed for operational, security, accounting, fraud, dispute, legal or provider-retention reasons.
Deleting your Pending account does not delete messages from your Gmail account. You can also manage Google authorization separately through your Google Account. Browser data such as localStorage or cookies may need to be cleared separately through your browser if it remains after logout or account deletion.
11. How We Protect Information
Pending uses technical and organizational measures intended to protect personal information. The current application design includes restricted database access to Gmail credentials, user-scoped controls for user-owned records, multi-factor requirements for application administrative routes, and HTTPS connections to key external services.
Where the Israeli Privacy Protection Regulations (Data Security), 2017 apply, Pending is required to maintain security measures appropriate to the applicable database and security level, including relevant controls for access management, identification and authentication, logging and monitoring, incident handling, external service providers, backup and recovery, and periodic review. This Policy does not itself determine the regulatory security classification of a Pending database.
If Pending becomes aware of a security incident involving personal information, it will assess and respond to the incident and make any notification to regulators or affected individuals required by applicable law. No method of transmission, processing or storage can be guaranteed to be completely secure.
12. Where Information Is Processed and International Transfers
Pending is operated from Israel and uses technology providers that may process personal information in Israel, the EEA, the United States or other countries. As a result, information may be processed outside the country where you live.
Transfers from Israel. When Pending transfers personal information from Israel to a database or recipient outside Israel, including a recipient in Europe, the transfer is subject to the applicable Israeli rules governing transfers of personal information outside Israel. Pending will rely on an available legal basis for the transfer and, where required, obtain contractual or other commitments intended to preserve the required level of privacy protection.
Transfers from the EEA to Israel. Israel is currently recognized by the European Commission as providing an adequate level of protection for personal data within the scope of the applicable adequacy decision. Personal information received in Israel from the EEA may also be subject to the Israeli Privacy Protection Regulations concerning information transferred to Israel from the EEA, which include requirements relating to notice, accuracy, deletion and limiting the continued holding of information that is no longer necessary.
Where the EU GDPR or UK GDPR applies to a transfer to a country not covered by an applicable adequacy mechanism, Pending will use another transfer mechanism permitted by the relevant law where required. You may contact hello@pending.to for information reasonably available about safeguards relevant to a particular transfer.
13. Your Privacy Rights and How to Exercise Them
Your rights depend on where you live, the source of the information, and which law applies. Pending will consider privacy requests under the law that applies to the relevant processing.
Israeli law: where applicable, you may have the right to inspect personal information about you held in a database under Section 13 of the Israeli Privacy Protection Law and to request correction or deletion of information that is inaccurate, incomplete, unclear or not up to date under Section 14, subject to the conditions and procedures in the law.
Information subject to the Israeli regulations concerning information received from the EEA may also carry rights and obligations concerning deletion, accuracy, notice and the continued holding of information that is no longer necessary.
EEA and UK: where the EU GDPR or UK GDPR applies, you may have rights of access, rectification, erasure, restriction, data portability, objection, withdrawal of consent where consent is the legal basis, and the right to complain to a competent data-protection authority, subject to applicable conditions and exceptions.
United States: residents of certain states may have additional rights if the relevant state privacy law applies to Pending, including rights to know or access, correct, delete, obtain a portable copy of certain information, opt out of certain activities, appeal a decision, or use an authorized agent, depending on the statute.
Pending provides self-service controls for some actions, including disconnecting Gmail, deleting certain orders or tracking records, and deleting the account. A complete self-service export of all Pending data is not currently provided. For access, correction, deletion, portability or another privacy request, contact hello@pending.to. Pending may need to verify your identity and may retain a limited record of the request and response as reasonably needed to document compliance, prevent abuse or resolve disputes.
14. Information About Other People
A connected mailbox, forwarded email, imported file, shipment record or invitation can contain personal information about someone other than the Pending account holder. Pending may receive that information without having a direct relationship with the other person. Pending processes it only as reasonably needed for the requested service function, security, legal compliance, request handling or the other purposes described in this Policy.
If you are not a Pending user but believe Pending may hold personal information about you, contact hello@pending.to. Pending may ask for information needed to identify the relevant record and verify the request and will consider the request in light of applicable law, the rights of the Pending user, and any applicable exception.
Where applicable law requires Pending to provide privacy information to a person whose information was received indirectly, Pending will provide the required information directly or through the source from which it was received, subject to any applicable exception.
15. Communications, Waitlists and Invitations
Pending may send service, account, support, billing and other operational messages. If you join a waitlist or receive a promotional or invitation-related communication, Pending may process your email address and related campaign or invitation information. If another user provides your email address for an invitation, that user is the source of the address.
If you do not want to receive marketing or promotional communications from Pending, you may use an available unsubscribe mechanism or contact hello@pending.to. Pending may keep a limited suppression record so it can honor the opt-out. Service, security, billing or account messages may still be sent when reasonably necessary to provide or administer the service.
16. Children and Minors
Pending is currently intended only for individuals who are 18 years of age or older. If you are under 18, you may not register for or use the service. Pending currently relies on an age self-declaration rather than identity-based age verification.
An authentication identity may be created before the age and Terms confirmation step is completed; protected account access is blocked unless the required confirmation is completed. Public contact or waitlist entry points may not use the same account age gate. They are not intended for persons under 18.
If Pending learns that an account is being used by a person under 18 in violation of this Policy or applicable law, Pending may suspend or terminate the account and take reasonable steps to address the related personal information. If you believe a person under 18 has provided personal information to Pending, contact hello@pending.to.
17. Automated Processing
Pending uses automated searches and rule-based processing to identify candidate order or shipment messages and extract information for the service. These product functions are not used to make decisions about you that produce legal or similarly significant effects.
18. Privacy Laws That May Apply
Pending is operated from Israel. Depending on the information, user location, source of the data, scale of processing and other statutory conditions, the privacy framework may include the Israeli Privacy Protection Law, 1981, as amended, including Amendment 13; the Privacy Protection Regulations (Data Security), 2017; the Privacy Protection Regulations (Transfer of Data to Databases Outside State Borders), 2001; and the Privacy Protection Regulations concerning information transferred to Israel from the European Economic Area, 2023.
Where their territorial and other conditions are met, the EU GDPR, UK GDPR and related ePrivacy or storage-access rules may also apply. Certain United States state privacy laws may apply only if their territorial, business, revenue, data-volume or other statutory thresholds are met. References in this Policy to a law do not mean that every provision of that law applies to every Pending user or processing activity.
19. Changes to This Privacy Policy
Pending may update this Privacy Policy to reflect changes in the service, its features, providers, data practices or legal requirements. The updated Policy will show a revised effective date. If a change would materially alter how personal information is used, or if applicable law requires additional notice or a new choice, Pending will provide the required notice or choice before relying on the change where required.
20. Contact Us
Privacy contact: hello@pending.to
Operator and database controller where applicable: Sarel Kaminsky
Location: Israel