Shipping and delivery

PixlNova sells services and digital goods only. Every deliverable is transmitted electronically: a commit in a repository you own, a deployment into a cloud account you own, a document sent by email, or a file downloaded from your account. Nothing is manufactured, packed, posted, couriered or handed over in person.

There are no physical products in the catalogue and none are planned. If a physical item is ever sold, this policy will be replaced before that happens, not amended afterwards.

No shipping, courier, freight, handling, packaging or delivery fee is charged on any purchase, at any price, to any country. Published prices are for the work or the package itself.

If a charge under any of those names ever appears on a document you receive from PixlNova, it is an error. Report it and it will be corrected and refunded.

Because nothing is shipped, no postal or delivery address is requested at any point of purchase. The enquiry form on this site collects your name, email, phone, company, role, the service you want, your product stage, budget band, timeline, project description, a reference link, your important requirements, and how you found us. There is no street address among those fields.

Nothing crosses a border physically, so no customs declaration, import duty, clearance delay or carrier charge can arise from a PixlNova delivery. Any tax on the transaction itself is dealt with in section 11.

For services there is no single moment at which a parcel arrives. Delivery is continuous: work lands in your repository as it is written, and each milestone ends in something you can open and use. Section 3 describes the route and section 4 the timing.

projects.pixlnova.com and freelancer.pixlnova.com are separate products with their own terms. This policy states the delivery position for project packages because they are sold under the same proprietorship, but where that property publishes its own delivery, licence or escrow terms, those terms govern that purchase.

This policy does not govern freelancer.pixlnova.com engagements at all. Work agreed between two other parties on that marketplace is delivered under its escrow rules.

Code is pushed to a repository under your account, not to a studio machine, from the first commit. You can read the work as it happens rather than receiving it at the end. Delivery of code is therefore visible to you before any milestone is declared complete.

Hosting, database, domains and any other running infrastructure sit in accounts you own and pay for directly, with access granted to the studio rather than the other way round. Running costs reach you at cost, with no margin added by PixlNova.

This is a delivery fact as much as a commercial one: revoking studio access does not take your product offline, and there is no environment you cannot reach.

Each milestone ends in working software you can open, not a status update. It is delivered when the work is in your repository or deployed to your environment and you have been told it is ready for review.

Payment follows acceptance of a delivered milestone. Two rounds of revision inside the agreed scope are included at each milestone. Work that changes the scope is quoted before it starts.

The last delivery of an engagement is a written handover: the architecture, the environment variables, the deploy steps, and the access you need to run everything without the studio. It is sent by email and, where it belongs with the code, committed to your repository.

An engagement can be stopped at any milestone boundary. You keep everything delivered and paid for, including the code, and no further milestone is invoiced. What happens to money already paid is dealt with in the Refunds and Cancellation Policy, not here.

Delivery dates come from the milestone plan in the scope document agreed before the first invoice. That document states what is being built, what is explicitly excluded, the milestones and the dates against them. Where it and this page differ on timing, it governs.

The ranges published on the pricing page span the smallest to the largest plan in each service. They describe typical shapes of work, not an offer:

Monthly plans deliver on a monthly cycle. The deliverable count for the month is written down before the month starts.

The studio operates from Attur, Salem, Tamil Nadu, India, in Indian Standard Time (UTC+5:30). Delivery activity, review responses and handovers happen in those hours. The published working hours are in the contact block at the end of this document.

A reply or a delivery outside those hours is a courtesy, not a commitment, and cannot be relied on when planning a launch.

PixlNova does not publish an uptime SLA, a guaranteed response time or round-the-clock support, and none is implied by anything on this page. Where a plan excludes those, the exclusion is printed next to the price.

Project packages bought on projects.pixlnova.com are delivered as downloads linked to the account used at checkout. Sign in with that account and the package is there. Nothing is emailed as an attachment and nothing is sent by post.

Download links are account-bound and may be time-limited or attempt-limited. Links can be rotated or revoked where they are being shared or abused; that does not remove the entitlement from your account.

Access is granted once the payment provider confirms the payment. In the ordinary case that is within minutes of checkout. It is not instantaneous by design, and it cannot be, because the confirmation comes from the provider rather than from PixlNova.

A confirmation email is sent when an order completes. If it does not arrive, check the spam folder, but do not wait on it: the account is the record of what you own, and access does not depend on the email being delivered.

Packages are maintained and may be updated. Keep a local copy of what you download. Continued availability of a specific historical version is not promised.

Payments are processed by Razorpay and by Stripe. Either provider may place a transaction in manual review, request additional verification, or hold settlement for fraud, risk or compliance reasons. While a payment is held, delivery waits, because delivery follows cleared payment.

PixlNova cannot shorten, override or appeal that review on your behalf. What can be done is telling you the payment status honestly and delivering the moment it clears.

A payment that fails, is reversed by the bank, or is disputed after the fact suspends delivery of anything not already delivered. Access already granted may be withdrawn while the dispute is open.

Service delivery frequently waits on the client: repository or cloud access, content, credentials for a third-party service, a decision, or acceptance of the previous milestone.

When that happens you will be told what is blocking, and revised dates are written down rather than assumed. Waiting time is not billed, but it does move the schedule.

App store review, DNS propagation, a provider's own outage, or a paid third-party plan the project needs and you do not yet hold, all sit outside the studio's control and can move a delivery date.

This is a one-person studio. Illness, a network or power failure, or another event outside reasonable control can delay delivery. If that happens you will be told promptly, with a revised date, rather than left to notice.

Code lives in your repository and infrastructure in your accounts precisely so that a delay of this kind never becomes a loss of access to your own product.

Email hello@pixlnova.com. For a service engagement, replying on the existing project thread is faster, because the scope and milestone history are already in it.

Never send card, UPI or bank credentials in a support message. They are never needed to investigate a delivery, and PixlNova will never ask for them.

Delivery complaints are handled on the same published timeframes as any other grievance. They are stated here rather than paraphrased:

Escalate through the Grievance Redressal Policy, which names the officer, the escalation path and the timeframes. If the failure means you should not have been charged at all, the Refunds and Cancellation Policy applies instead of this one.

Work is in your repository and your accounts throughout the engagement. That is possession and visibility. It is not, by itself, an assignment of intellectual property.

Full ownership of the source code, the designs and the associated intellectual property created for you transfers on cleared final payment, in writing. Cleared means the money has actually settled, not that a payment has been initiated.

Because the repository is already yours, that transfer is a formality rather than a migration. Before it happens, whatever rights you hold in delivered work are the rights stated in your signed scope; this policy neither grants nor removes any.

Open-source libraries, fonts, stock assets and third-party services used in a delivery remain under their own licences and are not transferred. Where a component carries a licence obligation, it is identified in the written handover.

The exact period is printed on the plan you bought and restated in your scope document. It runs from the delivery it covers.

If something shipped broken — it does not do what the accepted scope says it does — it is fixed at no charge inside the warranty period.

Ongoing support is a separate monthly arrangement priced by what it covers. Nothing renews automatically, and there is no retainer you have to remember to cancel.

Confirmation and notification email is sent through Resend, which processes your email address and the message content in order to deliver it.

Delivery records are stored in a Supabase-hosted PostgreSQL database in region ap-southeast-2, which is Sydney, Australia. Personal data belonging to users in India is therefore stored outside India. This is stated plainly because it is a decision a buyer may reasonably object to, not a detail to bury.

The Privacy Policy sets out the legal basis, retention and your rights. The Subprocessors page lists every provider in the path, including the payment providers and Resend.

Delivery adds nothing to the price. The amount agreed in the scope, or shown at checkout, is the amount payable. Third-party running costs — hosting, domains, model APIs, store fees — are billed to your own accounts by those providers at their cost, never marked up by PixlNova.

Prices are published as real figures in both INR and USD, set per market rather than converted from one another. Indian payments are processed by Razorpay and international payments by Stripe. Which provider handles a payment affects how quickly it clears, and therefore when delivery begins — see clause 6.1.

The billing document issued with a delivery is described below, together with the current GST position. It is reproduced from the identity record rather than restated, so it cannot drift out of date on this page:

A change is material if it alters how or when a deliverable reaches you, introduces a charge, or reduces a right you have under this policy. Material changes are published at least 30 days before they take effect. Corrections of wording, typography or broken cross-references are clarifications and take effect immediately.

For a service engagement, a scope document you have signed governs over this page wherever the two differ. For a purchase on projects.pixlnova.com, that property's own terms and licence govern over this page. This policy is the default, not the ceiling.

Every version of this document carries a date, an effective-from date and the date it was last read and found still accurate. The version history at the foot of this page lists each change in one line.