本文へスキップ

Privacy Policy

Effective date: October 1, 2026

This Privacy Policy describes how personal data is collected, used, disclosed and retained in connection with AicippY — the website at www.aicippy.com, the console and account area, the desktop application, the command line interface and the terminal user interface (together, the "Services").

By accessing or using the Services in any manner, you accept the practices described in this Policy and you consent to the collection, use and disclosure of your information as set out in it. Your use of the Services is at all times also subject to the Terms of Service, which incorporate this Policy. Terms used here without definition have the meaning given to them there.

Open source software that is not provided to you on a hosted basis is subject to the licence and terms published in the repository from which you obtain it, and those terms govern your use of that software exclusively.

Contents

1. The companies behind the Services

AIVIBE SOFTWARE SERVICES PRIVATE LIMITED is the company that publishes the Services and the entity responsible for the personal data described in this Policy. It is incorporated in India and headquartered in Chennai.

  • AIVIBE SOFTWARE SERVICES PRIVATE LIMITED
  • A501 Saraduez Olympus, Chennai, Tamil Nadu 600100, India
  • support@aivibe.in

AIVEDHA INC is a subsidiary incorporated in the United States and based in New York. It operates for the Americas and Europe regions. It acts under the governance of AIVIBE SOFTWARE SERVICES PRIVATE LIMITED and is bound by the parent company and by the parent company's jurisdiction.

Where you deal with AIVEDHA INC, that company's own notices apply to that dealing in addition to this Policy. Nothing in those notices extends beyond the governance of the parent company or beyond the jurisdiction stated in the next section.

2. Jurisdiction and governing law

This Policy, the personal data described in it, and every dispute, claim or proceeding arising out of or relating to either, are governed by the laws of India. The courts at Chennai, Tamil Nadu, India have sole and exclusive jurisdiction, wherever you live, wherever you access the Services from, and whatever the nature of the claim.

The company does not submit to the local law of any other country. It is bound by its own jurisdiction and by the international law to which that jurisdiction gives effect. Where an obligation from outside India is recognised and given effect by Indian law, it is met through Indian law and through the courts named above, and not otherwise.

Bringing a claim, a complaint or a regulatory proceeding in another forum does not transfer jurisdiction, does not create a submission to that forum, and does not vary this Policy.

3. What this Policy covers

"Personal data" means information that identifies or relates to an identifiable individual, including information called "personal information" or "personally identifiable information" under an applicable data protection law.

This Policy covers personal data handled across all five surfaces of the product:

  • The website at www.aicippy.com, including the marketing pages, the documentation and the download pages.
  • The console — the account, plan, billing and team area you reach after signing in.
  • The desktop application installed on your own machine.
  • The command line interface run in your own shell.
  • The terminal user interface run in your own terminal.

This Policy does not cover the practices of companies that are not controlled by AIVIBE SOFTWARE SERVICES PRIVATE LIMITED, or of people it does not manage. Where you connect the Services to a third party — a model provider you supply your own key for, a tool server you configure, a repository host — that third party handles your information under its own terms and its own privacy notice.

The same applies to a link. The website, the console and the documentation link to sites the Company does not operate — a provider's terms, a standards body, a package registry, a repository. A link is not an endorsement, the linked site is outside this Policy, and what it collects is governed by its own notice. Reading that notice before providing anything to a linked site is a matter for you.

4. Categories of personal data collected

The table below states what is collected, on which surface, and why. It is written from what the Services actually record.

Category and examples Where it is collected Why it is held
Account and contact data — name, email address, the subject identifier issued by the sign-in directory, the platform user identifier, the organisation or tenant identifier where your sign-in carries one, the role assigned to you, and the date and time of your last sign-in. Website, console, desktop application, command line interface, terminal user interface
  • Creating and operating your account
  • Authenticating you and applying your plan
  • Corresponding with you
Billing and transaction data — the plan and price you selected, the payment, order, subscription and mandate identifiers returned by the payment processor, the card brand and the last four digits of the card, the amount and currency of each payment, the tax treatment applied, the billing email, checkout session records and their expiry, and the history of changes to your subscription. Console
  • Taking payment and renewing a subscription
  • Issuing invoices and meeting tax and accounting obligations
  • Reconciling a payment and investigating a billing dispute
Payment instrument details. Card numbers, expiry dates, security codes, bank credentials and equivalent instrument details are entered in the payment processor's own checkout window. They are not received by, transmitted to, or stored on the infrastructure operated for the Services. The payment processor's checkout window
  • Handled by the payment processor alone, under its own terms
Device and network data — IP address, user agent, browser, operating system and device type, and the network-level signals the content delivery network records in front of the site. Website, console
  • Delivering pages and keeping the service available
  • Rate limiting, abuse prevention and fraud prevention
  • Recording administrative actions in the audit trail
Model usage metadata — the model identifier, the count of input and output tokens, whether the response was streamed, the outcome and stop reason, the latency, the request identifier, the plan in force, and the account the request belongs to. No prompt text and no model output is stored in this record. Desktop application, command line interface, terminal user interface, console
  • Measuring usage against the plan
  • Rate limiting and capacity planning
  • Investigating a failed or abnormal request
Content you send to a model — the prompts, files, code and other material you submit for a model to act on, and the model's response. This is passed to the model endpoint that serves your request and is not retained as a record of the conversation. Desktop application, command line interface, terminal user interface
  • Passing the request to the model provider so it can be answered
Local data on your own machine — the configuration, project settings, session history and credentials held by the desktop application, the command line interface and the terminal user interface. Sign-in credentials held on a desktop machine are placed in the operating system keychain. Desktop application, command line interface, terminal user interface
  • Kept on your device, under your control
  • Not transmitted except where an action you take requires it
Administrative audit entries — the actor, the action, the object acted on, the description, the IP address and the user agent recorded when an administrative change is made to an account. Console
  • Accountability for administrative changes
  • Investigating a security event or a disputed change
Payment event records — the notifications received from the payment processor, kept as received, together with the signature presented, the result of verifying it and the identifier used to reject a repeated delivery. Console and billing backend
  • Establishing what a payment processor stated and when
  • Rejecting replayed or unsigned notifications
Email delivery records — the message sent, the address it was sent to, the reason it was sent, and any suppression recorded against that address. Console and billing backend
  • Sending receipts, renewal notices and service messages once and only once
  • Honouring an unsubscribe
Correspondence — what you write when you contact support, report a problem or raise a grievance, and what you attach to it. Email and support channels
  • Answering you and keeping a record of the matter
Cookies and browser storage — the identifiers and preferences described in the Cookie Policy. Website, console
  • Sign-in, checkout, language, appearance and referral attribution

Sources

Personal data reaches the Services from three places, and no others:

  • From you — when you create an account, choose a plan, send a message, configure the product or write to support.
  • From your use of the Services — collected automatically as you use them, as set out in the table above and in the Cookie Policy.
  • From the providers listed in this Policy — the payment processor reports the outcome of a payment and the identifiers attached to it; the sign-in directory reports that you authenticated and who you authenticated as.

Personal data is not bought from data brokers and is not acquired from list vendors.

5. Why personal data is processed

  • To provide the Services — creating and operating accounts, authenticating you, applying your plan and entitlements, serving model requests, and delivering the website, the console and the downloads.
  • To take payment — processing subscriptions and orders, operating bank mandates for renewals, issuing invoices, applying the correct tax treatment, and reconciling what a payment processor reports.
  • To support you — answering correspondence, investigating a fault, and keeping a record of what was asked and what was done.
  • To keep the Services working and defensible — rate limiting, abuse and fraud prevention, detecting and investigating security events, maintaining audit trails, debugging, and capacity planning.
  • To improve the Services — measuring how features are used in aggregate, testing, and product development.
  • To market the Services — as set out in Marketing and sharing with third parties.
  • To meet legal obligations and to establish, exercise or defend legal claims — tax and accounting record keeping, responding to a lawful demand as described in Government and law-enforcement requests, enforcing the Terms of Service, responding to allegations that content infringes a third party's rights, and resolving disputes.

Personal data is not processed for a materially different, unrelated or incompatible purpose without notice to you or your consent, and no additional category is collected without the same.

The basis on which each purpose is carried out

Each purpose above rests on one of the bases below. Where a framework such as the EU or UK General Data Protection Regulation applies to a particular processing operation, these are the lawful bases relied on for it; stating them here is not a submission to that framework or to the jurisdiction of the country it comes from, and Jurisdiction and governing law continues to apply.

  • Performance of the contract with you. Providing the Services, authenticating you, applying your plan and entitlements, serving model requests, taking payment, operating renewals, and answering support correspondence. Without this processing the account cannot be operated.
  • Compliance with a legal obligation. Tax and accounting record keeping, GST and invoicing records, statutory retention periods, and responding to a lawful demand as described in Government and law-enforcement requests.
  • The legitimate interests of the Company. Rate limiting, abuse and fraud prevention, detecting and investigating security events, maintaining audit trails, debugging, capacity planning, measuring feature use in aggregate, product development, and establishing, exercising or defending a legal claim. In each case the interest is the continued, safe and solvent operation of the Services, it is balanced against your interests and rights, and the processing is limited to what the purpose needs.
  • Your consent. Non-essential cookies and browser storage, recorded in the preference centre in the Cookie Policy, and any kind of marketing for which the law applying under this Policy requires consent. Consent may be withdrawn at any time, and withdrawal does not affect processing carried out before it.

What happens if personal data is not provided

Account and contact data, and the billing data a payment processor requires, are needed to operate an account and to take payment; where they are not provided, an account cannot be created, a subscription cannot be taken and the Services cannot be supplied. Data the Company is required by law to hold, such as the details an invoice must carry, is needed for the same reason. Every other category is optional: declining it limits the feature that depends on it and nothing else, and it does not lead to the denial of the Services, a different price or a different level of quality.

What personal data is not used for

  • Personal data is not sold. No personal data described in this Policy is sold, and none is exchanged for money or for other valuable consideration. Sharing for the purposes set out in Marketing and sharing with third parties is sharing on the terms of that section, and it is not a sale.
  • Your content is not used to train the Company's models. The content you send to a model, the contents of your projects, and the output produced from them are not used to train, fine-tune or evaluate any model of the Company's own. The same undertaking is given contractually in the Data Processing Agreement. Where you direct a request to a destination you configure with your own key or your own account, what that provider does with the request is governed by that provider's own terms, which are linked against it in Third-party services and subprocessors.
  • No decision with a legal or similarly significant effect is taken about you by automated means alone. Automated processing is used for rate limiting, abuse and fraud signals and entitlement checks; where such a signal would result in suspension or termination, the decision is reviewed by a person before it takes effect, and the route for challenging it is the one set out under Your rights and how to exercise them.

Artificial intelligence in the Services

AicippY is an artificial-intelligence product, and personal data contained in what you send to a model is processed by that model in order to produce the output you asked for. Model output may be wrong; the position on that is set out in the Terms of Service. Models are used to serve your request and for the purposes listed in this section, and not to profile you, to score you or to reach a conclusion about you as a person.

6. Cookies and similar technologies

Cookies and browser storage used by the website and the console — what each one is named, who sets it, what it does, how long it lasts, and how to change what is allowed — are set out in full in the Cookie Policy. That document also carries the preference centre, where the non-essential categories are switched on and off.

Strictly necessary storage is used without consent because the Services cannot be delivered without it. Every other category is off until it is switched on, and a browser in which no choice has been recorded is treated as one in which everything other than the strictly necessary category has been refused.

The Services do not act on a browser's "Do Not Track" signal. Browser-level controls for deleting and blocking cookies remain available to you and operate independently of the preference centre; blocking strictly necessary storage will stop parts of the Services from working.

7. How personal data is disclosed

Service providers and subprocessors

Personal data is disclosed to the providers listed in Payment processors and Third-party services and subprocessors, each of which handles a defined part of the Services and is bound by its own terms and privacy notice.

Parties you authorise

Where you connect the Services to a third party, personal data is disclosed to that party because you directed it. This includes the providers of models you reach with your own API key: your prompt goes to that provider and is handled under that provider's terms and privacy notice. It also includes the sign-in provider you choose to authenticate with, and any tool or repository host you configure.

Legal and regulatory disclosure

Personal data is disclosed where required to meet a legal obligation, on the terms set out in Government and law-enforcement requests, and where necessary to establish, exercise or defend a legal claim, to enforce the Terms of Service, or to protect the rights, property or safety of a person.

Corporate transactions

Personal data may be transferred to a third party in a merger, acquisition, restructuring, insolvency or other transaction in which that party takes control of the business in whole or in part. This Policy continues to apply to the transferred data until it is replaced by a notice at least as protective.

Data that is not personal data

Aggregated, de-identified and anonymised data may be created from personal data and used and disclosed for lawful business purposes, including analysing and improving the Services and promoting the business, provided it is not disclosed in a form that identifies you.

8. Payment processors

Payments are taken through the processors listed below. Which one applies depends on the country you pay from, the instrument you pay with, and the arrangement in force at the time of the transaction.

Card details are not held. Card numbers, expiry dates, security codes and equivalent instrument details are entered in the processor's own checkout window and are handled by that processor alone. What is received back and kept is the payment, order, subscription and mandate identifier, the card brand, the last four digits, the amount, the currency and the outcome.

Renewals run on a bank mandate. Where a subscription renews, it renews against a mandate registered with your bank or card issuer through the processor, under that processor's rules and under the rules of the regulator with authority over it. Additional authentication is applied to a domestic card mandate above the threshold set by the Reserve Bank of India.

Processor Where it is used What it is used for Its terms and privacy notice
Razorpay
(primary)
India and international Hosted checkout, card, UPI, netbanking and wallet payments, subscriptions, bank mandates for renewal, payment status notifications, and the payment record returned to the account. Terms · Privacy
PayPal International Payment and billing agreements where offered for a transaction outside India, and the payment status returned for it. Terms · Privacy
PayU India India Domestic card, UPI, netbanking and wallet payments and recurring mandates where offered for a transaction. Terms · Privacy
Zoho Payments India Domestic collection and invoice settlement where offered for a transaction, and the reconciliation record returned for it. Terms · Privacy
ICICI IPay India Bank-side collection, netbanking and mandate registration where offered for a transaction, and the settlement record returned for it. Terms · Privacy

Each processor is used as provided and unmodified, under its own terms. Where a matter arises inside a processor's own systems — an authorisation decision, a mandate registration, a chargeback, a settlement delay, a breach of that processor's environment — that processor's terms and privacy notice govern it.

9. Third-party services and subprocessors

The Services depend on the providers listed below. Each handles a defined part, receives only the categories named against it, and is bound by its own terms and privacy notice.

The "Role" column separates two different things. A subprocessor is engaged to process personal data as part of delivering the Services. A destination you configure is a provider you choose to send your own requests to, with your own key or your own account: data reaching it goes there because you directed it, and that provider's terms and privacy notice govern it entirely.

Provider Role Purpose Data categories involved Region Its terms and privacy notice
Amazon Web Services
Lambda, RDS for PostgreSQL, Bedrock, AppSync, S3, Cognito, SES, CloudFront, Secrets Manager
Subprocessor Application compute, the platform database and its stored procedures, hosted model inference, the GraphQL and realtime API, object storage for the static site, the sign-in directory, transactional email, content delivery, and secret storage. Account and contact data, billing and transaction data, device and network data, model usage metadata, content sent to a hosted model, email delivery records, audit entries. United States (us-east-1) and the CloudFront edge network Terms · Privacy
Cloudflare
Workers, R2, KV, edge network
Subprocessor Serving the website and console at the edge, object and key-value storage for the application, bot detection, rate limiting and denial-of-service protection. Device and network data, cookies set at the network layer, request metadata. Global edge network Terms · Privacy
PlanetScale Subprocessor Managed database for the console and edge application data. Account and contact data, application records. United States Terms · Privacy
Upstash Subprocessor Ephemeral key-value storage for caching, rate limiting and short-lived state. Account identifiers, request metadata. United States and Europe Terms · Privacy
Honeycomb Subprocessor Operational telemetry and log analysis for the edge and backend services. Request metadata, error and latency records, account identifiers. United States Terms · Privacy
Razorpay Subprocessor Payments, subscriptions and bank mandates. Its checkout script is loaded in the browser at the moment you pay. Billing and transaction data, payment instrument details entered in its own window, device and network data. India Terms · Privacy
PayPal Subprocessor Payments and billing agreements outside India, where offered. Billing and transaction data, payment instrument details entered in its own window. United States and the European Union Terms · Privacy
PayU India Subprocessor Domestic payments and recurring mandates, where offered. Billing and transaction data, payment instrument details entered in its own window. India Terms · Privacy
Zoho Payments Subprocessor Domestic collection and invoice settlement, where offered. Billing and transaction data. India Terms · Privacy
ICICI IPay Subprocessor Bank-side collection, netbanking and mandate registration, where offered. Billing and transaction data. India Terms · Privacy
Google
OAuth and Google API Services
Subprocessor Sign-in with Google, federated through the sign-in directory. Google is the identity provider; the authentication happens on Google's own pages. Name, email address and the account identifier Google returns on sign-in. Global Terms · Privacy · API Services User Data Policy
PostHog Subprocessor Product and release measurement. Used for aggregate counts reported from the build and release pipeline; where it is enabled on a page, it falls under the Performance category in the Cookie Policy. Aggregate event counts; where enabled on a page, device and usage data. United States Terms · Privacy
Google Analytics Subprocessor Website and application measurement, where enabled. It falls under the Performance category in the Cookie Policy and does not run until that category is allowed. Device and network data, pages viewed, events, a browser-level identifier. Global Terms · Privacy
Google Search Console and Bing Webmaster Tools Subprocessor Search-engine reporting on how the site appears in results. These read the search engine's own records; they set nothing on your device through this site. Aggregate search impressions, clicks and positions. No individual visitor record. Global Google terms · Google privacy · Bing terms · Microsoft privacy
Amazon Bedrock Subprocessor Hosted model inference for the models served by the product itself, through a closed list of foundation models. The content you send to a model and the model's response; model usage metadata. United States (us-east-1) Terms · Privacy
Anthropic (Claude) Destination you configure Model inference against your own Anthropic account and key. The content you send to the model and the model's response. As set by that provider Terms · Privacy
OpenAI Destination you configure Model inference against your own OpenAI account and key. The content you send to the model and the model's response. As set by that provider Terms · Privacy
Google Gemini Destination you configure Model inference against your own Google AI or Vertex AI account and key. The content you send to the model and the model's response. As set by that provider Terms · Privacy
Groq Destination you configure Model inference against your own Groq account and key. The content you send to the model and the model's response. As set by that provider Terms · Privacy
Azure OpenAI Destination you configure Model inference against your own Microsoft Azure subscription and deployment. The content you send to the model and the model's response. The Azure region you deploy in Terms · Privacy
OpenRouter Destination you configure Model routing against your own OpenRouter account and key. OpenRouter forwards your request to a further provider it selects, under its own terms. The content you send to the model and the model's response. As set by that provider Terms · Privacy
NVIDIA (Enterprise AI) Destination you configure Model inference against your own NVIDIA account and key. The content you send to the model and the model's response. As set by that provider Terms · Privacy

How these services are used

Every provider above is used as provided and unmodified, under that provider's own terms of service, acceptable use policy and privacy notice. No provider's software is altered, and no provider is operated outside the configuration it offers.

Where an issue arises within a third-party service, that provider's policy governs the issue. This covers a fault, an outage, a change of terms, a change of region, a deletion or retention behaviour, and a security event occurring in that provider's own environment. A claim about the handling of data inside such a service lies against that provider under that provider's terms, and any claim brought here remains subject to Jurisdiction and governing law.

This list is reviewed as the Services change. A provider may be added, replaced or removed, and this document is updated when that happens.

10. Security controls applied

This section describes controls that are applied. It states what is implemented, not what the result of implementing it will be.

Framework

The control set is aligned to ISO/IEC 27001. Access control, change management, logging, secret handling, supplier management and incident handling are organised against that framework.

Accountability and governance

The technical controls in this section sit under the following governance, which is the process side of the same framework.

  • Assessment before a change. A change that introduces a new category of personal data, a new purpose, a new subprocessor or a new transfer is assessed for its effect on personal data before it is released, and the assessment is recorded.
  • Supplier due diligence. A provider is assessed before it is engaged, against the categories it would receive, the region it would hold them in and the terms it publishes. The outcome is recorded, and the provider appears in Third-party services and subprocessors before it receives anything.
  • Training. Every person engaged by the Company is briefed on this Policy and on the handling of personal data on joining and annually thereafter, and attendance is recorded.
  • Review. The control set, the subprocessor list and the retention periods are reviewed annually, and out of cycle where an incident or a change of law calls for it.
  • Incident handling. A security event is recorded, assessed for its effect on personal data, and notified on the terms set out in the Data Processing Agreement and as the law applying to the Company requires.

Tenancy and data separation

The platform is multi-tenant. Records are scoped on two axes and the application's data access requires both:

  • Per-application scoping (app_id). The database is shared with other products of the group. Every table that holds this product's records carries an app_id column constrained by a foreign key to the application registry, and the application resolves that identifier from the registry at query time rather than trusting a value supplied by a caller. Scoping by application is the mechanism that separates one product's rows from another's. A start-up consistency check compares the configured application identifier against the registry row, and the registry row prevails.
  • Per-tenant scoping (tenant_id). Where a sign-in carries an organisation or tenant claim, that claim is read from the verified token and role assignments are keyed on the combination of tenant, product, user and role. Records belonging to one tenant are addressed only through that combination.
  • Row-level security in the database. The platform database is a multi-tenant PostgreSQL instance with row-level security enabled. Tenant isolation is enforced by policies held in the database rather than by the application querying it, applied to reads, inserts, updates and deletes, and restricting rows to the tenant established for the session. On the subscription records that security is forced, so it binds the table's owner as well.
  • Application scoping above it. Reads and writes are also issued through application SQL carrying the application and account scope on every statement, so a defect in one layer is met by the other. Deleting a platform user record cascades the product records that reference it.

Encryption

  • In transit. Traffic to the website and console is redirected to HTTPS, the edge negotiates TLS 1.2 as a minimum, HTTP Strict Transport Security is sent with subdomains included, and the connection from the edge to the origin is TLS. Realtime connections use WebSocket over TLS in production. Connections from the application to the database are encrypted.
  • At rest. Data is held in managed storage services — the managed relational database, object storage and key-value storage named in the subprocessor table — and is encrypted at rest by those services under their own configurations.
  • On your own machine. Sign-in credentials held by the desktop application are placed in the operating system keychain rather than in a file.

Authentication and short-lived tokens

  • Sign-in is through a managed identity directory. Tokens are RS256 JSON Web Tokens.
  • Every token presented to a backend is verified against the directory's published signing keys: the signing key is selected by key identifier, the algorithm is required to be RS256, and the issuer, the token use, the application client and the expiry are each checked. A clock skew of thirty seconds is allowed and no more. Signing keys are refetched at most once a minute for an unknown key identifier, so a flood of invalid tokens cannot become a flood of key requests.
  • Access tokens are short-lived — one hour by default, and whatever shorter period the directory returns — and are renewed five minutes ahead of expiry. Realtime connections rotate their token before it expires.
  • In the browser, the sign-in token is held in session storage and is discarded when the tab is closed. No refresh token is held in the browser.
  • Sign-in redirects use PKCE, with a single-use verifier and a state value that is checked on return and then removed.
  • Checkout sessions carry their own expiry and move to an expired state when it passes.

Least privilege

  • The inference role names the permitted foundation model resources directly. The proxy accepts a closed list of model identifiers and no prefix, alias or case variation of them.
  • The platform database is reachable only from inside the private network. Administrative operations against it are invoked directly against the function that holds that permission and are not reachable from the public endpoint.
  • Secrets are separated by purpose and held in a managed secret store. The key used to sign unsubscribe links is kept apart from the payment credentials.
  • Production infrastructure is marked protected against removal.

Integrity of payment messages

  • Every notification from a payment processor is verified by HMAC-SHA256 over the exact bytes received before anything in it is acted on.
  • The delivery is recorded with the raw payload, the signature presented, the verification result and the algorithm used, under a unique idempotency key that rejects a repeated delivery.
  • Redirects back from a payment flow are restricted to an allowlist of the processor's own domains.

Boundary controls on the web surface

  • A Content Security Policy restricts which origins may supply scripts, styles, images, fonts, frames and network connections. The only third-party script origin permitted is the payment processor's checkout.
  • A Permissions Policy denies browser capabilities that the Services do not use, and grants the payment capability only to the payment processor's own origins.
  • Server and infrastructure identification headers are suppressed on responses from the edge.
  • Rate limiting is applied at the inference proxy.

Logging and audit

  • Administrative changes are recorded with the actor, the action, the object, the IP address and the user agent.
  • Payment notifications are recorded as described above.
  • Model requests are recorded as metadata — model, token counts, outcome, latency, request identifier. Prompt text and model output are not columns in that record.
  • Email sends and suppressions are recorded under idempotency keys.
  • Edge and backend logs are forwarded to the telemetry provider named in the subprocessor table.

Your part

Choose a strong and unique credential for the account you sign in with, keep control of the device and browser you sign in from, and sign out when you have finished. No method of transmitting or storing data over a public network is free of risk, and this Policy describes the controls applied rather than any outcome.

11. Retention and deletion

Deletion after account closure

Personal data is deleted ninety (90) days after account deletion. The ninety-day period begins on the date the account is deleted. At the end of it, the personal data held for that account is removed from the production systems, other than the records named under "What continues to be held" below.

Operational continuity records

Operational continuity records are maintained from the date of your last sign-in for the same ninety-day period. These are the records that allow the account to be operated, restored and accounted for within that window. They consist of:

  • Account identifiers and status — the account and directory identifiers, the application and tenant scope, the role assignments and the date of last sign-in. Held so that an account can be restored intact if the deletion is reversed within the window, and so that access removed on closure can be shown to have been removed.
  • Subscription and payment references — the plan, the subscription and mandate identifiers, and the payment references reported by the processor. Held so that a renewal, a cancellation, a settlement or a chargeback arriving after closure can be matched to the account it belongs to.
  • Payment event records — the processor's notifications as received, with their signature and verification result. Held so that what a processor stated, and when, can be established, and so that a repeated delivery continues to be rejected.
  • Administrative audit entries — the actor, action, object, IP address and user agent of administrative changes. Held so that a change made before closure remains attributable.
  • Email delivery and suppression records — what was sent, to which address, and any suppression recorded. Held so that a message is not sent twice and so that an unsubscribe continues to be honoured after closure.
  • System and security logs — request, error and security event records. Held so that an incident occurring before closure can still be investigated.

What continues to be held after ninety days

  • Financial and tax records. Invoices, payment records and the accounting entries behind them are retained for the period required by Indian tax, company and accounting law, and are used for no other purpose.
  • Records under legal hold. Where a dispute, claim, investigation or regulatory proceeding is live or reasonably anticipated, the records relevant to it are retained until it is concluded.
  • Suppression records. An address that has unsubscribed remains on the suppression list, because removing it would allow a message to be sent to it again.
  • Aggregated and anonymised data. Data from which you are not identifiable is not personal data and is retained.

Deleting your account

Write to support@aivibe.in from the address on the account. The request is acted on as set out in Your rights and how to exercise them. Deletion ends paid access; a subscription should be cancelled separately if you do not want it to renew before the deletion takes effect.

12. Government and law-enforcement requests

Personal data is disclosed in response to a government, regulatory or law-enforcement request only where that request has been approved through the Indian legal process in the company's jurisdiction.

A request originating from the government, regulator, agency, court or law-enforcement body of another country is not acted on directly. Such a request is acted on only where it carries the supporting approval of the Indian legal authorities, obtained through the channels that Indian law provides for it. Approval obtained in the country of origin is not a substitute for that approval.

The handling rule is as follows.

  • A request is assessed against Indian law and against this Policy before any data is identified, and nothing is produced while that assessment is open.
  • A request that is not valid under Indian law, that lacks the required approval, or that is not supported by legal process, is refused.
  • A request that is valid is answered to the minimum extent it compels. Nothing beyond what is compelled is produced.
  • A request that is excessive, overbroad, vague or disproportionate is challenged or narrowed before anything is produced.
  • You are notified of a request concerning your personal data, unless notification is prohibited by law or by the order itself, in which case notification is given when the prohibition ends.
  • Voluntary disclosure is not made. Disclosure follows compulsion under Indian legal process, or it does not happen.

Nothing in this section is a waiver of any right, privilege, objection or remedy, and nothing in it constitutes a submission to the jurisdiction of the requesting country.

13. International transfers

The Services are operated from India. The providers listed in this Policy operate in India, the United States, the European Union and on global edge networks. Personal data is therefore transferred across borders, stored outside the country you are in, and processed by providers in those regions.

By using the Services you agree to that transfer, that storage and that processing.

Transfers are made on the following basis:

  • Within the group. Transfers between AIVIBE SOFTWARE SERVICES PRIVATE LIMITED and AIVEDHA INC are made under the governance of the parent company and remain subject to the jurisdiction stated in this Policy.
  • To providers. Transfers to the providers listed in this Policy are made under each provider's data processing terms, including the standard contractual clauses or equivalent transfer mechanism that provider offers, where such a mechanism applies to the transfer.
  • Under Indian law. Transfers are made in accordance with the Digital Personal Data Protection Act, 2023 and the rules made under it, including any restriction notified by the Government of India on transfers to a particular country.
  • To a destination you configure. Where you direct the Services to a model provider or tool of your own choosing, the transfer is made at your direction and to the region that provider operates in.

A transfer mechanism recognised by another country's law is applied where Indian law gives effect to it. It does not by itself extend the jurisdiction stated in this Policy.

14. Children

The Services are permitted from the age of 13. They are not offered to, and must not be used by, anyone under 13 years of age.

If you are between 13 and the age of majority in your country, you may use the Services only with the consent of, and under the supervision of, a parent or legal guardian who accepts the Terms of Service on your behalf. Where the law applying under this Policy requires verifiable parental consent for a person of your age, that consent must be given before the account is used.

Personal data is not knowingly collected from a person under 13. Where it comes to notice that personal data of a person under 13 has been collected, the account is closed and the data is deleted as quickly as it can be identified and removed.

A parent or legal guardian who believes a person under 13 has provided personal data should write to support@aivibe.in.

Behavioural advertising is not directed at a person known to be a child, and targeting is not applied to an account identified as belonging to a child.

15. Your rights and how to exercise them

One process applies to every request about personal data, whoever makes it and wherever they are. It is operated under Indian law and, where Indian law gives effect to a right arising under another framework, that right is handled through the same process.

What you may ask for

  • Access. A summary of the personal data held about you, the purposes it is processed for, and the identities of the providers it has been disclosed to.
  • Correction. Correction of personal data that is inaccurate or misleading, and completion of personal data that is incomplete.
  • Erasure. Deletion of personal data, subject to Retention and deletion and to what must be kept by law.
  • Withdrawal of consent. Withdrawal, at any time and as easily as it was given, of consent you have given. Withdrawal does not affect processing carried out before you withdrew it, and it does not affect processing that rests on a basis other than consent.
  • Objection to marketing. An end to marketing messages, through the unsubscribe link in any marketing email or by writing to support. Service messages — receipts, renewal notices, security alerts and notices of changes to these documents — continue while you hold an account.
  • Cookie preferences. A change to the non-essential categories, at any time, in the preference centre on the Cookie Policy page.
  • Nomination. Nomination of another individual to exercise these rights on your behalf in the event of your death or incapacity, as provided by the Digital Personal Data Protection Act, 2023.
  • Grievance. A grievance about how personal data has been handled, answered through the grievance route below.

How to make a request

  • Write to support@aivibe.in from the email address on the account. For the Americas and Europe regions you may instead write to support@aivedha.com; the request is handled through the same process.
  • State which of the rights above you are exercising and what you want done. A request that does not say what is being asked for is answered with a question rather than an action.
  • Where the request is made by an authorised agent, provide written authorisation from the account holder. The account holder may be asked to confirm it directly.

Verification

A request is acted on only when the identity of the person making it has been established to a degree appropriate to what is being asked for. Where the request comes from the address on the account, that is ordinarily sufficient; where it does not, or where the request concerns access to or deletion of a whole account, further verification is required. Information supplied for verification is used for verification and for nothing else. A request that cannot be verified is declined, with the reason given.

Timing

  • Receipt is acknowledged.
  • A verified request is answered within thirty (30) days. Where the request is complex or where several requests have been made, that period may be extended once, by up to a further thirty (30) days, and you are told before the first period ends that it has been extended and why.
  • A cookie preference change takes effect immediately, in the preference centre, without a request.

When a request is refused

A request is refused where acting on it would breach a legal obligation, defeat a legal hold, prejudice the detection or prevention of fraud or a security event, compromise the rights of another person, or require the retention of data solely so that it can be produced. A refusal is given in writing with the reason, and a refused request may be appealed by replying to the refusal; an appeal is decided by someone other than the person who decided the original request, and the outcome is given in writing.

No detriment

Exercising a right under this section does not lead to the denial of the Services, a different price, a different level of quality, or any other penalty.

Rights arising under another framework

You may hold rights under the law of the place you live. Those rights are handled through the process above, on the terms of this Policy and subject to Jurisdiction and governing law. Handling a request that originates in another framework is not a submission to that framework or to the jurisdiction of the country it comes from.

16. Marketing and sharing with third parties

Personal data described in this Policy is used to tell you about the products, offers, features and events of AicippY and of the group, by email and inside the product, and to measure whether those messages are useful. It is combined with usage data to decide what to show and who to show it to.

Personal data is shared with third parties, including for those third parties' own marketing and advertising purposes, and with analytics, advertising and marketing providers who process it on instruction. What is shared for that purpose is identifiers, contact details and usage data. The contents of your projects and the content you send to a model are not shared for marketing.

By using the Services you accept this use and this sharing. Where the law applying under this Policy requires consent for a particular kind of marketing or sharing, that kind is carried out only on the consent given through the preference centre or otherwise obtained.

You may stop marketing messages at any time through the unsubscribe link in any marketing email or by writing to support@aivibe.in, and you may switch off the Targeting category in the Cookie Policy preference centre. Neither stops the service messages sent while you hold an account.

17. Changes to this Policy

This Policy is updated as the Services change. A material change is announced by a notice on the website, by email, or by both. If you have asked not to receive legal notice emails, or have not supplied an email address, the notices still apply to your use of the Services and you remain responsible for reading them.

Using the Services after a change has been published means you accept the changed Policy.

The effective date at the top of this document is the date the current version took effect.

18. Language of this Policy

The English text of this Policy is the authoritative text. The website is published in several languages, and a translation of this document, whether produced by the company, by a machine or by a third party, is provided for convenience only.

Where a translation differs from the English text, in meaning, in emphasis or in effect, the English text prevails. This applies to the interpretation of the Policy, to any dispute about it, and to any proceeding before the courts named in Jurisdiction and governing law.

19. Contact and grievance

Questions about this Policy, requests under Your rights and how to exercise them, and grievances about the handling of personal data all go to the same address. Email is the route; a reply is sent to the address the message came from.

  • AIVIBE SOFTWARE SERVICES PRIVATE LIMITED
  • A501 Saraduez Olympus, Chennai, Tamil Nadu 600100, India
  • Email: support@aivibe.in

For the Americas and Europe regions:

A grievance is acknowledged on receipt and answered within the period stated under Timing. A grievance that is not resolved to your satisfaction may be escalated by replying to the answer, and is then decided by someone other than the person who decided it first.

Taking a grievance to a regulator

Where the internal route above does not resolve the matter, a complaint may be made to the authority that supervises data protection in the place you live. For the Company's own jurisdiction that is the Data Protection Board of India, constituted under the Digital Personal Data Protection Act, 2023, and a complaint to it is made after the grievance has first been raised with the Company. A person in the European Economic Area or the United Kingdom may complain to their national supervisory authority. Complaining to a regulator does not require the Company's agreement and does not affect any other right you hold; the Company answers a regulator that has authority over it, and the position in Jurisdiction and governing law is unchanged by this paragraph.

Related documents: Terms of Service · Cookie Policy